keeping a high value for zookeeper.connection.timeout.ms

["Digumarthi, Prabhakar Venkata Surya" <Pr...@capitalone.com>]

Hi All,


Right now we are running kafka in AWS EC2 servers and zookeeper is also running on separate EC2 instances.

We have created a service (system units )  for kafka and zookeeper to make sure that they are started in case the server gets rebooted.

The problem is sometimes zookeeper severs are little late in starting and kafka brokers by that time getting terminated.


So to deal with this issue we are planning to increase the zookeeper.connection.timeout.ms to some high number like 10 mins, at the broker side. Is this a good approach ?


Thanks,
Prabhakar
________________________________________________________

The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.