I thought the Embedded server was good for a scenario where you wanted quickly to build a core with lots of documents locally. And then, move the core into production and swap it in. So you minimize the network traffic.
Regards, Alex. ---- Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter: http://www.solr-start.com/ On 5 August 2015 at 10:54, Shawn Heisey <apa...@elyograg.org> wrote: > 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 >
