Hoster requirements for running Solr - solr

I am planning to add a full-text search engine for searching a MySQL database to a website. Most recommendations on a nice, user-friendly implementation I found, mentioned the use of Apache Solr.
Keeping this in mind I started searching for the requirements for a hoster to use Solr but I didn't find any useful information expect for "it should support java". So I picked a random host that states it has Java JRE installed (http://wiki.dreamhost.com/What_We_Support) and asked if they supported Solr. Unfortunately, the answer was "no".
So, what would I need to be looking for? Do I need a dedicated server, a VPN, or are there shared hosting solutions where it is possible to run Solr?
What are the system requirements?
I hope there is someone out there, who knows a bit about this. Thanks!

The Solr requirements can be found here: https://wiki.apache.org/solr/SolrInstall
So an installed JRE is needed, but also an servlet container, which also needs an JRE.
If I would be in your situation, I would rent an virtual server.
An other option is an hosting service, specialized for solr hosting: search the web for "apache solr hosting". There are offers for free or payed offers also.

I've been running two drupal websites + apache solr on an ssd vps from rosehosting utilizing 2 cpu cores and 1gb ram. I wasn't able to setup apache solr and java myself so that's why I rented a managed vps service.
If you're not that technical I suggest you add managed to the keywords mentioned by #The Bndr and make sure you check with your host that they will support apache solr and java on your vps

Related

Unable to contact your Apache Solr server

I have a problem with an old TYPO3 installation (TYPO3 site 7 LTS [7.6.9]).
The site is using Apache Solr as the search engine, but it's not working. When a user tries to search, the system shows a message telling that the search engine is not available now.
In the administration panel, if I go to the Search option, I see this message:
Unable to contact your Apache Solr server.
Hosts missing:http://localhost:8080/solr/core_es/
http://localhost:8080/solr/core_eu/
http://localhost:8080/solr/core_en/
Of course, I have checked that Solr is running and listening on the port 8080. The Solr server is on the same machine than TYPO3.
I found this link about the Apache Solr configuration, but I cannot find these administration pages. I would like to test with the machine's public IP. In fact, I changed all the records regarding Solr in the cf_tx_solr_configuration table, and cleared all the cache tables manually, with no effect.
I have a couple of questions here:
Is it possible to change the configuration of the Solr server in TYPO3? If so, how can I do that?
Is TYPO3 shipped with an out-of-the-box search feature? If so, how can I disable Apache Solr and use the default search engine?
Thanks so much in advance!
please consume appropriate documentation Version of installed Extension.
So I assume(see Version Matix) you are using EXT:Solr version 6.5, therefore you must use the documentation for EXT:Solr v. 6.5.
--
QA
Is it possible to change the configuration of the Solr server in TYPO3? If so, how can I do that?
Yes, it is. You can set it via TypoScript path "plugin.tx_solr.solr.scheme|host|port|..."
Is TYPO3 shipped with an out-of-the-box search feature? If so, how can I disable Apache Solr and use the default search engine?
Yes, TYPO3 has build in search feature. Its name is indexed_search.
PS: You know, there are much more modern versions of TYPO3 available? Please upgrade at least to the newer major release.

Configure SOLR indexing with AEM 6.1

I am trying to configure SOLR indexing with AEM 6.1 but struggling with the following: -
What type of installation should be used for SOLR (embedded v/s
remote).
How to configure the selected installation with AEM 6.1.
How to determine whether the indexing has been successfully done.
Any help would be extremely appriciated.
I did lot of research on SOLR with AEM 6.0. I think I can answer to your question.
It depends on what are the requirements of the client. If the clients needs a quick search response and it have lot of content, you should prefer remove vs embedded. If the site has small content, the embedded could be sufficient. The remote permit to have a sharded cluster, so you can optimize the concurrent search response by adding more shared
The documentation of AEM is pretty well documented about this. You can find here: https://docs.adobe.com/docs/en/aem/6-1/deploy/platform/queries-and-indexing.html
Finally you can see the indexation well configured by enabling the logging configuration about the search (Look for to Enable Logging in the previous URL). You can test your search with tool in the ACS-Common with tools in ACS-Tools (http://adobe-consulting-services.github.io/acs-aem-tools/)
Hope this will help you.
Stéphane
I've stumbled upon these projects, as I searched for AEM Solr integration:
https://github.com/headwirecom/aem-solr-search
https://github.com/infielddesign/aem-id-solrindexer
Maybe it will help you with the Solr integration and configuration.
And as already mentioned above, the type of installation highly depends on your customer requirements.

Search engine for Apache Derby

I would like use a search engine for my application with Apache Derby database (contatin around 10k rows with text).
For web projects I used an elasticsearch, but it a desktop application. I would like to use an elasticksearch or solr for this app. It possible run elasticsearch or solr for it? It's require many memory or run in other (not application) thread, or have an alternative for derby?
There is a Lucene-Derby integration as part of this summer's release of Derby: https://issues.apache.org/jira/browse/DERBY-590
The development is complete; it is in testing. You can get access to it now, and give feedback to the development team about how it works for you.

Need some information about Crawl Anywhere and solr

I gone through the crawl anywhere documentation but i am very much confuse about its installation steps.
What i understood is Apache is optional. But do need independent tomcat instance for crawl? Because what i saw in folder structure, there is tomcat folder already present and war file is also there?
Also do we need independent instance of Apache solr also ?
If we want to add postgresql database to crawl, how we can do that?
Please provide some link also so that I can go through it and clarify any doubt I have in my mind.
Apache is needed to use admin interface. Tomcat is needed for some interactive features. You can crawl without both of them.
No.
MySQL and MongoDB are supported. The code is open source, so you can add postgresql support.
Try Google Groups for other questions

Install Jetty or run embedded for Solr install

I am about to install Solr on a production box. It will be the only Java applet running and be on the same box as the web server (nginx).
It seems there are two options.
Install Jetty separately and configure to use with Solr
Set Solr's embedded Jetty server to start as a service and just use that
Is there any performance benefit in having them separate?
I am a big fan of KISS, the less setup the better.
Thanks
If you want KISS there is no question: 2. stick to vanilla Solr distrib with included jetty.
Doing the work of installing an external servlet engine would make sense if you needed Tomcat for example, but just to use the same thing (Jetty) Solr already includes...no way.
Solr is still using jetty 6. So there would be some benefits if you can get the solr application to run in a recent jetty distribution. For example you could use jetty 9 and use features like SPDY to enhance the response times of your application.
However I have no idea or experience if it's possible to run the solr application standalone in a servlet engine.
Another option for running Solr and keeping it simple is to use Solr-Undertow which is a high performance with small footprint server for Solr. It is easy to use on local machines for development and also production. It supports simple config files for running instances with different data directories, ports and more. It also can run just by pointing it at a distribution .zip file without needing to unpack it.
(note, I am the author of Solr-Undertow)
Link here: https://github.com/bremeld/solr-undertow with releases under the "Releases" tab.

Resources