[jira] Updated: (ZOOKEEPER-772) zkpython segfaults when watcher from async get children is invoked.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-772: --- Status: Resolved (was: Patch Available) Hadoop Flags: [Reviewed] Resolution: Fixed +1, thanks Henry! > zkpython segfaults when watcher from async get children is invoked. > --- > > Key: ZOOKEEPER-772 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-772 > Project: Zookeeper > Issue Type: Bug > Components: contrib-bindings > Environment: ubuntu lucid (10.04) / zk trunk >Reporter: Kapil Thangavelu >Assignee: Henry Robinson > Fix For: 3.4.0 > > Attachments: asyncgetchildren.py, zkpython-testasyncgetchildren.diff, > ZOOKEEPER-772.patch, ZOOKEEPER-772.patch > > > When utilizing the zkpython async get children api with a watch, i > consistently get segfaults when the watcher is invoked to process events. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-772) zkpython segfaults when watcher from async get children is invoked.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-772: --- Fix Version/s: 3.4.0 > zkpython segfaults when watcher from async get children is invoked. > --- > > Key: ZOOKEEPER-772 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-772 > Project: Zookeeper > Issue Type: Bug > Components: contrib-bindings > Environment: ubuntu lucid (10.04) / zk trunk >Reporter: Kapil Thangavelu >Assignee: Henry Robinson > Fix For: 3.4.0 > > Attachments: asyncgetchildren.py, zkpython-testasyncgetchildren.diff, > ZOOKEEPER-772.patch, ZOOKEEPER-772.patch > > > When utilizing the zkpython async get children api with a watch, i > consistently get segfaults when the watcher is invoked to process events. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-769) Leader can treat observers as quorum members
[ https://issues.apache.org/jira/browse/ZOOKEEPER-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henry Robinson updated ZOOKEEPER-769: - Status: Patch Available (was: Open) > Leader can treat observers as quorum members > > > Key: ZOOKEEPER-769 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-769 > Project: Zookeeper > Issue Type: Bug >Affects Versions: 3.3.0 > Environment: Ubuntu Karmic x64 >Reporter: Sergey Doroshenko >Assignee: Sergey Doroshenko > Fix For: 3.4.0 > > Attachments: follower.log, leader.log, observer.log, warning.patch, > zoo1.cfg, ZOOKEEPER-769.patch, ZOOKEEPER-769.patch > > > In short: it seems leader can treat observers as quorum members. > Steps to repro: > 1. Server configuration: 3 voters, 2 observers (attached). > 2. Bring up 2 voters and one observer. It's enough for quorum. > 3. Shut down the one from the quorum who is the follower. > As I understand, expected result is that leader will start a new election > round so that to regain quorum. > But the real situation is that it just says goodbye to that follower, and is > still operable. (When I'm shutting down 3rd one -- observer -- leader starts > trying to regain a quorum). > (Expectedly, if on step 3 we shut down the leader, not the follower, > remaining follower starta new leader election, as it should be). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-769) Leader can treat observers as quorum members
[ https://issues.apache.org/jira/browse/ZOOKEEPER-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henry Robinson updated ZOOKEEPER-769: - Attachment: ZOOKEEPER-769.patch I made a few small changes to your patch to make the logic a little easier to follow. Take a look and let me know if you think this is ok, otherwise I'll commit the patch tomorrow. Thanks! Henry > Leader can treat observers as quorum members > > > Key: ZOOKEEPER-769 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-769 > Project: Zookeeper > Issue Type: Bug >Affects Versions: 3.3.0 > Environment: Ubuntu Karmic x64 >Reporter: Sergey Doroshenko >Assignee: Sergey Doroshenko > Fix For: 3.4.0 > > Attachments: follower.log, leader.log, observer.log, warning.patch, > zoo1.cfg, ZOOKEEPER-769.patch, ZOOKEEPER-769.patch > > > In short: it seems leader can treat observers as quorum members. > Steps to repro: > 1. Server configuration: 3 voters, 2 observers (attached). > 2. Bring up 2 voters and one observer. It's enough for quorum. > 3. Shut down the one from the quorum who is the follower. > As I understand, expected result is that leader will start a new election > round so that to regain quorum. > But the real situation is that it just says goodbye to that follower, and is > still operable. (When I'm shutting down 3rd one -- observer -- leader starts > trying to regain a quorum). > (Expectedly, if on step 3 we shut down the leader, not the follower, > remaining follower starta new leader election, as it should be). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-769) Leader can treat observers as quorum members
[ https://issues.apache.org/jira/browse/ZOOKEEPER-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henry Robinson updated ZOOKEEPER-769: - Status: Open (was: Patch Available) > Leader can treat observers as quorum members > > > Key: ZOOKEEPER-769 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-769 > Project: Zookeeper > Issue Type: Bug >Affects Versions: 3.3.0 > Environment: Ubuntu Karmic x64 >Reporter: Sergey Doroshenko >Assignee: Sergey Doroshenko > Fix For: 3.4.0 > > Attachments: follower.log, leader.log, observer.log, warning.patch, > zoo1.cfg, ZOOKEEPER-769.patch, ZOOKEEPER-769.patch > > > In short: it seems leader can treat observers as quorum members. > Steps to repro: > 1. Server configuration: 3 voters, 2 observers (attached). > 2. Bring up 2 voters and one observer. It's enough for quorum. > 3. Shut down the one from the quorum who is the follower. > As I understand, expected result is that leader will start a new election > round so that to regain quorum. > But the real situation is that it just says goodbye to that follower, and is > still operable. (When I'm shutting down 3rd one -- observer -- leader starts > trying to regain a quorum). > (Expectedly, if on step 3 we shut down the leader, not the follower, > remaining follower starta new leader election, as it should be). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-636) configure.ac has instructions which override the contents of CFLAGS and CXXFLAGS.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt reassigned ZOOKEEPER-636: -- Assignee: Maxim P. Dementiev (was: Patrick Hunt) > configure.ac has instructions which override the contents of CFLAGS and > CXXFLAGS. > - > > Key: ZOOKEEPER-636 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-636 > Project: Zookeeper > Issue Type: Improvement > Components: build, c client >Affects Versions: 3.2.1 >Reporter: Maxim P. Dementiev >Assignee: Maxim P. Dementiev > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-636.patch > > > The information mustn't be overridden. > The template like «CFLAGS="$CFLAGS -some-option"» should be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-769) Leader can treat observers as quorum members
[ https://issues.apache.org/jira/browse/ZOOKEEPER-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868780#action_12868780 ] Henry Robinson commented on ZOOKEEPER-769: -- Sergey - sorry for the delay. It's on me to review this patch, and then I'll commit it. Thanks for your patience! Henry > Leader can treat observers as quorum members > > > Key: ZOOKEEPER-769 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-769 > Project: Zookeeper > Issue Type: Bug >Affects Versions: 3.3.0 > Environment: Ubuntu Karmic x64 >Reporter: Sergey Doroshenko >Assignee: Sergey Doroshenko > Fix For: 3.4.0 > > Attachments: follower.log, leader.log, observer.log, warning.patch, > zoo1.cfg, ZOOKEEPER-769.patch > > > In short: it seems leader can treat observers as quorum members. > Steps to repro: > 1. Server configuration: 3 voters, 2 observers (attached). > 2. Bring up 2 voters and one observer. It's enough for quorum. > 3. Shut down the one from the quorum who is the follower. > As I understand, expected result is that leader will start a new election > round so that to regain quorum. > But the real situation is that it just says goodbye to that follower, and is > still operable. (When I'm shutting down 3rd one -- observer -- leader starts > trying to regain a quorum). > (Expectedly, if on step 3 we shut down the leader, not the follower, > remaining follower starta new leader election, as it should be). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-769) Leader can treat observers as quorum members
[ https://issues.apache.org/jira/browse/ZOOKEEPER-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868777#action_12868777 ] Sergey Doroshenko commented on ZOOKEEPER-769: - So, since tests pass, should this be committed? Or should something be updated? > Leader can treat observers as quorum members > > > Key: ZOOKEEPER-769 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-769 > Project: Zookeeper > Issue Type: Bug >Affects Versions: 3.3.0 > Environment: Ubuntu Karmic x64 >Reporter: Sergey Doroshenko >Assignee: Sergey Doroshenko > Fix For: 3.4.0 > > Attachments: follower.log, leader.log, observer.log, warning.patch, > zoo1.cfg, ZOOKEEPER-769.patch > > > In short: it seems leader can treat observers as quorum members. > Steps to repro: > 1. Server configuration: 3 voters, 2 observers (attached). > 2. Bring up 2 voters and one observer. It's enough for quorum. > 3. Shut down the one from the quorum who is the follower. > As I understand, expected result is that leader will start a new election > round so that to regain quorum. > But the real situation is that it just says goodbye to that follower, and is > still operable. (When I'm shutting down 3rd one -- observer -- leader starts > trying to regain a quorum). > (Expectedly, if on step 3 we shut down the leader, not the follower, > remaining follower starta new leader election, as it should be). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-775) A large scale pub/sub system
[ https://issues.apache.org/jira/browse/ZOOKEEPER-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868740#action_12868740 ] Patrick Hunt commented on ZOOKEEPER-775: bq. 1) we need to agree on a package name. i propose org.apache.hedwig. i can fix the package references when we decide. (the package is currently in the com.yahoo namespace) sounds good (similar to what we did with bk) bq. 2) we need to figure out where to put it. i'm assuming contrib/hedwig agree bq. 3) finally, we need to integrate into the build. this is a bit harder for me. we currently build hedwig with maven pulling zookeeper and bookkeeper from repositories. i'm not sure how to integrate into our current zookeeper build. so, if some one could take this last one, i would appreciate it. why don't we punt on this for now. just add a README.txt that explains that maven is used for the build. we can support maven for build/dev now and at some point add a simple build.xml that handles the packaging for the release. (if you agree add a JIRA for this task (build.xml) assigned to 3.4.0) > A large scale pub/sub system > > > Key: ZOOKEEPER-775 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-775 > Project: Zookeeper > Issue Type: New Feature > Components: contrib >Reporter: Benjamin Reed > Fix For: 3.4.0 > > Attachments: hedwig.tar.gz > > > we have developed a large scale pub/sub system based on ZooKeeper and > BookKeeper. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-775) A large scale pub/sub system
[ https://issues.apache.org/jira/browse/ZOOKEEPER-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868732#action_12868732 ] Benjamin Reed commented on ZOOKEEPER-775: - sorry, i should have listed the todos: 1) we need to agree on a package name. i propose org.apache.hedwig. i can fix the package references when we decide. (the package is currently in the com.yahoo namespace) 2) we need to figure out where to put it. i'm assuming contrib/hedwig 3) finally, we need to integrate into the build. this is a bit harder for me. we currently build hedwig with maven pulling zookeeper and bookkeeper from repositories. i'm not sure how to integrate into our current zookeeper build. so, if some one could take this last one, i would appreciate it. > A large scale pub/sub system > > > Key: ZOOKEEPER-775 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-775 > Project: Zookeeper > Issue Type: New Feature > Components: contrib >Reporter: Benjamin Reed > Fix For: 3.4.0 > > Attachments: hedwig.tar.gz > > > we have developed a large scale pub/sub system based on ZooKeeper and > BookKeeper. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-636) configure.ac has instructions which override the contents of CFLAGS and CXXFLAGS.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868574#action_12868574 ] Hadoop QA commented on ZOOKEEPER-636: - +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12444711/ZOOKEEPER-636.patch against trunk revision 944515. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 1 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h1.grid.sp2.yahoo.net/96/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h1.grid.sp2.yahoo.net/96/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h1.grid.sp2.yahoo.net/96/console This message is automatically generated. > configure.ac has instructions which override the contents of CFLAGS and > CXXFLAGS. > - > > Key: ZOOKEEPER-636 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-636 > Project: Zookeeper > Issue Type: Improvement > Components: build, c client >Affects Versions: 3.2.1 >Reporter: Maxim P. Dementiev >Assignee: Patrick Hunt > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-636.patch > > > The information mustn't be overridden. > The template like «CFLAGS="$CFLAGS -some-option"» should be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-636) configure.ac has instructions which override the contents of CFLAGS and CXXFLAGS.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim P. Dementiev updated ZOOKEEPER-636: - Status: Patch Available (was: Open) Resubmitting after the fail which isn't related to the patch. > configure.ac has instructions which override the contents of CFLAGS and > CXXFLAGS. > - > > Key: ZOOKEEPER-636 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-636 > Project: Zookeeper > Issue Type: Improvement > Components: build, c client >Affects Versions: 3.2.1 >Reporter: Maxim P. Dementiev >Assignee: Patrick Hunt > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-636.patch > > > The information mustn't be overridden. > The template like «CFLAGS="$CFLAGS -some-option"» should be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-636) configure.ac has instructions which override the contents of CFLAGS and CXXFLAGS.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim P. Dementiev updated ZOOKEEPER-636: - Status: Open (was: Patch Available) > configure.ac has instructions which override the contents of CFLAGS and > CXXFLAGS. > - > > Key: ZOOKEEPER-636 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-636 > Project: Zookeeper > Issue Type: Improvement > Components: build, c client >Affects Versions: 3.2.1 >Reporter: Maxim P. Dementiev >Assignee: Patrick Hunt > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-636.patch > > > The information mustn't be overridden. > The template like «CFLAGS="$CFLAGS -some-option"» should be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
