You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by Raúl Gutiérrez Segalés <rg...@itevenworks.net> on 2016/01/19 02:00:49 UTC
3.4.8 release
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
Re: 3.4.8 release
Posted by Raúl Gutiérrez Segalés <rg...@itevenworks.net>.
On 29 January 2016 at 10:23, Flavio Junqueira <fp...@apache.org> wrote:
> Give me until the end of today to have a look at ZK-2247. Rakesh has put
> the effort to prepare the patch, so I'd like to consider it. If it is not
> ready, then let's push it to 3.4.9. Does it sound good, Raul?
>
Yeah that's reasonable. I actually won't be able to cut an RC until Sunday,
so we have the whole weekend for that patch get more reviews :-) Thanks
Flavio!
-rgs
>
> -Flavio
>
> > On 29 Jan 2016, at 10:20, Raúl Gutiérrez Segalés <rg...@itevenworks.net>
> wrote:
> >
> > Ok - lets punt them to 3.4.9 then.
> >
> >
> > -rgs
> >
> > On 29 January 2016 at 10:10, Chris Nauroth <cn...@hortonworks.com>
> wrote:
> >
> >> +1 for expediting the 3.4.8 release. Our goal was simply to correct the
> >> critical bug discovered late in 3.4.7. Any patches more than that can
> be
> >> deferred to a 3.4.9 at a later date.
> >>
> >> --Chris Nauroth
> >>
> >>
> >>
> >>
> >> On 1/29/16, 10:06 AM, "Flavio Junqueira" <fp...@apache.org> wrote:
> >>
> >>> +1
> >>>
> >>>> On 29 Jan 2016, at 10:02, Ted Yu <yu...@gmail.com> wrote:
> >>>>
> >>>> ZOOKEEPER-2355 is in Open state as of now.
> >>>>
> >>>> My two cents:
> >>>>
> >>>> 3.4.7 has been retracted.
> >>>> It would be nice to get 3.4.8 out the door soon so that zookeeper
> users
> >>>> can
> >>>> pick up bug fixes in between 3.4.6 and 3.4 branch.
> >>>>
> >>>> On Thu, Jan 28, 2016 at 8:57 AM, Raúl Gutiérrez Segalés
> >>>> <rgs@itevenworks.net
> >>>>> wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> On 28 January 2016 at 07:07, Talluri, Chandra <
> >>>>> Chandra.Talluri@fmr.com.invalid> wrote:
> >>>>>
> >>>>>> Thanks for the updates.
> >>>>>>
> >>>>>> When can we expect 3.4.8?
> >>>>>>
> >>>>>
> >>>>> I think we need to decide if we want to include these patches:
> >>>>>
> >>>>> https://issues.apache.org/jira/browse/ZOOKEEPER-2355
> >>>>> https://issues.apache.org/jira/browse/ZOOKEEPER-2247
> >>>>>
> >>>>> They seem to be almost ready, though there might be some subtleties
> >>>>> left to
> >>>>> be addressed.
> >>>>>
> >>>>>
> >>>>>> What are the plans for 3.5.* stable version release?
> >>>>>>
> >>>>>
> >>>>> The general plan for making 3.5 stable is here:
> >>>>>
> >>>>> http://markmail.org/message/ymxliy2rrwjc2pmo
> >>>>>
> >>>>> I believe Chris Nauroth will be the RM for the upcoming 3.5.2
> release.
> >>>>>
> >>>>>
> >>>>> -rgs
> >>>>>
> >>>
> >>>
> >>
> >>
>
>
Re: 3.4.8 release
Posted by Raúl Gutiérrez Segalés <rg...@itevenworks.net>.
On 29 January 2016 at 10:23, Flavio Junqueira <fp...@apache.org> wrote:
> Give me until the end of today to have a look at ZK-2247. Rakesh has put
> the effort to prepare the patch, so I'd like to consider it. If it is not
> ready, then let's push it to 3.4.9. Does it sound good, Raul?
>
Yeah that's reasonable. I actually won't be able to cut an RC until Sunday,
so we have the whole weekend for that patch get more reviews :-) Thanks
Flavio!
-rgs
>
> -Flavio
>
> > On 29 Jan 2016, at 10:20, Raúl Gutiérrez Segalés <rg...@itevenworks.net>
> wrote:
> >
> > Ok - lets punt them to 3.4.9 then.
> >
> >
> > -rgs
> >
> > On 29 January 2016 at 10:10, Chris Nauroth <cn...@hortonworks.com>
> wrote:
> >
> >> +1 for expediting the 3.4.8 release. Our goal was simply to correct the
> >> critical bug discovered late in 3.4.7. Any patches more than that can
> be
> >> deferred to a 3.4.9 at a later date.
> >>
> >> --Chris Nauroth
> >>
> >>
> >>
> >>
> >> On 1/29/16, 10:06 AM, "Flavio Junqueira" <fp...@apache.org> wrote:
> >>
> >>> +1
> >>>
> >>>> On 29 Jan 2016, at 10:02, Ted Yu <yu...@gmail.com> wrote:
> >>>>
> >>>> ZOOKEEPER-2355 is in Open state as of now.
> >>>>
> >>>> My two cents:
> >>>>
> >>>> 3.4.7 has been retracted.
> >>>> It would be nice to get 3.4.8 out the door soon so that zookeeper
> users
> >>>> can
> >>>> pick up bug fixes in between 3.4.6 and 3.4 branch.
> >>>>
> >>>> On Thu, Jan 28, 2016 at 8:57 AM, Raúl Gutiérrez Segalés
> >>>> <rgs@itevenworks.net
> >>>>> wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> On 28 January 2016 at 07:07, Talluri, Chandra <
> >>>>> Chandra.Talluri@fmr.com.invalid> wrote:
> >>>>>
> >>>>>> Thanks for the updates.
> >>>>>>
> >>>>>> When can we expect 3.4.8?
> >>>>>>
> >>>>>
> >>>>> I think we need to decide if we want to include these patches:
> >>>>>
> >>>>> https://issues.apache.org/jira/browse/ZOOKEEPER-2355
> >>>>> https://issues.apache.org/jira/browse/ZOOKEEPER-2247
> >>>>>
> >>>>> They seem to be almost ready, though there might be some subtleties
> >>>>> left to
> >>>>> be addressed.
> >>>>>
> >>>>>
> >>>>>> What are the plans for 3.5.* stable version release?
> >>>>>>
> >>>>>
> >>>>> The general plan for making 3.5 stable is here:
> >>>>>
> >>>>> http://markmail.org/message/ymxliy2rrwjc2pmo
> >>>>>
> >>>>> I believe Chris Nauroth will be the RM for the upcoming 3.5.2
> release.
> >>>>>
> >>>>>
> >>>>> -rgs
> >>>>>
> >>>
> >>>
> >>
> >>
>
>
Re: 3.4.8 release
Posted by Flavio Junqueira <fp...@apache.org>.
Give me until the end of today to have a look at ZK-2247. Rakesh has put the effort to prepare the patch, so I'd like to consider it. If it is not ready, then let's push it to 3.4.9. Does it sound good, Raul?
-Flavio
> On 29 Jan 2016, at 10:20, Raúl Gutiérrez Segalés <rg...@itevenworks.net> wrote:
>
> Ok - lets punt them to 3.4.9 then.
>
>
> -rgs
>
> On 29 January 2016 at 10:10, Chris Nauroth <cn...@hortonworks.com> wrote:
>
>> +1 for expediting the 3.4.8 release. Our goal was simply to correct the
>> critical bug discovered late in 3.4.7. Any patches more than that can be
>> deferred to a 3.4.9 at a later date.
>>
>> --Chris Nauroth
>>
>>
>>
>>
>> On 1/29/16, 10:06 AM, "Flavio Junqueira" <fp...@apache.org> wrote:
>>
>>> +1
>>>
>>>> On 29 Jan 2016, at 10:02, Ted Yu <yu...@gmail.com> wrote:
>>>>
>>>> ZOOKEEPER-2355 is in Open state as of now.
>>>>
>>>> My two cents:
>>>>
>>>> 3.4.7 has been retracted.
>>>> It would be nice to get 3.4.8 out the door soon so that zookeeper users
>>>> can
>>>> pick up bug fixes in between 3.4.6 and 3.4 branch.
>>>>
>>>> On Thu, Jan 28, 2016 at 8:57 AM, Raúl Gutiérrez Segalés
>>>> <rgs@itevenworks.net
>>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> On 28 January 2016 at 07:07, Talluri, Chandra <
>>>>> Chandra.Talluri@fmr.com.invalid> wrote:
>>>>>
>>>>>> Thanks for the updates.
>>>>>>
>>>>>> When can we expect 3.4.8?
>>>>>>
>>>>>
>>>>> I think we need to decide if we want to include these patches:
>>>>>
>>>>> https://issues.apache.org/jira/browse/ZOOKEEPER-2355
>>>>> https://issues.apache.org/jira/browse/ZOOKEEPER-2247
>>>>>
>>>>> They seem to be almost ready, though there might be some subtleties
>>>>> left to
>>>>> be addressed.
>>>>>
>>>>>
>>>>>> What are the plans for 3.5.* stable version release?
>>>>>>
>>>>>
>>>>> The general plan for making 3.5 stable is here:
>>>>>
>>>>> http://markmail.org/message/ymxliy2rrwjc2pmo
>>>>>
>>>>> I believe Chris Nauroth will be the RM for the upcoming 3.5.2 release.
>>>>>
>>>>>
>>>>> -rgs
>>>>>
>>>
>>>
>>
>>
Re: 3.4.8 release
Posted by Flavio Junqueira <fp...@apache.org>.
Give me until the end of today to have a look at ZK-2247. Rakesh has put the effort to prepare the patch, so I'd like to consider it. If it is not ready, then let's push it to 3.4.9. Does it sound good, Raul?
-Flavio
> On 29 Jan 2016, at 10:20, Raúl Gutiérrez Segalés <rg...@itevenworks.net> wrote:
>
> Ok - lets punt them to 3.4.9 then.
>
>
> -rgs
>
> On 29 January 2016 at 10:10, Chris Nauroth <cn...@hortonworks.com> wrote:
>
>> +1 for expediting the 3.4.8 release. Our goal was simply to correct the
>> critical bug discovered late in 3.4.7. Any patches more than that can be
>> deferred to a 3.4.9 at a later date.
>>
>> --Chris Nauroth
>>
>>
>>
>>
>> On 1/29/16, 10:06 AM, "Flavio Junqueira" <fp...@apache.org> wrote:
>>
>>> +1
>>>
>>>> On 29 Jan 2016, at 10:02, Ted Yu <yu...@gmail.com> wrote:
>>>>
>>>> ZOOKEEPER-2355 is in Open state as of now.
>>>>
>>>> My two cents:
>>>>
>>>> 3.4.7 has been retracted.
>>>> It would be nice to get 3.4.8 out the door soon so that zookeeper users
>>>> can
>>>> pick up bug fixes in between 3.4.6 and 3.4 branch.
>>>>
>>>> On Thu, Jan 28, 2016 at 8:57 AM, Raúl Gutiérrez Segalés
>>>> <rgs@itevenworks.net
>>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> On 28 January 2016 at 07:07, Talluri, Chandra <
>>>>> Chandra.Talluri@fmr.com.invalid> wrote:
>>>>>
>>>>>> Thanks for the updates.
>>>>>>
>>>>>> When can we expect 3.4.8?
>>>>>>
>>>>>
>>>>> I think we need to decide if we want to include these patches:
>>>>>
>>>>> https://issues.apache.org/jira/browse/ZOOKEEPER-2355
>>>>> https://issues.apache.org/jira/browse/ZOOKEEPER-2247
>>>>>
>>>>> They seem to be almost ready, though there might be some subtleties
>>>>> left to
>>>>> be addressed.
>>>>>
>>>>>
>>>>>> What are the plans for 3.5.* stable version release?
>>>>>>
>>>>>
>>>>> The general plan for making 3.5 stable is here:
>>>>>
>>>>> http://markmail.org/message/ymxliy2rrwjc2pmo
>>>>>
>>>>> I believe Chris Nauroth will be the RM for the upcoming 3.5.2 release.
>>>>>
>>>>>
>>>>> -rgs
>>>>>
>>>
>>>
>>
>>
Re: 3.4.8 release
Posted by Raúl Gutiérrez Segalés <rg...@itevenworks.net>.
Ok - lets punt them to 3.4.9 then.
-rgs
On 29 January 2016 at 10:10, Chris Nauroth <cn...@hortonworks.com> wrote:
> +1 for expediting the 3.4.8 release. Our goal was simply to correct the
> critical bug discovered late in 3.4.7. Any patches more than that can be
> deferred to a 3.4.9 at a later date.
>
> --Chris Nauroth
>
>
>
>
> On 1/29/16, 10:06 AM, "Flavio Junqueira" <fp...@apache.org> wrote:
>
> >+1
> >
> >> On 29 Jan 2016, at 10:02, Ted Yu <yu...@gmail.com> wrote:
> >>
> >> ZOOKEEPER-2355 is in Open state as of now.
> >>
> >> My two cents:
> >>
> >> 3.4.7 has been retracted.
> >> It would be nice to get 3.4.8 out the door soon so that zookeeper users
> >>can
> >> pick up bug fixes in between 3.4.6 and 3.4 branch.
> >>
> >> On Thu, Jan 28, 2016 at 8:57 AM, Raúl Gutiérrez Segalés
> >><rgs@itevenworks.net
> >>> wrote:
> >>
> >>> Hi,
> >>>
> >>> On 28 January 2016 at 07:07, Talluri, Chandra <
> >>> Chandra.Talluri@fmr.com.invalid> wrote:
> >>>
> >>>> Thanks for the updates.
> >>>>
> >>>> When can we expect 3.4.8?
> >>>>
> >>>
> >>> I think we need to decide if we want to include these patches:
> >>>
> >>> https://issues.apache.org/jira/browse/ZOOKEEPER-2355
> >>> https://issues.apache.org/jira/browse/ZOOKEEPER-2247
> >>>
> >>> They seem to be almost ready, though there might be some subtleties
> >>>left to
> >>> be addressed.
> >>>
> >>>
> >>>> What are the plans for 3.5.* stable version release?
> >>>>
> >>>
> >>> The general plan for making 3.5 stable is here:
> >>>
> >>> http://markmail.org/message/ymxliy2rrwjc2pmo
> >>>
> >>> I believe Chris Nauroth will be the RM for the upcoming 3.5.2 release.
> >>>
> >>>
> >>> -rgs
> >>>
> >
> >
>
>
Re: 3.4.8 release
Posted by Raúl Gutiérrez Segalés <rg...@itevenworks.net>.
Ok - lets punt them to 3.4.9 then.
-rgs
On 29 January 2016 at 10:10, Chris Nauroth <cn...@hortonworks.com> wrote:
> +1 for expediting the 3.4.8 release. Our goal was simply to correct the
> critical bug discovered late in 3.4.7. Any patches more than that can be
> deferred to a 3.4.9 at a later date.
>
> --Chris Nauroth
>
>
>
>
> On 1/29/16, 10:06 AM, "Flavio Junqueira" <fp...@apache.org> wrote:
>
> >+1
> >
> >> On 29 Jan 2016, at 10:02, Ted Yu <yu...@gmail.com> wrote:
> >>
> >> ZOOKEEPER-2355 is in Open state as of now.
> >>
> >> My two cents:
> >>
> >> 3.4.7 has been retracted.
> >> It would be nice to get 3.4.8 out the door soon so that zookeeper users
> >>can
> >> pick up bug fixes in between 3.4.6 and 3.4 branch.
> >>
> >> On Thu, Jan 28, 2016 at 8:57 AM, Raúl Gutiérrez Segalés
> >><rgs@itevenworks.net
> >>> wrote:
> >>
> >>> Hi,
> >>>
> >>> On 28 January 2016 at 07:07, Talluri, Chandra <
> >>> Chandra.Talluri@fmr.com.invalid> wrote:
> >>>
> >>>> Thanks for the updates.
> >>>>
> >>>> When can we expect 3.4.8?
> >>>>
> >>>
> >>> I think we need to decide if we want to include these patches:
> >>>
> >>> https://issues.apache.org/jira/browse/ZOOKEEPER-2355
> >>> https://issues.apache.org/jira/browse/ZOOKEEPER-2247
> >>>
> >>> They seem to be almost ready, though there might be some subtleties
> >>>left to
> >>> be addressed.
> >>>
> >>>
> >>>> What are the plans for 3.5.* stable version release?
> >>>>
> >>>
> >>> The general plan for making 3.5 stable is here:
> >>>
> >>> http://markmail.org/message/ymxliy2rrwjc2pmo
> >>>
> >>> I believe Chris Nauroth will be the RM for the upcoming 3.5.2 release.
> >>>
> >>>
> >>> -rgs
> >>>
> >
> >
>
>
Re: 3.4.8 release
Posted by Chris Nauroth <cn...@hortonworks.com>.
+1 for expediting the 3.4.8 release. Our goal was simply to correct the
critical bug discovered late in 3.4.7. Any patches more than that can be
deferred to a 3.4.9 at a later date.
--Chris Nauroth
On 1/29/16, 10:06 AM, "Flavio Junqueira" <fp...@apache.org> wrote:
>+1
>
>> On 29 Jan 2016, at 10:02, Ted Yu <yu...@gmail.com> wrote:
>>
>> ZOOKEEPER-2355 is in Open state as of now.
>>
>> My two cents:
>>
>> 3.4.7 has been retracted.
>> It would be nice to get 3.4.8 out the door soon so that zookeeper users
>>can
>> pick up bug fixes in between 3.4.6 and 3.4 branch.
>>
>> On Thu, Jan 28, 2016 at 8:57 AM, Raúl Gutiérrez Segalés
>><rgs@itevenworks.net
>>> wrote:
>>
>>> Hi,
>>>
>>> On 28 January 2016 at 07:07, Talluri, Chandra <
>>> Chandra.Talluri@fmr.com.invalid> wrote:
>>>
>>>> Thanks for the updates.
>>>>
>>>> When can we expect 3.4.8?
>>>>
>>>
>>> I think we need to decide if we want to include these patches:
>>>
>>> https://issues.apache.org/jira/browse/ZOOKEEPER-2355
>>> https://issues.apache.org/jira/browse/ZOOKEEPER-2247
>>>
>>> They seem to be almost ready, though there might be some subtleties
>>>left to
>>> be addressed.
>>>
>>>
>>>> What are the plans for 3.5.* stable version release?
>>>>
>>>
>>> The general plan for making 3.5 stable is here:
>>>
>>> http://markmail.org/message/ymxliy2rrwjc2pmo
>>>
>>> I believe Chris Nauroth will be the RM for the upcoming 3.5.2 release.
>>>
>>>
>>> -rgs
>>>
>
>
Re: 3.4.8 release
Posted by Chris Nauroth <cn...@hortonworks.com>.
+1 for expediting the 3.4.8 release. Our goal was simply to correct the
critical bug discovered late in 3.4.7. Any patches more than that can be
deferred to a 3.4.9 at a later date.
--Chris Nauroth
On 1/29/16, 10:06 AM, "Flavio Junqueira" <fp...@apache.org> wrote:
>+1
>
>> On 29 Jan 2016, at 10:02, Ted Yu <yu...@gmail.com> wrote:
>>
>> ZOOKEEPER-2355 is in Open state as of now.
>>
>> My two cents:
>>
>> 3.4.7 has been retracted.
>> It would be nice to get 3.4.8 out the door soon so that zookeeper users
>>can
>> pick up bug fixes in between 3.4.6 and 3.4 branch.
>>
>> On Thu, Jan 28, 2016 at 8:57 AM, Raúl Gutiérrez Segalés
>><rgs@itevenworks.net
>>> wrote:
>>
>>> Hi,
>>>
>>> On 28 January 2016 at 07:07, Talluri, Chandra <
>>> Chandra.Talluri@fmr.com.invalid> wrote:
>>>
>>>> Thanks for the updates.
>>>>
>>>> When can we expect 3.4.8?
>>>>
>>>
>>> I think we need to decide if we want to include these patches:
>>>
>>> https://issues.apache.org/jira/browse/ZOOKEEPER-2355
>>> https://issues.apache.org/jira/browse/ZOOKEEPER-2247
>>>
>>> They seem to be almost ready, though there might be some subtleties
>>>left to
>>> be addressed.
>>>
>>>
>>>> What are the plans for 3.5.* stable version release?
>>>>
>>>
>>> The general plan for making 3.5 stable is here:
>>>
>>> http://markmail.org/message/ymxliy2rrwjc2pmo
>>>
>>> I believe Chris Nauroth will be the RM for the upcoming 3.5.2 release.
>>>
>>>
>>> -rgs
>>>
>
>
Re: 3.4.8 release
Posted by Flavio Junqueira <fp...@apache.org>.
+1
> On 29 Jan 2016, at 10:02, Ted Yu <yu...@gmail.com> wrote:
>
> ZOOKEEPER-2355 is in Open state as of now.
>
> My two cents:
>
> 3.4.7 has been retracted.
> It would be nice to get 3.4.8 out the door soon so that zookeeper users can
> pick up bug fixes in between 3.4.6 and 3.4 branch.
>
> On Thu, Jan 28, 2016 at 8:57 AM, Raúl Gutiérrez Segalés <rgs@itevenworks.net
>> wrote:
>
>> Hi,
>>
>> On 28 January 2016 at 07:07, Talluri, Chandra <
>> Chandra.Talluri@fmr.com.invalid> wrote:
>>
>>> Thanks for the updates.
>>>
>>> When can we expect 3.4.8?
>>>
>>
>> I think we need to decide if we want to include these patches:
>>
>> https://issues.apache.org/jira/browse/ZOOKEEPER-2355
>> https://issues.apache.org/jira/browse/ZOOKEEPER-2247
>>
>> They seem to be almost ready, though there might be some subtleties left to
>> be addressed.
>>
>>
>>> What are the plans for 3.5.* stable version release?
>>>
>>
>> The general plan for making 3.5 stable is here:
>>
>> http://markmail.org/message/ymxliy2rrwjc2pmo
>>
>> I believe Chris Nauroth will be the RM for the upcoming 3.5.2 release.
>>
>>
>> -rgs
>>
Re: 3.4.8 release
Posted by Flavio Junqueira <fp...@apache.org>.
+1
> On 29 Jan 2016, at 10:02, Ted Yu <yu...@gmail.com> wrote:
>
> ZOOKEEPER-2355 is in Open state as of now.
>
> My two cents:
>
> 3.4.7 has been retracted.
> It would be nice to get 3.4.8 out the door soon so that zookeeper users can
> pick up bug fixes in between 3.4.6 and 3.4 branch.
>
> On Thu, Jan 28, 2016 at 8:57 AM, Raúl Gutiérrez Segalés <rgs@itevenworks.net
>> wrote:
>
>> Hi,
>>
>> On 28 January 2016 at 07:07, Talluri, Chandra <
>> Chandra.Talluri@fmr.com.invalid> wrote:
>>
>>> Thanks for the updates.
>>>
>>> When can we expect 3.4.8?
>>>
>>
>> I think we need to decide if we want to include these patches:
>>
>> https://issues.apache.org/jira/browse/ZOOKEEPER-2355
>> https://issues.apache.org/jira/browse/ZOOKEEPER-2247
>>
>> They seem to be almost ready, though there might be some subtleties left to
>> be addressed.
>>
>>
>>> What are the plans for 3.5.* stable version release?
>>>
>>
>> The general plan for making 3.5 stable is here:
>>
>> http://markmail.org/message/ymxliy2rrwjc2pmo
>>
>> I believe Chris Nauroth will be the RM for the upcoming 3.5.2 release.
>>
>>
>> -rgs
>>
Re: 3.4.8 release
Posted by Ted Yu <yu...@gmail.com>.
ZOOKEEPER-2355 is in Open state as of now.
My two cents:
3.4.7 has been retracted.
It would be nice to get 3.4.8 out the door soon so that zookeeper users can
pick up bug fixes in between 3.4.6 and 3.4 branch.
On Thu, Jan 28, 2016 at 8:57 AM, Raúl Gutiérrez Segalés <rgs@itevenworks.net
> wrote:
> Hi,
>
> On 28 January 2016 at 07:07, Talluri, Chandra <
> Chandra.Talluri@fmr.com.invalid> wrote:
>
> > Thanks for the updates.
> >
> > When can we expect 3.4.8?
> >
>
> I think we need to decide if we want to include these patches:
>
> https://issues.apache.org/jira/browse/ZOOKEEPER-2355
> https://issues.apache.org/jira/browse/ZOOKEEPER-2247
>
> They seem to be almost ready, though there might be some subtleties left to
> be addressed.
>
>
> > What are the plans for 3.5.* stable version release?
> >
>
> The general plan for making 3.5 stable is here:
>
> http://markmail.org/message/ymxliy2rrwjc2pmo
>
> I believe Chris Nauroth will be the RM for the upcoming 3.5.2 release.
>
>
> -rgs
>
Re: 3.4.8 release
Posted by Ted Yu <yu...@gmail.com>.
ZOOKEEPER-2355 is in Open state as of now.
My two cents:
3.4.7 has been retracted.
It would be nice to get 3.4.8 out the door soon so that zookeeper users can
pick up bug fixes in between 3.4.6 and 3.4 branch.
On Thu, Jan 28, 2016 at 8:57 AM, Raúl Gutiérrez Segalés <rgs@itevenworks.net
> wrote:
> Hi,
>
> On 28 January 2016 at 07:07, Talluri, Chandra <
> Chandra.Talluri@fmr.com.invalid> wrote:
>
> > Thanks for the updates.
> >
> > When can we expect 3.4.8?
> >
>
> I think we need to decide if we want to include these patches:
>
> https://issues.apache.org/jira/browse/ZOOKEEPER-2355
> https://issues.apache.org/jira/browse/ZOOKEEPER-2247
>
> They seem to be almost ready, though there might be some subtleties left to
> be addressed.
>
>
> > What are the plans for 3.5.* stable version release?
> >
>
> The general plan for making 3.5 stable is here:
>
> http://markmail.org/message/ymxliy2rrwjc2pmo
>
> I believe Chris Nauroth will be the RM for the upcoming 3.5.2 release.
>
>
> -rgs
>
Re: 3.4.8 release
Posted by Raúl Gutiérrez Segalés <rg...@itevenworks.net>.
Hi,
On 28 January 2016 at 07:07, Talluri, Chandra <
Chandra.Talluri@fmr.com.invalid> wrote:
> Thanks for the updates.
>
> When can we expect 3.4.8?
>
I think we need to decide if we want to include these patches:
https://issues.apache.org/jira/browse/ZOOKEEPER-2355
https://issues.apache.org/jira/browse/ZOOKEEPER-2247
They seem to be almost ready, though there might be some subtleties left to
be addressed.
> What are the plans for 3.5.* stable version release?
>
The general plan for making 3.5 stable is here:
http://markmail.org/message/ymxliy2rrwjc2pmo
I believe Chris Nauroth will be the RM for the upcoming 3.5.2 release.
-rgs
Re: 3.4.8 release
Posted by Raúl Gutiérrez Segalés <rg...@itevenworks.net>.
Hi,
On 28 January 2016 at 07:07, Talluri, Chandra <
Chandra.Talluri@fmr.com.invalid> wrote:
> Thanks for the updates.
>
> When can we expect 3.4.8?
>
I think we need to decide if we want to include these patches:
https://issues.apache.org/jira/browse/ZOOKEEPER-2355
https://issues.apache.org/jira/browse/ZOOKEEPER-2247
They seem to be almost ready, though there might be some subtleties left to
be addressed.
> What are the plans for 3.5.* stable version release?
>
The general plan for making 3.5 stable is here:
http://markmail.org/message/ymxliy2rrwjc2pmo
I believe Chris Nauroth will be the RM for the upcoming 3.5.2 release.
-rgs
RE: 3.4.8 release
Posted by "Talluri, Chandra" <Ch...@FMR.com.INVALID>.
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:rakeshr.apache@gmail.com]
Sent: Tuesday, January 19, 2016 9:58 AM
To: user@zookeeper.apache.org
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 <fp...@apache.org> 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
> > <ra...@gmail.com>
> 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 <
> rgs@itevenworks.net
> >> 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
> >>
>
>
RE: 3.4.8 release
Posted by "Talluri, Chandra" <Ch...@FMR.com.INVALID>.
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:rakeshr.apache@gmail.com]
Sent: Tuesday, January 19, 2016 9:58 AM
To: user@zookeeper.apache.org
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 <fp...@apache.org> 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
> > <ra...@gmail.com>
> 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 <
> rgs@itevenworks.net
> >> 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
> >>
>
>
Re: 3.4.8 release
Posted by Rakesh Radhakrishnan <ra...@gmail.com>.
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 <fp...@apache.org> 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 <ra...@gmail.com>
> 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 <
> rgs@itevenworks.net
> >> 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
> >>
>
>
Re: 3.4.8 release
Posted by Rakesh Radhakrishnan <ra...@gmail.com>.
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 <fp...@apache.org> 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 <ra...@gmail.com>
> 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 <
> rgs@itevenworks.net
> >> 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
> >>
>
>
Re: 3.4.8 release
Posted by Flavio Junqueira <fp...@apache.org>.
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 <ra...@gmail.com> 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 <rgs@itevenworks.net
>> 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
>>
Re: 3.4.8 release
Posted by Flavio Junqueira <fp...@apache.org>.
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 <ra...@gmail.com> 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 <rgs@itevenworks.net
>> 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
>>
Re: 3.4.8 release
Posted by Rakesh Radhakrishnan <ra...@gmail.com>.
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 <rgs@itevenworks.net
> 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
>
Re: 3.4.8 release
Posted by Rakesh Radhakrishnan <ra...@gmail.com>.
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 <rgs@itevenworks.net
> 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
>