Thanks for the updates. When can we expect 3.4.8? What are the plans for 3.5.* stable version release?
-Thanks -----Original Message----- From: Rakesh Radhakrishnan [mailto:[email protected]] Sent: Tuesday, January 19, 2016 9:58 AM To: [email protected] Cc: DevZooKeeper Subject: Re: 3.4.8 release Thanks Flavio for the reply. Bad disk is one such case where it can occur exception. In jira its described using bad disk scenario. In general, it can be any unexpected exception which will bring down the ZooKeeperCriticalThread. The jira proposal is to handle the generic exception handling logic. Yes, this is not a core execution flow, but an improvement to the critical thread exception handling logic. It would be good to take up this also if time permits. -Rakesh On Tue, Jan 19, 2016 at 8:07 PM, Flavio Junqueira <[email protected]> wrote: > Is ZK-2247 just good to have or is it a blocker? My sense is that it > is critical because a bad disk can cause the ensemble to stall, but > I'm not sure I want to block 3.4.8 on it. Is it good if we just > release 3.4.8 now and make it a blocker for 3.4.9? > > -Flavio > > > On 19 Jan 2016, at 07:31, Rakesh Radhakrishnan > > <[email protected]> > wrote: > > > > Thank you Raul for the initiative. > > > > It would be good if we can include ZOOKEEPER-2247 into this release, > > it looks like the proposed patch solves the issue. Probably needs to > > undergo few more review cycles. > > > > Thanks, > > Rakesh > > > > On Tue, Jan 19, 2016 at 6:30 AM, Raúl Gutiérrez Segalés < > [email protected] > >> wrote: > > > >> Hi, > >> > >> I'd like to prepare an RC for 3.4.8 soonish (hopefully, this week). > >> For now, this is the only blocker I can see: > >> > >> ZOOKEEPER-2355: Ephemeral node is never deleted if follower fails > >> while reading the proposal packet > >> > >> Given the magnitude of that bug, I think it should go out with this > >> release. > >> > >> Any other JIRA that should be included? > >> > >> > >> -rgs > >> > >
