Session timeout is a Zookeeper concept. It's just the amount of time (in MS) that a client session can be idle for before the Zookeeper server times it out. A heart beat keeps the session alive, so the session will only time out due to network issues.
The connection timeout is a Curator concept. Jordan described its use in this thread. Basically, it just defines how long Curator will wait for a connection to be established to Zookeeper before giving up and trying again. On Wed, Nov 2, 2016 at 4:00 PM, Imesha Sudasingha <[email protected]> wrote: > Hello all, > > I was going through this thread and found out I too need a clear > explanation on "what is connectionTimeout and sessionTimeout". Even though > you have discussed a lot about it(which I have read), still I'm not getting > a clear picture. Can someone elaborate on the it? And give a clear view of > those 2 parameters and what they are for? > > Thanks! > > Regards, > Imesha Sudasingha > > On Nov 2, 2016 4:26 AM, "Jordan Zimmerman" <[email protected]> > wrote: > >> >> so if we use a connectionTimeout smaller than sessionTimeout, we may fail >> before having tried all the nodes. >> >> >> That’s correct and up to you. That’s why these are configurable options. >> Use values that make sense for your applications. >> >> -Jordan >> >> >> >>
