Ah, I hadn't seen that that had a patch. Could you mark the jira's which have a patch, as patch available. Even if the patch isn't ready to go in, it'll give an idea of what code is available.
-Ivan On 11 November 2014 20:23, Sijie Guo <[email protected]> wrote: > BOOKKEEPER-705 is what we handled the session expiry event on client & > server side. > > - Sijie > > On Fri, Nov 7, 2014 at 7:11 AM, Ivan Kelly <[email protected]> wrote: > >> Hi folks, >> >> Currently bookie lifetime is dependent on the zookeeper session which >> the bookie was started with. This is bad, and unnecessary and >> something that has causes us some downtime here. I have a fix for this >> available, but before I put up the patch, I'd like to know if anyone >> has also fixed this (I'm looking in the direction of Twitter here). >> BOOKKEEPER-704 added a zookeeper client that survived session expiry >> but this client was never wired into anything. I'm currently writing >> some tests for this in the bookkeeper client. >> >> @Sijie, do you guys already have more changes in this area. I'd like >> to avoid duplicating work here. >> >> Cheers, >> Ivan >>
