Thanks, Shawn. Adding it to all clients and servers worked
On Tue, Apr 8, 2014 at 3:37 PM, KNitin wrote:
> Thanks. I missed "the clients" part from doc. Will try and update the
> results here
>
>
>
>
> On Tue, Apr 8, 2014 at 3:27 PM, Shawn Heisey wrote:
>
>> On 4/8/2014 4:13 PM, KNitin wrote:
Thanks. I missed "the clients" part from doc. Will try and update the
results here
On Tue, Apr 8, 2014 at 3:27 PM, Shawn Heisey wrote:
> On 4/8/2014 4:13 PM, KNitin wrote:
>
>> I have already raised the jute.buffersize to 5Mb on the zookeeper server
>> side but still hitting the same problem.
On 4/8/2014 4:13 PM, KNitin wrote:
I have already raised the jute.buffersize to 5Mb on the zookeeper server
side but still hitting the same problem. Should i make any changes on the
solr server side for this (client side changes?)
The jute.maxbuffer system property needs to be set on everything
Thanks, Shawn
I have already raised the jute.buffersize to 5Mb on the zookeeper server
side but still hitting the same problem. Should i make any changes on the
solr server side for this (client side changes?)
On Tue, Apr 8, 2014 at 9:09 AM, Shawn Heisey wrote:
> On 4/8/2014 9:48 AM, KNitin wr
On 4/8/2014 9:48 AM, KNitin wrote:
I am running solr cloud 4.3.1 (there is a plan to upgrade to later
versions but that would take a few months). I noticed a very peculiar solr
behavior in solr that beyond *2496* cores I am unable to create any more
collections due to this error
*Could not get
Hi
I am running solr cloud 4.3.1 (there is a plan to upgrade to later
versions but that would take a few months). I noticed a very peculiar solr
behavior in solr that beyond *2496* cores I am unable to create any more
collections due to this error
*Could not get shard id for core.*
I also n
