[jira] Commented: (ZOOKEEPER-210) Require Java 6
[ https://issues.apache.org/jira/browse/ZOOKEEPER-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12666492#action_12666492 ] Hudson commented on ZOOKEEPER-210: -- Integrated in ZooKeeper-trunk #207 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/207/]) , Require Java 6. Require Java 6 -- Key: ZOOKEEPER-210 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-210 Project: Zookeeper Issue Type: Task Components: documentation, java client, jmx, server Reporter: Patrick Hunt Assignee: Patrick Hunt Fix For: 3.1.0 Attachments: ZOOKEEPER-210.patch We should require Java 6 for release 3.1.0. At this point there is full java6 support on all major platforms (linux/windows/macosx). The vast majority of ZooKeeper contributors use Java 6 when developing, and hence do run into (usually minor) back-compatibility problems. I believe there are also some benefits regarding JMX (updated spec support in java6) if we drop java 5. FWIW: Hadoop Core has also moved to require Java6: https://issues.apache.org/jira/browse/HADOOP-2325 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Fwd: [Travel Assistance] Applications for ApacheCon EU 2009 - Now Open
From: Tony Stevenson pct...@apache.org Date: January 23, 2009 5:28:19 AM PST To: travel-assista...@apache.org Subject: [Travel Assistance] Applications for ApacheCon EU 2009 - Now Open The Travel Assistance Committee is now accepting applications for those wanting to attend ApacheCon EU 2009 between the 23rd and 27th March 2009 in Amsterdam. The Travel Assistance Committee is looking for people who would like to be able to attend ApacheCon EU 2009 who need some financial support in order to get there. There are very few places available and the criteria is high, that aside applications are open to all open source developers who feel that their attendance would benefit themselves, their project(s), the ASF or open source in general. Financial assistance is available for travel, accommodation and entrance fees either in full or in part, depending on circumstances. It is intended that all our ApacheCon events are covered, so it may be prudent for those in the United States or Asia to wait until an event closer to them comes up - you are all welcome to apply for ApacheCon EU of course, but there must be compelling reasons for you to attend an event further away that your home location for your application to be considered above those closer to the event location. More information can be found on the main Apache website at http://www.apache.org/travel/index.html - where you will also find a link to the online application form. Time is very tight for this event, so applications are open now and will end on the 4th February 2009 - to give enough time for travel arrangements to be made. Good luck to all those that apply. Regards, The Travel Assistance Committee
[jira] Updated: (ZOOKEEPER-273) Zookeeper c client build should not depend on CPPUNIT
[ https://issues.apache.org/jira/browse/ZOOKEEPER-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-273: --- Fix Version/s: 3.1.0 Status: Open (was: Patch Available) Unfortunately this patch removes cppunit entirely from ac, we need cppunit for the tests. Rather this patch should make cppunit an option for configure - ie on by default, with a commmand line option to configure to turn off. I think there is a std way to do this in ac. Zookeeper c client build should not depend on CPPUNIT - Key: ZOOKEEPER-273 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-273 Project: Zookeeper Issue Type: Bug Components: c client Reporter: Runping Qi Fix For: 3.1.0 Attachments: patch_zookeeper_273.txt One should be able to build Zookeeper C client libs on a machine without CPPUNIT installation. A simple fix is to remove from configure.ac the following line: M_PATH_CPPUNIT(1.10.2) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-231) Quotas in zookeeper
[ https://issues.apache.org/jira/browse/ZOOKEEPER-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-231: Attachment: ZOOKEEPER-231.patch Here is the latest patch. THis patch has the following -- - quota can be set via the commadn line using setQuota -n|-b path - quota can be deleted via the commandline using delQuota [-n|-b] path - setting quota for a node that does not exist will throw an exception - setting quota for a node that has an ancestor or a descendant that has a quota cannot be set - includes a simeple test case -- their are lot of corner cases. I am still trying to add more - includes documentation (please review the documentation to see if you understand how to use quotas) - their are a lot of corner cases --- feel free to test them and mention it on the jira -- i will tru and write a test case for that. Quotas in zookeeper --- Key: ZOOKEEPER-231 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-231 Project: Zookeeper Issue Type: New Feature Affects Versions: 3.0.0 Reporter: Mahadev konar Assignee: Mahadev konar Fix For: 3.1.0 Attachments: ZOOKEEPER-231.patch, ZOOKEEPER-231.patch, ZOOKEEPER-231.patch, ZOOKEEPER-231.patch, ZOOKEEPER-231.patch, ZOOKEEPER-231.patch creating quota's in zookeeper so that a runaway application does not bring down the zookeeper cluster. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-231) Quotas in zookeeper
[ https://issues.apache.org/jira/browse/ZOOKEEPER-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1293#action_1293 ] Mahadev konar commented on ZOOKEEPER-231: - forogt to mention- - to list the quota limit and usage use listquota path Quotas in zookeeper --- Key: ZOOKEEPER-231 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-231 Project: Zookeeper Issue Type: New Feature Affects Versions: 3.0.0 Reporter: Mahadev konar Assignee: Mahadev konar Fix For: 3.1.0 Attachments: ZOOKEEPER-231.patch, ZOOKEEPER-231.patch, ZOOKEEPER-231.patch, ZOOKEEPER-231.patch, ZOOKEEPER-231.patch, ZOOKEEPER-231.patch creating quota's in zookeeper so that a runaway application does not bring down the zookeeper cluster. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-275) Bug in FastLeaderElection
[ https://issues.apache.org/jira/browse/ZOOKEEPER-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12666786#action_12666786 ] Patrick Hunt commented on ZOOKEEPER-275: What do you mean by kill qcnxmanager? During the kill is the code explicitly closing the port? It might be that the socket isn't being closed explicitly? (relies on gc?) Ensure that the code will explicitly close the port if killed. If you're done on this issue you might consider submitting the patch for review. Bug in FastLeaderElection - Key: ZOOKEEPER-275 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-275 Project: Zookeeper Issue Type: Bug Components: leaderElection Reporter: Flavio Paiva Junqueira Assignee: Flavio Paiva Junqueira Fix For: 3.1.0 Attachments: ZOOKEEPER-275.patch I found an execution in which leader election does not make progress. Here is the problematic scenario: - We have an ensemble of 3 servers, and we start only 2; - We let them elect a leader, and then crash the one with lowest id, say S_1 (call the other S_2); - We restart the crashed server. Upon restarting S_1, S_2 has its logical clock more advanced, and S_1 has its logical clock set to 1. Once S_1 receives a notification from S_2, it notices that it is in the wrong round and it advances its logical clock to the same value as S_1. Now, the problem comes exactly in this point because in the current code S_1 resets its vote to its initial vote (its own id and zxid). Since S_2 has already notified S_1, it won't do it again, and we are stuck. The patch I'm submitting fixes this problem by setting the vote of S_1 to the one received if it satisfies the total order predicate (received zxid is higher or received zxid is the same and received id is higher). Related to this problem, I noticed that by trying to avoid unnecessary notification duplicates, there could be scenarios in which a server fails before electing a leader and restarts before leader election succeeds. This could happen, for example, when there isn't enough servers available and one available crashes and restarts. I fixed this problem in the attached patch by allowing a server to send a new batch of notifications if there is at least one outgoing queue of pending notifications empty. This is ok because we space out consecutive batches of notifications. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-263) document connection host:port as comma separated list in forrest docs
[ https://issues.apache.org/jira/browse/ZOOKEEPER-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-263: --- Attachment: ZOOKEEPER-263.patch Updated documentation to better reflect host connection string syntax/semantics. document connection host:port as comma separated list in forrest docs - Key: ZOOKEEPER-263 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-263 Project: Zookeeper Issue Type: Improvement Components: c client, documentation, java client Affects Versions: 3.0.0, 3.0.1 Reporter: Patrick Hunt Priority: Minor Fix For: 3.1.0 Attachments: ZOOKEEPER-263.patch The java API docs talk about the host:port comma separated list, however the forrest docs don't mention this. it's confusing for users, they don't know that the connection string can be a list of host:port comma separated. We should mention in the programmer guide, perhaps even in the overview/started (mention in passing and reference the prog guide for full detail). Also the java doc should be updated, right now we have a see also in the short constructor, to make it more explicit we should copy/paste the docs. The c client should also be updated to detail that it's a comma separated list of host:port (similar to java). Right host we just say host, need to be more explicit as to the format of the string. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-277) Define PATH_SEPARATOR
Define PATH_SEPARATOR - Key: ZOOKEEPER-277 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-277 Project: Zookeeper Issue Type: Improvement Reporter: Nitay Joffe Priority: Trivial We should define a constant for PATH_SEPARATOR = / and use that throughout the code rather than the hardcoded /. Users can be told to use this constant to be safe in case of future changes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-269) connectionloss - add more documentation to detail
[ https://issues.apache.org/jira/browse/ZOOKEEPER-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-269: --- Attachment: ZOOKEEPER-269.patch Added doc details per the bug desc/comments. Kept things fairly high level - don't want to talk about api details in forrest, really need those in doxy/javadoc. connectionloss - add more documentation to detail -- Key: ZOOKEEPER-269 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-269 Project: Zookeeper Issue Type: Improvement Components: documentation Affects Versions: 3.0.0, 3.0.1 Reporter: Patrick Hunt Priority: Minor Fix For: 3.1.0 Attachments: ZOOKEEPER-269.patch discussion with user, this should be better documented: -- There are basically 2 cases where you can see connectionloss: 1) you call an operation on a session that is no longer alive 2) you are disconnected from a server when there are pending async operations to that server (you made an async request which has not yet completed) Patrick Kevin Burton wrote: Can this be thrown when using multiple servers as long as 1 of them is online? Trying to figure out of I should try some type of reconnect if a single machine fails instead of failing altogether. Kevin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-269) connectionloss - add more documentation to detail
[ https://issues.apache.org/jira/browse/ZOOKEEPER-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-269: --- Assignee: Patrick Hunt Status: Patch Available (was: Open) connectionloss - add more documentation to detail -- Key: ZOOKEEPER-269 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-269 Project: Zookeeper Issue Type: Improvement Components: documentation Affects Versions: 3.0.1, 3.0.0 Reporter: Patrick Hunt Assignee: Patrick Hunt Priority: Minor Fix For: 3.1.0 Attachments: ZOOKEEPER-269.patch discussion with user, this should be better documented: -- There are basically 2 cases where you can see connectionloss: 1) you call an operation on a session that is no longer alive 2) you are disconnected from a server when there are pending async operations to that server (you made an async request which has not yet completed) Patrick Kevin Burton wrote: Can this be thrown when using multiple servers as long as 1 of them is online? Trying to figure out of I should try some type of reconnect if a single machine fails instead of failing altogether. Kevin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-277) Define PATH_SEPARATOR
[ https://issues.apache.org/jira/browse/ZOOKEEPER-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-277: --- Component/s: tests server java client documentation c client Define PATH_SEPARATOR - Key: ZOOKEEPER-277 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-277 Project: Zookeeper Issue Type: Improvement Components: c client, documentation, java client, server, tests Reporter: Nitay Joffe Priority: Trivial We should define a constant for PATH_SEPARATOR = / and use that throughout the code rather than the hardcoded /. Users can be told to use this constant to be safe in case of future changes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
