There's a reason why we have min set the way we do. ;-) ZK was never designed for such tight latencies, first and foremost is reliability/availability and correctness.
I suspect if you want that level of latency you'd be better off turning down the ticktime instead. Then you're going to have to make sure that all depended upon resources themselves have super low latencies (disk for example). Perhaps a ramdisk in that case? What results have you seen so far? Patrick On Mon, Oct 31, 2011 at 5:08 AM, amithdk <[email protected]> wrote: > Hi Guys, > > > > Currently if we set > > > > tickTime=2000 > > minSessionTimeOut=200 > > maxSessionTimeOut=1500 in zoo.cfg > > > > Zookeeper will successfully read the configuration and start. > > But this kind of configuration may lead to many Session Expiry, since > tickTime>maxSessionTimeOut. > > > > So do u guys think this should be handled in server side? > > > > Thanks in advance. > > > > Amith > > > > > >
