[jira] Updated: (ZOOKEEPER-702) GSoC 2010: Failure Detector Model
[ https://issues.apache.org/jira/browse/ZOOKEEPER-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abmar Barros updated ZOOKEEPER-702: --- Attachment: ZOOKEEPER-702.patch In this patch: * Adapted failure detectors to work on both client and server sides of the client-server monitoring. * Refactored server-side code to use the FailureDetector interface. * Created a new FailureDetector, which groups monitoreds by their tick time, similar to what the SessionTracking does. * Made the failure detector (and its parameters) options of the ZooKeeper configuration file. * Corrected indentation (spaces instead of tabs). Next steps are: * As suggested by Flavio, create sub tasks in this Jira for: ** Experimentation. ** Refactor server-server monitoring to use FailureDetector interface and make it configurable. ** Forrest documentation. > GSoC 2010: Failure Detector Model > - > > Key: ZOOKEEPER-702 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-702 > Project: Zookeeper > Issue Type: Wish >Reporter: Henry Robinson >Assignee: Abmar Barros > Attachments: bertier-pseudo.txt, bertier-pseudo.txt, chen-pseudo.txt, > chen-pseudo.txt, phiaccrual-pseudo.txt, phiaccrual-pseudo.txt, > ZOOKEEPER-702.patch, ZOOKEEPER-702.patch, ZOOKEEPER-702.patch, > ZOOKEEPER-702.patch > > > Failure Detector Module > Possible Mentor > Henry Robinson (henry at apache dot org) > Requirements > Java, some distributed systems knowledge, comfort implementing distributed > systems protocols > Description > ZooKeeper servers detects the failure of other servers and clients by > counting the number of 'ticks' for which it doesn't get a heartbeat from > other machines. This is the 'timeout' method of failure detection and works > very well; however it is possible that it is too aggressive and not easily > tuned for some more unusual ZooKeeper installations (such as in a wide-area > network, or even in a mobile ad-hoc network). > This project would abstract the notion of failure detection to a dedicated > Java module, and implement several failure detectors to compare and contrast > their appropriateness for ZooKeeper. For example, Apache Cassandra uses a > phi-accrual failure detector (http://ddsg.jaist.ac.jp/pub/HDY+04.pdf) which > is much more tunable and has some very interesting properties. This is a > great project if you are interested in distributed algorithms, or want to > help re-factor some of ZooKeeper's internal code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-702) GSoC 2010: Failure Detector Model
[ https://issues.apache.org/jira/browse/ZOOKEEPER-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886224#action_12886224 ] Abmar Barros commented on ZOOKEEPER-702: Hi Flavio, actually I was talking about the client monitoring on the server-side (SessionTracking). > GSoC 2010: Failure Detector Model > - > > Key: ZOOKEEPER-702 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-702 > Project: Zookeeper > Issue Type: Wish >Reporter: Henry Robinson >Assignee: Abmar Barros > Attachments: bertier-pseudo.txt, bertier-pseudo.txt, chen-pseudo.txt, > chen-pseudo.txt, phiaccrual-pseudo.txt, phiaccrual-pseudo.txt, > ZOOKEEPER-702.patch, ZOOKEEPER-702.patch, ZOOKEEPER-702.patch > > > Failure Detector Module > Possible Mentor > Henry Robinson (henry at apache dot org) > Requirements > Java, some distributed systems knowledge, comfort implementing distributed > systems protocols > Description > ZooKeeper servers detects the failure of other servers and clients by > counting the number of 'ticks' for which it doesn't get a heartbeat from > other machines. This is the 'timeout' method of failure detection and works > very well; however it is possible that it is too aggressive and not easily > tuned for some more unusual ZooKeeper installations (such as in a wide-area > network, or even in a mobile ad-hoc network). > This project would abstract the notion of failure detection to a dedicated > Java module, and implement several failure detectors to compare and contrast > their appropriateness for ZooKeeper. For example, Apache Cassandra uses a > phi-accrual failure detector (http://ddsg.jaist.ac.jp/pub/HDY+04.pdf) which > is much more tunable and has some very interesting properties. This is a > great project if you are interested in distributed algorithms, or want to > help re-factor some of ZooKeeper's internal code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-794) Callbacks are not invoked when the client is closed
[ https://issues.apache.org/jira/browse/ZOOKEEPER-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886020#action_12886020 ] Mahadev konar commented on ZOOKEEPER-794: - alexis, Do you see the problem with c client library as well? Or do you just see the problem with the java client? > Callbacks are not invoked when the client is closed > --- > > Key: ZOOKEEPER-794 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-794 > Project: Zookeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.3.1 >Reporter: Alexis Midon >Assignee: Alexis Midon > Fix For: 3.3.2, 3.4.0 > > Attachments: ZOOKEEPER-794.patch.txt, ZOOKEEPER-794.txt > > > I noticed that ZooKeeper has different behaviors when calling synchronous or > asynchronous actions on a closed ZooKeeper client. > Actually a synchronous call will throw a "session expired" exception while an > asynchronous call will do nothing. No exception, no callback invocation. > Actually, even if the EventThread receives the Packet with the session > expired err code, the packet is never processed since the thread has been > killed by the ventOfDeath. So the call back is not invoked. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-719) Add throttling to BookKeeper client
[ https://issues.apache.org/jira/browse/ZOOKEEPER-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886019#action_12886019 ] Benjamin Reed commented on ZOOKEEPER-719: - +1 looks good > Add throttling to BookKeeper client > --- > > Key: ZOOKEEPER-719 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-719 > Project: Zookeeper > Issue Type: Bug > Components: contrib-bookkeeper >Affects Versions: 3.3.0 >Reporter: Flavio Paiva Junqueira >Assignee: Flavio Paiva Junqueira > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-719.patch, ZOOKEEPER-719.patch, > ZOOKEEPER-719.patch, ZOOKEEPER-719.patch > > > Add throttling to client to control the rate of operations to bookies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-802) Improved LogGraph filters + documentation
[ https://issues.apache.org/jira/browse/ZOOKEEPER-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885994#action_12885994 ] Hadoop QA commented on ZOOKEEPER-802: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12448889/ZOOKEEPER-802.patch against trunk revision 961026. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no tests are needed for this patch. +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/135/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h1.grid.sp2.yahoo.net/135/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h1.grid.sp2.yahoo.net/135/console This message is automatically generated. > Improved LogGraph filters + documentation > - > > Key: ZOOKEEPER-802 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-802 > Project: Zookeeper > Issue Type: Improvement >Affects Versions: 3.4.0 >Reporter: Ivan Kelly >Assignee: Ivan Kelly >Priority: Minor > Fix For: 3.4.0 > > Attachments: logs.tar.gz, ZOOKEEPER-802.patch, ZOOKEEPER-802.patch, > ZOOKEEPER-802.patch, ZOOKEEPER-802.patch, ZOOKEEPER-802.patch > > > The log filtering mechanism has been improved and extended to work with > message logs. Also, the documentation has been moved into the forrest > documentation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-802) Improved LogGraph filters + documentation
[ https://issues.apache.org/jira/browse/ZOOKEEPER-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated ZOOKEEPER-802: - Attachment: ZOOKEEPER-802.patch > Improved LogGraph filters + documentation > - > > Key: ZOOKEEPER-802 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-802 > Project: Zookeeper > Issue Type: Improvement >Affects Versions: 3.4.0 >Reporter: Ivan Kelly >Assignee: Ivan Kelly >Priority: Minor > Fix For: 3.4.0 > > Attachments: logs.tar.gz, ZOOKEEPER-802.patch, ZOOKEEPER-802.patch, > ZOOKEEPER-802.patch, ZOOKEEPER-802.patch, ZOOKEEPER-802.patch > > > The log filtering mechanism has been improved and extended to work with > message logs. Also, the documentation has been moved into the forrest > documentation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-802) Improved LogGraph filters + documentation
[ https://issues.apache.org/jira/browse/ZOOKEEPER-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated ZOOKEEPER-802: - Status: Patch Available (was: Open) Comments addressed. > Improved LogGraph filters + documentation > - > > Key: ZOOKEEPER-802 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-802 > Project: Zookeeper > Issue Type: Improvement >Affects Versions: 3.4.0 >Reporter: Ivan Kelly >Assignee: Ivan Kelly >Priority: Minor > Fix For: 3.4.0 > > Attachments: logs.tar.gz, ZOOKEEPER-802.patch, ZOOKEEPER-802.patch, > ZOOKEEPER-802.patch, ZOOKEEPER-802.patch, ZOOKEEPER-802.patch > > > The log filtering mechanism has been improved and extended to work with > message logs. Also, the documentation has been moved into the forrest > documentation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-802) Improved LogGraph filters + documentation
[ https://issues.apache.org/jira/browse/ZOOKEEPER-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-802: --- Attachment: logs.tar.gz logs that show the failure I'm seeing. (server 5 missing from graph and sessions not showing up) > Improved LogGraph filters + documentation > - > > Key: ZOOKEEPER-802 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-802 > Project: Zookeeper > Issue Type: Improvement >Affects Versions: 3.4.0 >Reporter: Ivan Kelly >Assignee: Ivan Kelly >Priority: Minor > Fix For: 3.4.0 > > Attachments: logs.tar.gz, ZOOKEEPER-802.patch, ZOOKEEPER-802.patch, > ZOOKEEPER-802.patch, ZOOKEEPER-802.patch > > > The log filtering mechanism has been improved and extended to work with > message logs. Also, the documentation has been moved into the forrest > documentation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-806) Cluster management with Zookeeper - Norbert
[ https://issues.apache.org/jira/browse/ZOOKEEPER-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885969#action_12885969 ] Mahadev konar commented on ZOOKEEPER-806: - great to see this!!! John, Here is a link on how to contribute to ZooKeeper: http://wiki.apache.org/hadoop/ZooKeeper/HowToContribute Hope this helps. > Cluster management with Zookeeper - Norbert > --- > > Key: ZOOKEEPER-806 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-806 > Project: Zookeeper > Issue Type: New Feature >Reporter: John Wang > > Hello, we have built a cluster management layer on top of Zookeeper here at > the SNA team at LinkedIn: > http://sna-projects.com/norbert/ > We were wondering ways for collaboration as this is a very useful application > of zookeeper. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-806) Cluster management with Zookeeper - Norbert
Cluster management with Zookeeper - Norbert --- Key: ZOOKEEPER-806 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-806 Project: Zookeeper Issue Type: New Feature Reporter: John Wang Hello, we have built a cluster management layer on top of Zookeeper here at the SNA team at LinkedIn: http://sna-projects.com/norbert/ We were wondering ways for collaboration as this is a very useful application of zookeeper. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-796) zkServer.sh should support an external PIDFILE variable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885918#action_12885918 ] Hudson commented on ZOOKEEPER-796: -- Integrated in ZooKeeper-trunk #870 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/870/]) ZOOKEEPER-796. zkServer.sh should support an external PIDFILE variable > zkServer.sh should support an external PIDFILE variable > --- > > Key: ZOOKEEPER-796 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-796 > Project: Zookeeper > Issue Type: Bug > Components: scripts >Reporter: Alex Newman >Assignee: Alex Newman > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-796.patch, ZOOKEEPER-796.patch > > > So currently the pid file has to be tied to the datadirectory when starting > zkServer.sh. It would be good to be able to break them up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
