You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by Mahadev Konar <ma...@hortonworks.com> on 2011/08/02 04:49:58 UTC
Re: 3.4 Release.
Looks like jenkins is still having issues. Until then we can fix the
Open issues we have:
ZOOKEEPER-1125: Intermittent java core test failures
Vishal do you want to take this up?
ZOOKEEPER-839: Ill upload a patch by tonight.
ZOOKEEPER-1136. Ben would you be taking this up?
ZOOKEEPER-1055. Eugene, do you have sometime to take a look at this?
thanks
mahadev
On Fri, Jul 29, 2011 at 10:05 AM, Patrick Hunt <ph...@apache.org> wrote:
> I see that the Apache jenkins machines have been down for a couple
> days now, anyone have an idea when it will come back?
>
> I don't think we should commit code that hasn't gone through the patch
> test process, otw we're going to miss stuff. There's also the fact
> that the trunk job is not running either - as a result issues are
> likely to come in and be hard to diagnose later when jenkins does come
> back.
>
> I see there are currently 9 open issues for 3.4.0, great progress
> everyone! http://bit.ly/ovR7xg However, there are 4 open blockers, 3
> of which do not have anyone assigned to them. We need to nail these
> down so a release candidate can be cut.
>
> Patrick
>
> On Mon, Jul 25, 2011 at 1:27 PM, Mahadev Konar <ma...@hortonworks.com> wrote:
>> Thanks a ton Vishal!
>>
>> mahadev
>>
>> On Jul 25, 2011, at 10:49 AM, Vishal Kher wrote:
>>
>>> Hi Mahadev,
>>>
>>> ZOOKEEPER-1006 is fixed.
>>> ZOOKEEPER-1090<https://issues.apache.org/jira/browse/ZOOKEEPER-1090>should
>>> go in 3.4.0 as well.
>>> I have patch available on the jira. It is one liner.
>>>
>>> On Mon, Jul 18, 2011 at 3:35 AM, Mahadev Konar <ma...@hortonworks.com>wrote:
>>>
>>>> HI all,
>>>> The 3.4 release is making good progress. I think we are a week or so
>>>> away from the release getting out.
>>>> We have 11 open issues and 16 PA's.
>>>>
>>>> Most of the PA's are good to get in or are most likely to be
>>>> checked in by this week.
>>>>
>>>> For the Open issues:
>>>>
>>>> ZOOKEEPER-1155. Eugene/Vishal can you folks please take a look and
>>>> update the jira?
>>>> ZOOKEEPER-839. I am working on it.
>>>> ZOOKEEPER-736. Pat you want to give this a shot?
>>>> ZOOKEEPER-1055. I think Eugene is updating the fix.
>>>> ZOOKEEPER-1057. Waiting for an update. Most likely I will move it out to
>>>> 3.5.
>>>> ZOOKEEPER-1080. Looks like a duplicate of ZOOKEEPER-1095 (Thanks to
>>>> Aaron for pointing this out). Will most likely mark it as such.
>>>> ZOOKEEPER-1101. Is something that just needs to be done during the
>>>> release.
>>>> ZOOKEEPER-731. Anyone want to take a shot at this? Should be a very minor
>>>> fix.
>>>> ZOOKEEPER-1006. Pat/Vishal, Should this be marked resolved?
>>>> ZOOKEEPER-195. Can be most likely moved out unless someone steps up.
>>>> ZOOKEEPER-1104. Has a patch. Eugene, will you be able to update the
>>>> patch and mark it PA in case its uptodate?
>>>>
>>>>
>>>> Other than this, committers please help reviewing/committing the
>>>> patches that are in PA state.
>>>>
>>>> thanks
>>>> mahadev
>>>>
>>
>> Mahadev Konar
>> @mahadevkonar
>> Hortonworks
>>
>>
>>
>>
>
RE: 3.4 Release.
Posted by Laxman <la...@huawei.com>.
Ok. I agree that these are non-blockers for 3.4.
But IMO we don't need to hold these trivial fixes as a backlog for 3.5.
ZOOKEEPER-1107 : New Feature. Turned off by default. Review already
completed.
ZOOKEEPER-1025 : Trivial fix fox Cli.
Anyways, you can take a call whether to push them to 3.4
ZOOKEEPER-1140 : Sure. I will work on this.
-----Original Message-----
From: Mahadev Konar [mailto:mahadev@hortonworks.com]
Sent: Tuesday, August 02, 2011 11:51 AM
To: dev@zookeeper.apache.org
Subject: Re: 3.4 Release.
Hi Laxman,
The patches look good but I think we need to be careful on checkin in
patches for the 3.4 release. We havent had a release for a long time and I'd
prefer for anything (not a blocker and non critical features) to go into
3.5.
I am hopeful (if the jenkins servers are up) of cutting a branch this
week/weekend. We can check in your patches into 3.5 release.
As you mentioned ZOOKEEPER-1140 is a blocker. Your help would be very
useful!
thanks a lot
mahadev
On Aug 1, 2011, at 10:58 PM, Laxman wrote:
> Hi Mahadev,
>
> Please check if we can push the following issues into 3.4
> ZOOKEEPER-1107 : patch available
> ZOOKEEPER-1025 : patch available
> ZOOKEEPER-1137 : I'm working on this. Will upload a patch today.
>
>
> ZOOKEEPER-1140 : We must fix [blocker] for the release. I will take this
up
> with the help of Flavio.
>
> -----Original Message-----
> From: Mahadev Konar [mailto:mahadev@hortonworks.com]
> Sent: Tuesday, August 02, 2011 8:20 AM
> To: dev@zookeeper.apache.org
> Cc: Eugene Koontz; Vishal Kher; Benjamin Reed
> Subject: Re: 3.4 Release.
>
> Looks like jenkins is still having issues. Until then we can fix the
> Open issues we have:
>
> ZOOKEEPER-1125: Intermittent java core test failures
> Vishal do you want to take this up?
>
> ZOOKEEPER-839: Ill upload a patch by tonight.
>
> ZOOKEEPER-1136. Ben would you be taking this up?
>
> ZOOKEEPER-1055. Eugene, do you have sometime to take a look at this?
>
> thanks
> mahadev
>
>
> On Fri, Jul 29, 2011 at 10:05 AM, Patrick Hunt <ph...@apache.org> wrote:
>> I see that the Apache jenkins machines have been down for a couple
>> days now, anyone have an idea when it will come back?
>>
>> I don't think we should commit code that hasn't gone through the patch
>> test process, otw we're going to miss stuff. There's also the fact
>> that the trunk job is not running either - as a result issues are
>> likely to come in and be hard to diagnose later when jenkins does come
>> back.
>>
>> I see there are currently 9 open issues for 3.4.0, great progress
>> everyone! http://bit.ly/ovR7xg However, there are 4 open blockers, 3
>> of which do not have anyone assigned to them. We need to nail these
>> down so a release candidate can be cut.
>>
>> Patrick
>>
>> On Mon, Jul 25, 2011 at 1:27 PM, Mahadev Konar <ma...@hortonworks.com>
> wrote:
>>> Thanks a ton Vishal!
>>>
>>> mahadev
>>>
>>> On Jul 25, 2011, at 10:49 AM, Vishal Kher wrote:
>>>
>>>> Hi Mahadev,
>>>>
>>>> ZOOKEEPER-1006 is fixed.
>>>>
> ZOOKEEPER-1090<https://issues.apache.org/jira/browse/ZOOKEEPER-1090>should
>>>> go in 3.4.0 as well.
>>>> I have patch available on the jira. It is one liner.
>>>>
>>>> On Mon, Jul 18, 2011 at 3:35 AM, Mahadev Konar
> <ma...@hortonworks.com>wrote:
>>>>
>>>>> HI all,
>>>>> The 3.4 release is making good progress. I think we are a week or so
>>>>> away from the release getting out.
>>>>> We have 11 open issues and 16 PA's.
>>>>>
>>>>> Most of the PA's are good to get in or are most likely to be
>>>>> checked in by this week.
>>>>>
>>>>> For the Open issues:
>>>>>
>>>>> ZOOKEEPER-1155. Eugene/Vishal can you folks please take a look and
>>>>> update the jira?
>>>>> ZOOKEEPER-839. I am working on it.
>>>>> ZOOKEEPER-736. Pat you want to give this a shot?
>>>>> ZOOKEEPER-1055. I think Eugene is updating the fix.
>>>>> ZOOKEEPER-1057. Waiting for an update. Most likely I will move it out
> to
>>>>> 3.5.
>>>>> ZOOKEEPER-1080. Looks like a duplicate of ZOOKEEPER-1095 (Thanks to
>>>>> Aaron for pointing this out). Will most likely mark it as such.
>>>>> ZOOKEEPER-1101. Is something that just needs to be done during the
>>>>> release.
>>>>> ZOOKEEPER-731. Anyone want to take a shot at this? Should be a very
> minor
>>>>> fix.
>>>>> ZOOKEEPER-1006. Pat/Vishal, Should this be marked resolved?
>>>>> ZOOKEEPER-195. Can be most likely moved out unless someone steps up.
>>>>> ZOOKEEPER-1104. Has a patch. Eugene, will you be able to update the
>>>>> patch and mark it PA in case its uptodate?
>>>>>
>>>>>
>>>>> Other than this, committers please help reviewing/committing the
>>>>> patches that are in PA state.
>>>>>
>>>>> thanks
>>>>> mahadev
>>>>>
>>>
>>> Mahadev Konar
>>> @mahadevkonar
>>> Hortonworks
>>>
>>>
>>>
>>>
>>
>
Re: 3.4 Release.
Posted by Mahadev Konar <ma...@hortonworks.com>.
Hi Laxman,
The patches look good but I think we need to be careful on checkin in patches for the 3.4 release. We havent had a release for a long time and I'd prefer for anything (not a blocker and non critical features) to go into 3.5.
I am hopeful (if the jenkins servers are up) of cutting a branch this week/weekend. We can check in your patches into 3.5 release.
As you mentioned ZOOKEEPER-1140 is a blocker. Your help would be very useful!
thanks a lot
mahadev
On Aug 1, 2011, at 10:58 PM, Laxman wrote:
> Hi Mahadev,
>
> Please check if we can push the following issues into 3.4
> ZOOKEEPER-1107 : patch available
> ZOOKEEPER-1025 : patch available
> ZOOKEEPER-1137 : I'm working on this. Will upload a patch today.
>
>
> ZOOKEEPER-1140 : We must fix [blocker] for the release. I will take this up
> with the help of Flavio.
>
> -----Original Message-----
> From: Mahadev Konar [mailto:mahadev@hortonworks.com]
> Sent: Tuesday, August 02, 2011 8:20 AM
> To: dev@zookeeper.apache.org
> Cc: Eugene Koontz; Vishal Kher; Benjamin Reed
> Subject: Re: 3.4 Release.
>
> Looks like jenkins is still having issues. Until then we can fix the
> Open issues we have:
>
> ZOOKEEPER-1125: Intermittent java core test failures
> Vishal do you want to take this up?
>
> ZOOKEEPER-839: Ill upload a patch by tonight.
>
> ZOOKEEPER-1136. Ben would you be taking this up?
>
> ZOOKEEPER-1055. Eugene, do you have sometime to take a look at this?
>
> thanks
> mahadev
>
>
> On Fri, Jul 29, 2011 at 10:05 AM, Patrick Hunt <ph...@apache.org> wrote:
>> I see that the Apache jenkins machines have been down for a couple
>> days now, anyone have an idea when it will come back?
>>
>> I don't think we should commit code that hasn't gone through the patch
>> test process, otw we're going to miss stuff. There's also the fact
>> that the trunk job is not running either - as a result issues are
>> likely to come in and be hard to diagnose later when jenkins does come
>> back.
>>
>> I see there are currently 9 open issues for 3.4.0, great progress
>> everyone! http://bit.ly/ovR7xg However, there are 4 open blockers, 3
>> of which do not have anyone assigned to them. We need to nail these
>> down so a release candidate can be cut.
>>
>> Patrick
>>
>> On Mon, Jul 25, 2011 at 1:27 PM, Mahadev Konar <ma...@hortonworks.com>
> wrote:
>>> Thanks a ton Vishal!
>>>
>>> mahadev
>>>
>>> On Jul 25, 2011, at 10:49 AM, Vishal Kher wrote:
>>>
>>>> Hi Mahadev,
>>>>
>>>> ZOOKEEPER-1006 is fixed.
>>>>
> ZOOKEEPER-1090<https://issues.apache.org/jira/browse/ZOOKEEPER-1090>should
>>>> go in 3.4.0 as well.
>>>> I have patch available on the jira. It is one liner.
>>>>
>>>> On Mon, Jul 18, 2011 at 3:35 AM, Mahadev Konar
> <ma...@hortonworks.com>wrote:
>>>>
>>>>> HI all,
>>>>> The 3.4 release is making good progress. I think we are a week or so
>>>>> away from the release getting out.
>>>>> We have 11 open issues and 16 PA's.
>>>>>
>>>>> Most of the PA's are good to get in or are most likely to be
>>>>> checked in by this week.
>>>>>
>>>>> For the Open issues:
>>>>>
>>>>> ZOOKEEPER-1155. Eugene/Vishal can you folks please take a look and
>>>>> update the jira?
>>>>> ZOOKEEPER-839. I am working on it.
>>>>> ZOOKEEPER-736. Pat you want to give this a shot?
>>>>> ZOOKEEPER-1055. I think Eugene is updating the fix.
>>>>> ZOOKEEPER-1057. Waiting for an update. Most likely I will move it out
> to
>>>>> 3.5.
>>>>> ZOOKEEPER-1080. Looks like a duplicate of ZOOKEEPER-1095 (Thanks to
>>>>> Aaron for pointing this out). Will most likely mark it as such.
>>>>> ZOOKEEPER-1101. Is something that just needs to be done during the
>>>>> release.
>>>>> ZOOKEEPER-731. Anyone want to take a shot at this? Should be a very
> minor
>>>>> fix.
>>>>> ZOOKEEPER-1006. Pat/Vishal, Should this be marked resolved?
>>>>> ZOOKEEPER-195. Can be most likely moved out unless someone steps up.
>>>>> ZOOKEEPER-1104. Has a patch. Eugene, will you be able to update the
>>>>> patch and mark it PA in case its uptodate?
>>>>>
>>>>>
>>>>> Other than this, committers please help reviewing/committing the
>>>>> patches that are in PA state.
>>>>>
>>>>> thanks
>>>>> mahadev
>>>>>
>>>
>>> Mahadev Konar
>>> @mahadevkonar
>>> Hortonworks
>>>
>>>
>>>
>>>
>>
>
RE: 3.4 Release.
Posted by Laxman <la...@huawei.com>.
Hi Mahadev,
Please check if we can push the following issues into 3.4
ZOOKEEPER-1107 : patch available
ZOOKEEPER-1025 : patch available
ZOOKEEPER-1137 : I'm working on this. Will upload a patch today.
ZOOKEEPER-1140 : We must fix [blocker] for the release. I will take this up
with the help of Flavio.
-----Original Message-----
From: Mahadev Konar [mailto:mahadev@hortonworks.com]
Sent: Tuesday, August 02, 2011 8:20 AM
To: dev@zookeeper.apache.org
Cc: Eugene Koontz; Vishal Kher; Benjamin Reed
Subject: Re: 3.4 Release.
Looks like jenkins is still having issues. Until then we can fix the
Open issues we have:
ZOOKEEPER-1125: Intermittent java core test failures
Vishal do you want to take this up?
ZOOKEEPER-839: Ill upload a patch by tonight.
ZOOKEEPER-1136. Ben would you be taking this up?
ZOOKEEPER-1055. Eugene, do you have sometime to take a look at this?
thanks
mahadev
On Fri, Jul 29, 2011 at 10:05 AM, Patrick Hunt <ph...@apache.org> wrote:
> I see that the Apache jenkins machines have been down for a couple
> days now, anyone have an idea when it will come back?
>
> I don't think we should commit code that hasn't gone through the patch
> test process, otw we're going to miss stuff. There's also the fact
> that the trunk job is not running either - as a result issues are
> likely to come in and be hard to diagnose later when jenkins does come
> back.
>
> I see there are currently 9 open issues for 3.4.0, great progress
> everyone! http://bit.ly/ovR7xg However, there are 4 open blockers, 3
> of which do not have anyone assigned to them. We need to nail these
> down so a release candidate can be cut.
>
> Patrick
>
> On Mon, Jul 25, 2011 at 1:27 PM, Mahadev Konar <ma...@hortonworks.com>
wrote:
>> Thanks a ton Vishal!
>>
>> mahadev
>>
>> On Jul 25, 2011, at 10:49 AM, Vishal Kher wrote:
>>
>>> Hi Mahadev,
>>>
>>> ZOOKEEPER-1006 is fixed.
>>>
ZOOKEEPER-1090<https://issues.apache.org/jira/browse/ZOOKEEPER-1090>should
>>> go in 3.4.0 as well.
>>> I have patch available on the jira. It is one liner.
>>>
>>> On Mon, Jul 18, 2011 at 3:35 AM, Mahadev Konar
<ma...@hortonworks.com>wrote:
>>>
>>>> HI all,
>>>> The 3.4 release is making good progress. I think we are a week or so
>>>> away from the release getting out.
>>>> We have 11 open issues and 16 PA's.
>>>>
>>>> Most of the PA's are good to get in or are most likely to be
>>>> checked in by this week.
>>>>
>>>> For the Open issues:
>>>>
>>>> ZOOKEEPER-1155. Eugene/Vishal can you folks please take a look and
>>>> update the jira?
>>>> ZOOKEEPER-839. I am working on it.
>>>> ZOOKEEPER-736. Pat you want to give this a shot?
>>>> ZOOKEEPER-1055. I think Eugene is updating the fix.
>>>> ZOOKEEPER-1057. Waiting for an update. Most likely I will move it out
to
>>>> 3.5.
>>>> ZOOKEEPER-1080. Looks like a duplicate of ZOOKEEPER-1095 (Thanks to
>>>> Aaron for pointing this out). Will most likely mark it as such.
>>>> ZOOKEEPER-1101. Is something that just needs to be done during the
>>>> release.
>>>> ZOOKEEPER-731. Anyone want to take a shot at this? Should be a very
minor
>>>> fix.
>>>> ZOOKEEPER-1006. Pat/Vishal, Should this be marked resolved?
>>>> ZOOKEEPER-195. Can be most likely moved out unless someone steps up.
>>>> ZOOKEEPER-1104. Has a patch. Eugene, will you be able to update the
>>>> patch and mark it PA in case its uptodate?
>>>>
>>>>
>>>> Other than this, committers please help reviewing/committing the
>>>> patches that are in PA state.
>>>>
>>>> thanks
>>>> mahadev
>>>>
>>
>> Mahadev Konar
>> @mahadevkonar
>> Hortonworks
>>
>>
>>
>>
>
Re: 3.4 Release.
Posted by Mahadev Konar <ma...@hortonworks.com>.
I think Pat was seeing them as well. Pat?
mahadev
On Tue, Aug 2, 2011 at 7:48 AM, Vishal Kher <vi...@gmail.com> wrote:
>
> Hi,
>
> On Mon, Aug 1, 2011 at 10:49 PM, Mahadev Konar <ma...@hortonworks.com>
> wrote:
>>
>> Looks like jenkins is still having issues. Until then we can fix the
>> Open issues we have:
>>
>> ZOOKEEPER-1125: Intermittent java core test failures
>> Vishal do you want to take this up?
>>
>
> Sure. Am I the only one seeing this failure?
>
>>
>> ZOOKEEPER-839: Ill upload a patch by tonight.
>>
>> ZOOKEEPER-1136. Ben would you be taking this up?
>>
>> ZOOKEEPER-1055. Eugene, do you have sometime to take a look at this?
>>
>> thanks
>> mahadev
>>
>>
>> On Fri, Jul 29, 2011 at 10:05 AM, Patrick Hunt <ph...@apache.org> wrote:
>> > I see that the Apache jenkins machines have been down for a couple
>> > days now, anyone have an idea when it will come back?
>> >
>> > I don't think we should commit code that hasn't gone through the patch
>> > test process, otw we're going to miss stuff. There's also the fact
>> > that the trunk job is not running either - as a result issues are
>> > likely to come in and be hard to diagnose later when jenkins does come
>> > back.
>> >
>> > I see there are currently 9 open issues for 3.4.0, great progress
>> > everyone! http://bit.ly/ovR7xg However, there are 4 open blockers, 3
>> > of which do not have anyone assigned to them. We need to nail these
>> > down so a release candidate can be cut.
>> >
>> > Patrick
>> >
>> > On Mon, Jul 25, 2011 at 1:27 PM, Mahadev Konar <ma...@hortonworks.com>
>> > wrote:
>> >> Thanks a ton Vishal!
>> >>
>> >> mahadev
>> >>
>> >> On Jul 25, 2011, at 10:49 AM, Vishal Kher wrote:
>> >>
>> >>> Hi Mahadev,
>> >>>
>> >>> ZOOKEEPER-1006 is fixed.
>> >>>
>> >>> ZOOKEEPER-1090<https://issues.apache.org/jira/browse/ZOOKEEPER-1090>should
>> >>> go in 3.4.0 as well.
>> >>> I have patch available on the jira. It is one liner.
>> >>>
>> >>> On Mon, Jul 18, 2011 at 3:35 AM, Mahadev Konar
>> >>> <ma...@hortonworks.com>wrote:
>> >>>
>> >>>> HI all,
>> >>>> The 3.4 release is making good progress. I think we are a week or so
>> >>>> away from the release getting out.
>> >>>> We have 11 open issues and 16 PA's.
>> >>>>
>> >>>> Most of the PA's are good to get in or are most likely to be
>> >>>> checked in by this week.
>> >>>>
>> >>>> For the Open issues:
>> >>>>
>> >>>> ZOOKEEPER-1155. Eugene/Vishal can you folks please take a look and
>> >>>> update the jira?
>> >>>> ZOOKEEPER-839. I am working on it.
>> >>>> ZOOKEEPER-736. Pat you want to give this a shot?
>> >>>> ZOOKEEPER-1055. I think Eugene is updating the fix.
>> >>>> ZOOKEEPER-1057. Waiting for an update. Most likely I will move it out
>> >>>> to
>> >>>> 3.5.
>> >>>> ZOOKEEPER-1080. Looks like a duplicate of ZOOKEEPER-1095 (Thanks to
>> >>>> Aaron for pointing this out). Will most likely mark it as such.
>> >>>> ZOOKEEPER-1101. Is something that just needs to be done during the
>> >>>> release.
>> >>>> ZOOKEEPER-731. Anyone want to take a shot at this? Should be a very
>> >>>> minor
>> >>>> fix.
>> >>>> ZOOKEEPER-1006. Pat/Vishal, Should this be marked resolved?
>> >>>> ZOOKEEPER-195. Can be most likely moved out unless someone steps up.
>> >>>> ZOOKEEPER-1104. Has a patch. Eugene, will you be able to update the
>> >>>> patch and mark it PA in case its uptodate?
>> >>>>
>> >>>>
>> >>>> Other than this, committers please help reviewing/committing the
>> >>>> patches that are in PA state.
>> >>>>
>> >>>> thanks
>> >>>> mahadev
>> >>>>
>> >>
>> >> Mahadev Konar
>> >> @mahadevkonar
>> >> Hortonworks
>> >>
>> >>
>> >>
>> >>
>> >
>
>
RE: 3.4 Release.
Posted by "Fournier, Camille F." <Ca...@gs.com>.
---
Hi,
On Mon, Aug 1, 2011 at 10:49 PM, Mahadev Konar <ma...@hortonworks.com>wrote:
> Looks like jenkins is still having issues. Until then we can fix the
> Open issues we have:
>
> ZOOKEEPER-1125: Intermittent java core test failures
> Vishal do you want to take this up?
>
>
Sure. Am I the only one seeing this failure?
---
No, I've seen it on my home box as well. I thought I had a fix for the RwServer test, specifically, waiting for a RWConnect, instead of just a connect (because of timing, you could get a read-only connection before getting a RW connection), but it didn't seem to fix the issue on my local machine reliably, so there's more than that.
C
-----Original Message-----
From: Vishal Kher [mailto:vishalmlst@gmail.com]
Sent: Tuesday, August 02, 2011 10:49 AM
To: Mahadev Konar
Cc: dev@zookeeper.apache.org; Eugene Koontz; Benjamin Reed
Subject: Re: 3.4 Release.
Hi,
On Mon, Aug 1, 2011 at 10:49 PM, Mahadev Konar <ma...@hortonworks.com>wrote:
> Looks like jenkins is still having issues. Until then we can fix the
> Open issues we have:
>
> ZOOKEEPER-1125: Intermittent java core test failures
> Vishal do you want to take this up?
>
>
Sure. Am I the only one seeing this failure?
> ZOOKEEPER-839: Ill upload a patch by tonight.
>
> ZOOKEEPER-1136. Ben would you be taking this up?
>
> ZOOKEEPER-1055. Eugene, do you have sometime to take a look at this?
>
> thanks
> mahadev
>
>
> On Fri, Jul 29, 2011 at 10:05 AM, Patrick Hunt <ph...@apache.org> wrote:
> > I see that the Apache jenkins machines have been down for a couple
> > days now, anyone have an idea when it will come back?
> >
> > I don't think we should commit code that hasn't gone through the patch
> > test process, otw we're going to miss stuff. There's also the fact
> > that the trunk job is not running either - as a result issues are
> > likely to come in and be hard to diagnose later when jenkins does come
> > back.
> >
> > I see there are currently 9 open issues for 3.4.0, great progress
> > everyone! http://bit.ly/ovR7xg However, there are 4 open blockers, 3
> > of which do not have anyone assigned to them. We need to nail these
> > down so a release candidate can be cut.
> >
> > Patrick
> >
> > On Mon, Jul 25, 2011 at 1:27 PM, Mahadev Konar <ma...@hortonworks.com>
> wrote:
> >> Thanks a ton Vishal!
> >>
> >> mahadev
> >>
> >> On Jul 25, 2011, at 10:49 AM, Vishal Kher wrote:
> >>
> >>> Hi Mahadev,
> >>>
> >>> ZOOKEEPER-1006 is fixed.
> >>> ZOOKEEPER-1090<https://issues.apache.org/jira/browse/ZOOKEEPER-1090
> >should
> >>> go in 3.4.0 as well.
> >>> I have patch available on the jira. It is one liner.
> >>>
> >>> On Mon, Jul 18, 2011 at 3:35 AM, Mahadev Konar <
> mahadev@hortonworks.com>wrote:
> >>>
> >>>> HI all,
> >>>> The 3.4 release is making good progress. I think we are a week or so
> >>>> away from the release getting out.
> >>>> We have 11 open issues and 16 PA's.
> >>>>
> >>>> Most of the PA's are good to get in or are most likely to be
> >>>> checked in by this week.
> >>>>
> >>>> For the Open issues:
> >>>>
> >>>> ZOOKEEPER-1155. Eugene/Vishal can you folks please take a look and
> >>>> update the jira?
> >>>> ZOOKEEPER-839. I am working on it.
> >>>> ZOOKEEPER-736. Pat you want to give this a shot?
> >>>> ZOOKEEPER-1055. I think Eugene is updating the fix.
> >>>> ZOOKEEPER-1057. Waiting for an update. Most likely I will move it out
> to
> >>>> 3.5.
> >>>> ZOOKEEPER-1080. Looks like a duplicate of ZOOKEEPER-1095 (Thanks to
> >>>> Aaron for pointing this out). Will most likely mark it as such.
> >>>> ZOOKEEPER-1101. Is something that just needs to be done during the
> >>>> release.
> >>>> ZOOKEEPER-731. Anyone want to take a shot at this? Should be a very
> minor
> >>>> fix.
> >>>> ZOOKEEPER-1006. Pat/Vishal, Should this be marked resolved?
> >>>> ZOOKEEPER-195. Can be most likely moved out unless someone steps up.
> >>>> ZOOKEEPER-1104. Has a patch. Eugene, will you be able to update the
> >>>> patch and mark it PA in case its uptodate?
> >>>>
> >>>>
> >>>> Other than this, committers please help reviewing/committing the
> >>>> patches that are in PA state.
> >>>>
> >>>> thanks
> >>>> mahadev
> >>>>
> >>
> >> Mahadev Konar
> >> @mahadevkonar
> >> Hortonworks
> >>
> >>
> >>
> >>
> >
>
Re: 3.4 Release.
Posted by Vishal Kher <vi...@gmail.com>.
Hi,
On Mon, Aug 1, 2011 at 10:49 PM, Mahadev Konar <ma...@hortonworks.com>wrote:
> Looks like jenkins is still having issues. Until then we can fix the
> Open issues we have:
>
> ZOOKEEPER-1125: Intermittent java core test failures
> Vishal do you want to take this up?
>
>
Sure. Am I the only one seeing this failure?
> ZOOKEEPER-839: Ill upload a patch by tonight.
>
> ZOOKEEPER-1136. Ben would you be taking this up?
>
> ZOOKEEPER-1055. Eugene, do you have sometime to take a look at this?
>
> thanks
> mahadev
>
>
> On Fri, Jul 29, 2011 at 10:05 AM, Patrick Hunt <ph...@apache.org> wrote:
> > I see that the Apache jenkins machines have been down for a couple
> > days now, anyone have an idea when it will come back?
> >
> > I don't think we should commit code that hasn't gone through the patch
> > test process, otw we're going to miss stuff. There's also the fact
> > that the trunk job is not running either - as a result issues are
> > likely to come in and be hard to diagnose later when jenkins does come
> > back.
> >
> > I see there are currently 9 open issues for 3.4.0, great progress
> > everyone! http://bit.ly/ovR7xg However, there are 4 open blockers, 3
> > of which do not have anyone assigned to them. We need to nail these
> > down so a release candidate can be cut.
> >
> > Patrick
> >
> > On Mon, Jul 25, 2011 at 1:27 PM, Mahadev Konar <ma...@hortonworks.com>
> wrote:
> >> Thanks a ton Vishal!
> >>
> >> mahadev
> >>
> >> On Jul 25, 2011, at 10:49 AM, Vishal Kher wrote:
> >>
> >>> Hi Mahadev,
> >>>
> >>> ZOOKEEPER-1006 is fixed.
> >>> ZOOKEEPER-1090<https://issues.apache.org/jira/browse/ZOOKEEPER-1090
> >should
> >>> go in 3.4.0 as well.
> >>> I have patch available on the jira. It is one liner.
> >>>
> >>> On Mon, Jul 18, 2011 at 3:35 AM, Mahadev Konar <
> mahadev@hortonworks.com>wrote:
> >>>
> >>>> HI all,
> >>>> The 3.4 release is making good progress. I think we are a week or so
> >>>> away from the release getting out.
> >>>> We have 11 open issues and 16 PA's.
> >>>>
> >>>> Most of the PA's are good to get in or are most likely to be
> >>>> checked in by this week.
> >>>>
> >>>> For the Open issues:
> >>>>
> >>>> ZOOKEEPER-1155. Eugene/Vishal can you folks please take a look and
> >>>> update the jira?
> >>>> ZOOKEEPER-839. I am working on it.
> >>>> ZOOKEEPER-736. Pat you want to give this a shot?
> >>>> ZOOKEEPER-1055. I think Eugene is updating the fix.
> >>>> ZOOKEEPER-1057. Waiting for an update. Most likely I will move it out
> to
> >>>> 3.5.
> >>>> ZOOKEEPER-1080. Looks like a duplicate of ZOOKEEPER-1095 (Thanks to
> >>>> Aaron for pointing this out). Will most likely mark it as such.
> >>>> ZOOKEEPER-1101. Is something that just needs to be done during the
> >>>> release.
> >>>> ZOOKEEPER-731. Anyone want to take a shot at this? Should be a very
> minor
> >>>> fix.
> >>>> ZOOKEEPER-1006. Pat/Vishal, Should this be marked resolved?
> >>>> ZOOKEEPER-195. Can be most likely moved out unless someone steps up.
> >>>> ZOOKEEPER-1104. Has a patch. Eugene, will you be able to update the
> >>>> patch and mark it PA in case its uptodate?
> >>>>
> >>>>
> >>>> Other than this, committers please help reviewing/committing the
> >>>> patches that are in PA state.
> >>>>
> >>>> thanks
> >>>> mahadev
> >>>>
> >>
> >> Mahadev Konar
> >> @mahadevkonar
> >> Hortonworks
> >>
> >>
> >>
> >>
> >
>
Re: 3.4 Release.
Posted by Eugene Koontz <ek...@hiro-tan.org>.
On 08/05/2011 11:47 AM, Fournier, Camille F. wrote:
> I might have time this weekend to look at some of this. If I do, I will keep you guys in the loop.
>
> C
>
Thanks Camille,
Much appreciated.
-Eugene
Re: 3.4 Release.
Posted by Eugene Koontz <ek...@hiro-tan.org>.
On 08/05/2011 04:41 PM, Vishal Kher wrote:
> Sorry, I meant to say 1144 instead of 1145 in my earlier mail :-) I will
> fix 1144.
> Eugene, you can leave 1145 assigned to me for now. If 1144 doesn't resolve
> it, I will assign it back to you :-)
Thanks, sounds fine, Vishal, feel free to assign back to me.
-Eugene
Re: 3.4 Release.
Posted by Vishal Kher <vi...@gmail.com>.
Sorry, I meant to say 1144 instead of 1145 in my earlier mail :-) I will
fix 1144.
Eugene, you can leave 1145 assigned to me for now. If 1144 doesn't resolve
it, I will assign it back to you :-)
On Fri, Aug 5, 2011 at 7:28 PM, Eugene Koontz <ek...@hiro-tan.org> wrote:
> On 8/5/11 4:03 PM, Vishal Kher wrote:
>
>> Thanks, Camille. I am pretty sure that the bug that Eugene is seeing is
>> because of 1145 as well. In the interest of time, I wanted to make sure
>> that I wasn't doing the same changes that Eugene was working on. I will
>> fix
>> 1145 since I had spent some time debugging it and have a fair idea of the
>> fix. I think we need help with the other tests (though they could be
>> failing because of 1145).
>>
>> -Vishal
>>
>>
>> Thanks Vishal; I will reassign 1145 to you.
> -Eugene
>
Re: 3.4 Release.
Posted by Eugene Koontz <ek...@hiro-tan.org>.
On 8/5/11 4:03 PM, Vishal Kher wrote:
> Thanks, Camille. I am pretty sure that the bug that Eugene is seeing is
> because of 1145 as well. In the interest of time, I wanted to make sure
> that I wasn't doing the same changes that Eugene was working on. I will fix
> 1145 since I had spent some time debugging it and have a fair idea of the
> fix. I think we need help with the other tests (though they could be
> failing because of 1145).
>
> -Vishal
>
>
Thanks Vishal; I will reassign 1145 to you.
-Eugene
Re: 3.4 Release.
Posted by Vishal Kher <vi...@gmail.com>.
Thanks, Camille. I am pretty sure that the bug that Eugene is seeing is
because of 1145 as well. In the interest of time, I wanted to make sure
that I wasn't doing the same changes that Eugene was working on. I will fix
1145 since I had spent some time debugging it and have a fair idea of the
fix. I think we need help with the other tests (though they could be
failing because of 1145).
-Vishal
On Fri, Aug 5, 2011 at 2:47 PM, Fournier, Camille F. <
Camille.Fournier@gs.com> wrote:
> I might have time this weekend to look at some of this. If I do, I will
> keep you guys in the loop.
>
> C
>
> -----Original Message-----
> From: Eugene Koontz [mailto:ekoontz@hiro-tan.org]
> Sent: Friday, August 05, 2011 2:02 PM
> To: dev@zookeeper.apache.org
> Subject: Re: 3.4 Release.
>
> On 8/4/11 4:48 PM, Vishal Kher wrote:
> > Is your fix for 1145 also going to fix 1144 (are you fixing the Leader)?
> >
> Hi Vishal,
> I'm not at all sure yet..will update the 1145 when I have a chance
> to look at it next week.
> -Eugene
>
Re: 3.4 Release.
Posted by Mahadev Konar <ma...@hortonworks.com>.
Thats great!
mahadev
On Fri, Aug 5, 2011 at 11:47 AM, Fournier, Camille F. <
Camille.Fournier@gs.com> wrote:
> I might have time this weekend to look at some of this. If I do, I will
> keep you guys in the loop.
>
> C
>
> -----Original Message-----
> From: Eugene Koontz [mailto:ekoontz@hiro-tan.org]
> Sent: Friday, August 05, 2011 2:02 PM
> To: dev@zookeeper.apache.org
> Subject: Re: 3.4 Release.
>
> On 8/4/11 4:48 PM, Vishal Kher wrote:
> > Is your fix for 1145 also going to fix 1144 (are you fixing the Leader)?
> >
> Hi Vishal,
> I'm not at all sure yet..will update the 1145 when I have a chance
> to look at it next week.
> -Eugene
>
RE: 3.4 Release.
Posted by "Fournier, Camille F." <Ca...@gs.com>.
I might have time this weekend to look at some of this. If I do, I will keep you guys in the loop.
C
-----Original Message-----
From: Eugene Koontz [mailto:ekoontz@hiro-tan.org]
Sent: Friday, August 05, 2011 2:02 PM
To: dev@zookeeper.apache.org
Subject: Re: 3.4 Release.
On 8/4/11 4:48 PM, Vishal Kher wrote:
> Is your fix for 1145 also going to fix 1144 (are you fixing the Leader)?
>
Hi Vishal,
I'm not at all sure yet..will update the 1145 when I have a chance
to look at it next week.
-Eugene
Re: 3.4 Release.
Posted by Eugene Koontz <ek...@hiro-tan.org>.
On 8/4/11 4:48 PM, Vishal Kher wrote:
> Is your fix for 1145 also going to fix 1144 (are you fixing the Leader)?
>
Hi Vishal,
I'm not at all sure yet..will update the 1145 when I have a chance
to look at it next week.
-Eugene
Re: 3.4 Release.
Posted by Vishal Kher <vi...@gmail.com>.
Hi Eugene,
On Thu, Aug 4, 2011 at 1:46 PM, Eugene Koontz <ek...@hiro-tan.org> wrote:
> On 08/03/2011 07:23 PM, Mahadev Konar wrote:
>
>> Thanks Vishal and Eugene.
>>
>> I am still waiting on the jenkins builds. Are you guys planning to work on
>> ZOOKEEPER-1144<https://issues.**apache.org/jira/browse/**ZOOKEEPER-1144<https://issues.apache.org/jira/browse/ZOOKEEPER-1144>
>> >/1145?
>>
>> thanks
>> mahadev
>>
> Sure, I'll assign ZOOKEEPER-1145 to myself.
>
>
Is your fix for 1145 also going to fix 1144 (are you fixing the Leader)?
> -Eugene
>
Re: 3.4 Release.
Posted by Eugene Koontz <ek...@hiro-tan.org>.
On 08/03/2011 07:23 PM, Mahadev Konar wrote:
> Thanks Vishal and Eugene.
>
> I am still waiting on the jenkins builds. Are you guys planning to work on
> ZOOKEEPER-1144<https://issues.apache.org/jira/browse/ZOOKEEPER-1144>/1145?
>
> thanks
> mahadev
Sure, I'll assign ZOOKEEPER-1145 to myself.
-Eugene
Re: 3.4 Release.
Posted by Mahadev Konar <ma...@hortonworks.com>.
Thanks Vishal and Eugene.
I am still waiting on the jenkins builds. Are you guys planning to work on
ZOOKEEPER-1144 <https://issues.apache.org/jira/browse/ZOOKEEPER-1144>/1145?
thanks
mahadev
On Wed, Aug 3, 2011 at 3:39 PM, Eugene Koontz <ek...@hiro-tan.org> wrote:
> On 08/03/2011 09:32 AM, Patrick Hunt wrote:
>
>>
>> Please file a bug on this. Blocker for 3.4.0.
>>
>> Hi Patrick,
>
> Filed the bug here: https://issues.apache.org/**jira/browse/ZOOKEEPER-1145<https://issues.apache.org/jira/browse/ZOOKEEPER-1145>
>
>
> Can you try re-running your test, but modify it to attempt to have a
>> client connect to a non-observer in the case that connecting to the
>> observer fails? It would be interesting to see if this was an observer
>> specific issue or not. (another thing perhaps to try is just have the
>> existing client connect to a non-observer rather than the observer,
>> run it a bunch of times and see if it happens)
>>
> Thanks for these leads; I will try to investigate these and see if I can
> get some more insight into what's going on.
>
> -Eugene
>
Re: 3.4 Release.
Posted by Eugene Koontz <ek...@hiro-tan.org>.
On 08/03/2011 09:32 AM, Patrick Hunt wrote:
>
> Please file a bug on this. Blocker for 3.4.0.
>
Hi Patrick,
Filed the bug here: https://issues.apache.org/jira/browse/ZOOKEEPER-1145
> Can you try re-running your test, but modify it to attempt to have a
> client connect to a non-observer in the case that connecting to the
> observer fails? It would be interesting to see if this was an observer
> specific issue or not. (another thing perhaps to try is just have the
> existing client connect to a non-observer rather than the observer,
> run it a bunch of times and see if it happens)
Thanks for these leads; I will try to investigate these and see if I can
get some more insight into what's going on.
-Eugene
Re: 3.4 Release.
Posted by Vishal Kher <vi...@gmail.com>.
I found one problem - https://issues.apache.org/jira/browse/ZOOKEEPER-1144
I am not sure if this is causing Euguene's test to fail as well.
On Wed, Aug 3, 2011 at 12:32 PM, Patrick Hunt <ph...@apache.org> wrote:
> Seems the observer (or the quorum itself) is failing to allow a client
> to connect:
>
> [junit] 2011-08-03 14:12:29,273 [myid:3] - INFO
> [QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:11229:QuorumPeer@701] - OBSERVING
> ....
> [junit] 2011-08-03 14:12:29,359 [myid:] - INFO
> [main:ZooKeeper@427] - Initiating client connection,
> connectString=127.0.0.1:11229 sessionTimeout=30000
> watcher=org.apache.zookeeper.test.ObserverTest@6490832e
> [junit] 2011-08-03 14:12:29,378 [myid:] - INFO
> [main-SendThread():ClientCnxn$SendThread@888] - Opening socket
> connection to server /127.0.0.1:11229
> [junit] 2011-08-03 14:12:29,379 [myid:3] - INFO
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11229:NIOServerCnxnFactory@197]
> - Accepted socket connection from /127.0.0.1:56250
> [junit] 2011-08-03 14:12:29,379 [myid:] - INFO
> [main-SendThread(localhost:11229):ClientCnxn$SendThread@814] - Socket
> connection established to localhost/127.0.0.1:11229, initiating
> session
> [junit] 2011-08-03 14:12:29,380 [myid:3] - INFO
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11229:ZooKeeperServer@833] -
> Client attempting to establish new session at /127.0.0.1:56250
> [junit] 2011-08-03 14:12:53,356 [myid:2] - INFO
> [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:11228:Leader@419] - Shutting down
>
> Notice that last line, ~24 seconds go by.
>
> Please file a bug on this. Blocker for 3.4.0.
>
> Can you try re-running your test, but modify it to attempt to have a
> client connect to a non-observer in the case that connecting to the
> observer fails? It would be interesting to see if this was an observer
> specific issue or not. (another thing perhaps to try is just have the
> existing client connect to a non-observer rather than the observer,
> run it a bunch of times and see if it happens)
>
> Patrick
>
> On Wed, Aug 3, 2011 at 7:16 AM, Eugene Koontz <ek...@hiro-tan.org>
> wrote:
> > On 8/2/11 10:32 PM, Patrick Hunt wrote:
> >>
> >> What type of ec2 instance are you running on? I've seen some failures
> >> due to underpowered/underresourced systems.
> >>
> >> Is ObserverTest consistently failing?
> >>
> >> Patrick
> >>
> > Hi Patrick,
> > It's an m1.large. I have ulimit -a set so that open files and open
> > processes are at 100,000.
> >
> > If I run ObserverTest on its own using the attached shell script
> repeat.sh
> > (src/repeat.sh ObserverTest), it usually fails within 20 iterations;
> > (although in the following pastebin it took 38 iterations to fail).
> >
> >
> > It always fails in the same place, at ObserverTest.java:101:
> >
> > http://pastebin.com/BGNUb05t
> >
> > -Eugene
> >
> >
>
Re: 3.4 Release.
Posted by Patrick Hunt <ph...@apache.org>.
Seems the observer (or the quorum itself) is failing to allow a client
to connect:
[junit] 2011-08-03 14:12:29,273 [myid:3] - INFO
[QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:11229:QuorumPeer@701] - OBSERVING
....
[junit] 2011-08-03 14:12:29,359 [myid:] - INFO
[main:ZooKeeper@427] - Initiating client connection,
connectString=127.0.0.1:11229 sessionTimeout=30000
watcher=org.apache.zookeeper.test.ObserverTest@6490832e
[junit] 2011-08-03 14:12:29,378 [myid:] - INFO
[main-SendThread():ClientCnxn$SendThread@888] - Opening socket
connection to server /127.0.0.1:11229
[junit] 2011-08-03 14:12:29,379 [myid:3] - INFO
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11229:NIOServerCnxnFactory@197]
- Accepted socket connection from /127.0.0.1:56250
[junit] 2011-08-03 14:12:29,379 [myid:] - INFO
[main-SendThread(localhost:11229):ClientCnxn$SendThread@814] - Socket
connection established to localhost/127.0.0.1:11229, initiating
session
[junit] 2011-08-03 14:12:29,380 [myid:3] - INFO
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11229:ZooKeeperServer@833] -
Client attempting to establish new session at /127.0.0.1:56250
[junit] 2011-08-03 14:12:53,356 [myid:2] - INFO
[QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:11228:Leader@419] - Shutting down
Notice that last line, ~24 seconds go by.
Please file a bug on this. Blocker for 3.4.0.
Can you try re-running your test, but modify it to attempt to have a
client connect to a non-observer in the case that connecting to the
observer fails? It would be interesting to see if this was an observer
specific issue or not. (another thing perhaps to try is just have the
existing client connect to a non-observer rather than the observer,
run it a bunch of times and see if it happens)
Patrick
On Wed, Aug 3, 2011 at 7:16 AM, Eugene Koontz <ek...@hiro-tan.org> wrote:
> On 8/2/11 10:32 PM, Patrick Hunt wrote:
>>
>> What type of ec2 instance are you running on? I've seen some failures
>> due to underpowered/underresourced systems.
>>
>> Is ObserverTest consistently failing?
>>
>> Patrick
>>
> Hi Patrick,
> It's an m1.large. I have ulimit -a set so that open files and open
> processes are at 100,000.
>
> If I run ObserverTest on its own using the attached shell script repeat.sh
> (src/repeat.sh ObserverTest), it usually fails within 20 iterations;
> (although in the following pastebin it took 38 iterations to fail).
>
>
> It always fails in the same place, at ObserverTest.java:101:
>
> http://pastebin.com/BGNUb05t
>
> -Eugene
>
>
Re: 3.4 Release.
Posted by Eugene Koontz <ek...@hiro-tan.org>.
On 8/2/11 10:32 PM, Patrick Hunt wrote:
> What type of ec2 instance are you running on? I've seen some failures
> due to underpowered/underresourced systems.
>
> Is ObserverTest consistently failing?
>
> Patrick
>
Hi Patrick,
It's an m1.large. I have ulimit -a set so that open files and open
processes are at 100,000.
If I run ObserverTest on its own using the attached shell script
repeat.sh (src/repeat.sh ObserverTest), it usually fails within 20
iterations; (although in the following pastebin it took 38 iterations to
fail).
It always fails in the same place, at ObserverTest.java:101:
http://pastebin.com/BGNUb05t
-Eugene
Re: 3.4 Release.
Posted by Patrick Hunt <ph...@apache.org>.
What type of ec2 instance are you running on? I've seen some failures
due to underpowered/underresourced systems.
Is ObserverTest consistently failing?
Patrick
On Tue, Aug 2, 2011 at 6:28 PM, Eugene Koontz <ek...@hiro-tan.org> wrote:
> On 8/2/11 5:26 PM, Patrick Hunt wrote:
>>
>> Eugene you saw my email about that test and ulimit right? Make sure
>> you have ulimit for max files and max processes> 1k, that was the
>> issue I had (max proc was set to 1024).
>>
>> Patrick
>>
> Thank you Patrick, no; I missed your earlier email about max processes. I
> increased my max processes to 100000 by adding to /etc/security/limits.conf:
>
> ec2-user soft nproc 100000
> ec2-user hard nproc 100000
>
> It was great to see that QuorumZxidSyncTest passed after doing this (as well
> as ReadOnlyModeTest, which I neglected to metion, also failed before) .
>
> Unfortunately, now ObserverTest fails.
>
> So let me try increasing nofiles similarly and see if that helps (although I
> doubt this would be a factor, because it passed earlier with its currently
> limit of only 1024 max open files).
>
> -Eugene
>
Re: 3.4 Release.
Posted by Eugene Koontz <ek...@hiro-tan.org>.
On 8/2/11 5:26 PM, Patrick Hunt wrote:
> Eugene you saw my email about that test and ulimit right? Make sure
> you have ulimit for max files and max processes> 1k, that was the
> issue I had (max proc was set to 1024).
>
> Patrick
>
Thank you Patrick, no; I missed your earlier email about max processes.
I increased my max processes to 100000 by adding to
/etc/security/limits.conf:
ec2-user soft nproc 100000
ec2-user hard nproc 100000
It was great to see that QuorumZxidSyncTest passed after doing this (as
well as ReadOnlyModeTest, which I neglected to metion, also failed
before) .
Unfortunately, now ObserverTest fails.
So let me try increasing nofiles similarly and see if that helps
(although I doubt this would be a factor, because it passed earlier with
its currently limit of only 1024 max open files).
-Eugene
Re: 3.4 Release.
Posted by Patrick Hunt <ph...@apache.org>.
Eugene you saw my email about that test and ulimit right? Make sure
you have ulimit for max files and max processes > 1k, that was the
issue I had (max proc was set to 1024).
Patrick
On Tue, Aug 2, 2011 at 4:35 PM, Eugene Koontz <ek...@hiro-tan.org> wrote:
> On 8/1/11 7:49 PM, Mahadev Konar wrote:
>>
>> Looks like jenkins is still having issues. Until then we can fix the
>> Open issues we have:
>>
>> ZOOKEEPER-1125: Intermittent java core test failures
>> Vishal do you want to take this up?
>>
>> ZOOKEEPER-839: Ill upload a patch by tonight.
>>
>> ZOOKEEPER-1136. Ben would you be taking this up?
>>
>> ZOOKEEPER-1055. Eugene, do you have sometime to take a look at this?
>>
>>
> Hi Mahadev,
> I refreshed the patch for ZOOKEEPER-1055. I am having trouble getting
> QuorumZxidSyncTest to pass, on EC2. The test works locally with
>
> "ant junit.run -Dtest.output=yes -Dtestcase=QuorumZxidSyncTest", though.
>
> This odd behavior is the topic of ZOOKEEPER-1125.
>
>
> -Eugene
>
Re: 3.4 Release.
Posted by Eugene Koontz <ek...@hiro-tan.org>.
On 8/1/11 7:49 PM, Mahadev Konar wrote:
> Looks like jenkins is still having issues. Until then we can fix the
> Open issues we have:
>
> ZOOKEEPER-1125: Intermittent java core test failures
> Vishal do you want to take this up?
>
> ZOOKEEPER-839: Ill upload a patch by tonight.
>
> ZOOKEEPER-1136. Ben would you be taking this up?
>
> ZOOKEEPER-1055. Eugene, do you have sometime to take a look at this?
>
>
Hi Mahadev,
I refreshed the patch for ZOOKEEPER-1055. I am having trouble getting
QuorumZxidSyncTest to pass, on EC2. The test works locally with
"ant junit.run -Dtest.output=yes -Dtestcase=QuorumZxidSyncTest", though.
This odd behavior is the topic of ZOOKEEPER-1125.
-Eugene