Re: CloudSolrStream can't set the setZkClientTimeout and setZkConnectTimeout properties

2017-01-19 Thread Will Martin
Default behavior. Client - Server negotiate 2/3 of min (max server, max client). This allows a client time to search for a new leader before all of its time consumed. zookeeper user @ apache org -will On 1/19/2017 12:59 PM, Yago Riveiro wrote: I can see some reconnects in my logs, the

Re: CloudSolrStream can't set the setZkClientTimeout and setZkConnectTimeout properties

2017-01-19 Thread Yago Riveiro
I can see some reconnects in my logs, the process of consuming the stream doesn't broke and continue as normal. The timeout is 10s but I can see in logs that after 6s the reconnect is triggered, I don't know if it's the default behaviour or the zk timeout it's not honoured. - Best regards

Re: CloudSolrStream can't set the setZkClientTimeout and setZkConnectTimeout properties

2017-01-09 Thread Joel Bernstein
Currently these are not settable.It's easy enough to add a setter for this values. What types of behaviors have you run into when CloudSolrClient is having timeouts issues? Joel Bernstein http://joelsolr.blogspot.com/ On Mon, Jan 9, 2017 at 10:06 AM, Yago Riveiro wrote:

CloudSolrStream can't set the setZkClientTimeout and setZkConnectTimeout properties

2017-01-09 Thread Yago Riveiro
Hi, Using the CloudSolrStream, is it possible define the setZkConnectTimeout and setZkClientTimeout of internal CloudSolrClient? The default negotiation timeout is set to 10 seconds. Regards, /Yago - Best regards /Yago -- View this message in context: