Hi Jan, Nevermind you already answered that in the mailing list. Thank you again.
Amrit Sarkar Search Engineer Lucidworks, Inc. 415-589-9269 www.lucidworks.com Twitter http://twitter.com/lucidworks LinkedIn: https://www.linkedin.com/in/sarkaramrit2 On Mon, Jan 30, 2017 at 1:21 PM, Amrit Sarkar <sarkaramr...@gmail.com> wrote: > Hi Jan, > > Thank you for responding. I understand we should not use embedded ZK in > production. As three components share the same heap, I am assuming there is > no way to control the component individual consumption rate? > > Amrit Sarkar > Search Engineer > Lucidworks, Inc. > 415-589-9269 > www.lucidworks.com > Twitter http://twitter.com/lucidworks > LinkedIn: https://www.linkedin.com/in/sarkaramrit2 > > On Sun, Jan 29, 2017 at 4:35 AM, Jan Høydahl <jan....@cominvent.com> > wrote: > >> Hi, >> >> The embedded ZK is not intended for production use, please use a >> standalone cluster. >> Embedded ZK will share JVM heap with Jetty and Solr, so if any of them >> cause OOM, it will affect all. >> >> -- >> Jan Høydahl, search solution architect >> Cominvent AS - www.cominvent.com >> >> > 28. jan. 2017 kl. 09.21 skrev Amrit Sarkar <sarkaramr...@gmail.com>: >> > >> > I would like to understand how the embedded ZK works with Solr. If Xg >> > memory is allocated to the Solr installation and we spin up the >> SolrCloud >> > with embedded ZK; what part/percentage of the X is allocated to the ZK >> or >> > is it shared? >> > >> > If that is known, how can I change the memory settings for the embedded >> ZK? >> > >> > Amrit Sarkar >> > Search Engineer >> > Lucidworks, Inc. >> > 415-589-9269 >> > www.lucidworks.com >> > Twitter http://twitter.com/lucidworks >> > LinkedIn: https://www.linkedin.com/in/sarkaramrit2 >> >> >
