On 08/05/2015 08:34 PM, Ken Krugler wrote:
Hi Shawn,
We have a different use case than the ones you covered in your response to
Robert
(below), which I wanted to call out.
We currently use the embedded server when building indexes as part of a Hadoop
workflow. The results get copied to a production analytics server and swapped
in on
a daily basis.
Writing to multiple embedded servers (one per reduce task) gives us maximum
performance, and has proven to be a very reliable method for the daily rebuild
of
pre-aggregations we need for our analytics use case.
Regards,
-- Ken
Hi,
applications that are ultimately deployed by a third party not well versed in
the intricacies of deploying a full-blown installation of solr would be another
use case. Embedding the server, either through embedded class or by deploying
it entirely within web application (as opposed to a stand alone server) might be
preferred as it makes deployment much simpler.
There are applications where solr could be used as a search engine to
supplement
their core functionalities but only when one doesnt have to pay the price of
overly
complicated deployment of the entire package.
lukasz
PS - I'm also currently looking at using embedded Solr as a state storage
engine for Samza.
From: Shawn Heisey
Sent: August 5, 2015 7:54:07am PDT
To: solr-user@lucene.apache.org
Subject: Re: Embedded Solr now deprecated?
On 8/5/2015 7:09 AM, Robert Krüger wrote:
I tried to upgrade my application from solr 4 to 5 and just now realized
that embedded use of solr seems to be on the way out. Is that correct or is
there a just new API to use for that?
Building on Erick's reply:
I doubt that the embedded server is going away, and I do not recall
seeing *anything* marking the entire class deprecated. The class still
receives attention from devs -- this feature was released with 5.1.0:
https://issues.apache.org/jira/browse/SOLR-7307
That said, we have discouraged users from deploying it in production for
quite some time, even though it continues to exist and receive developer
attention. Some of the reasons that I think users should avoid the
embedded server: It doesn't support SolrCloud, you cannot make it
fault-tolerant (redundant), and troubleshooting is harder because you
cannot connect to it from outside of the source code where it is embedded.
Deploying Solr as a network service offers much more capability than you
can get when you embed it in your application. Chances are that you can
easily replace EmbeddedSolrServer with one of the SolrClient classes and
use a separate Solr deployment from your application.
Thanks,
Shawn
--------------------------
Ken Krugler
+1 530-210-6378
http://www.scaleunlimited.com
custom big data solutions & training
Hadoop, Cascading, Cassandra & Solr
--
-------------------------------------------------------------------------
Lukasz Salwinski PHONE: 310-825-1402
UCLA-DOE Institute FAX: 310-206-3914
UCLA, Los Angeles EMAIL: luk...@mbi.ucla.edu
-------------------------------------------------------------------------
