[jira] Commented: (ZOOKEEPER-78) added a high level protocol/feature - for easy Leader Election or exclusive Write Lock creation
[ https://issues.apache.org/jira/browse/ZOOKEEPER-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680825#action_12680825 ] Tom White commented on ZOOKEEPER-78: i am implementing the recipes in c. Should the C version go in a separate Jira issue and patch? added a high level protocol/feature - for easy Leader Election or exclusive Write Lock creation --- Key: ZOOKEEPER-78 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-78 Project: Zookeeper Issue Type: New Feature Components: java client Affects Versions: 3.0.0 Reporter: james strachan Assignee: james strachan Fix For: 3.2.0 Attachments: patch_with_including_Benjamin's_fix.patch, using_zookeeper_facade.patch, ZOOKEEPER-78.patch, ZOOKEEPER-78.patch, ZOOKEEPER-78.patch Here's a patch which adds a little WriteLock helper class for performing leader elections or creating exclusive locks in some directory znode. Note its an early cut; am sure we can improve it over time. The aim is to avoid folks having to use the low level ZK stuff but provide a simpler high level abstraction. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Hudson build is back to normal: ZooKeeper-trunk #251
See http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/251/
[jira] Commented: (ZOOKEEPER-318) remove locking in zk_hashtable.c or add locking in collect_keys()
[ https://issues.apache.org/jira/browse/ZOOKEEPER-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680848#action_12680848 ] Hudson commented on ZOOKEEPER-318: -- Integrated in ZooKeeper-trunk #251 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/251/]) remove locking in zk_hashtable.c or add locking in collect_keys() - Key: ZOOKEEPER-318 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-318 Project: Zookeeper Issue Type: Bug Components: c client Affects Versions: 3.0.0, 3.0.1, 3.1.0 Reporter: Chris Darroch Assignee: Chris Darroch Fix For: 3.2.0 Attachments: ZOOKEEPER-318.patch From a review of zk_hashtable.c it appears to me that all functions which manipulate the hashtables are called from the IO thread, and therefore any need for locking is obviated. If I'm wrong about that, then I think at a minimum collect_keys() should acquire a lock in the same manner as collect_session_watchers(). Both iterate over hashtable contents (in the latter case using copy_table()). However, from what I can see, the only function (besides the init/destroy functions used when creating a zhandle_t) called from the completion thread is deliverWatchers(), which simply iterates over a delivery list created from the hashtables by collectWatchers(). The activateWatcher() function contains comments which describe it being called by the completion thread, but in fact it is called by the IO thread in zookeeper_process(). I believe all calls to collectWatchers(), activateWatcher(), and collect_keys() are made by the IO thread in zookeeper_interest(), zookeeper_process(), check_events(), send_set_watches(), and handle_error(). Note that queue_session_event() is aliased as PROCESS_SESSION_EVENT, but appears only in handle_error() and check_events(). Also note that handle_error() is called only in zookeeper_process() and handle_socket_error_msg(), which is used only by the IO thread, so far as I can see. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-279) Allow specialization of quorum config parsing (e.g. variable expansion in zoo.cfg)
[
https://issues.apache.org/jira/browse/ZOOKEEPER-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680850#action_12680850
]
Hudson commented on ZOOKEEPER-279:
--
Integrated in ZooKeeper-trunk #251 (See
[http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/251/])
Allow specialization of quorum config parsing (e.g. variable expansion in
zoo.cfg)
--
Key: ZOOKEEPER-279
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-279
Project: Zookeeper
Issue Type: Improvement
Affects Versions: 3.1.0
Reporter: Nitay Joffe
Assignee: Jean-Daniel Cryans
Priority: Minor
Fix For: 3.1.1, 3.2.0
Attachments: HBaseQPC.java, zookeeper-279.patch, zookeeper-279.patch
We would like to define certain parts of ZooKeeper's configuration using
variables that get substituted. For example, we want the ZooKeeper quorum to
be able to use a dataDir configured per user. In other words, something like:
tickTime=2000
dataDir=/tmp/zookeeper-${user.name}
clientPort=2181
initLimit=5
syncLimit=2
server.1=zoo1:2888:3888
server.2=zoo2:2888:3888
server.3=zoo3:2888:3888
I think Java already has a system for configuration that allows something
like this using Properties?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-78) added a high level protocol/feature - for easy Leader Election or exclusive Write Lock creation
[ https://issues.apache.org/jira/browse/ZOOKEEPER-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680933#action_12680933 ] Mahadev konar commented on ZOOKEEPER-78: dont know.. the jira says just talks abt the recipe, so is adequate for both java and c :). .. I would like to have both in one jira so that everyone who wants to contribute to such zookeeeper recipes is encouraged to have both the java and c implementation, but I am open to creating a new jira for c. added a high level protocol/feature - for easy Leader Election or exclusive Write Lock creation --- Key: ZOOKEEPER-78 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-78 Project: Zookeeper Issue Type: New Feature Components: java client Affects Versions: 3.0.0 Reporter: james strachan Assignee: james strachan Fix For: 3.2.0 Attachments: patch_with_including_Benjamin's_fix.patch, using_zookeeper_facade.patch, ZOOKEEPER-78.patch, ZOOKEEPER-78.patch, ZOOKEEPER-78.patch Here's a patch which adds a little WriteLock helper class for performing leader elections or creating exclusive locks in some directory znode. Note its an early cut; am sure we can improve it over time. The aim is to avoid folks having to use the low level ZK stuff but provide a simpler high level abstraction. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-78) added a high level protocol/feature - for easy Leader Election or exclusive Write Lock creation
[ https://issues.apache.org/jira/browse/ZOOKEEPER-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680956#action_12680956 ] Patrick Hunt commented on ZOOKEEPER-78: --- I agree with Mahadev -- we want to encourage ppl to provide (interoperable) implementations for both c/java. However the JIRA should be updated to have both java and c client component listed. Should we add a new recipe component? added a high level protocol/feature - for easy Leader Election or exclusive Write Lock creation --- Key: ZOOKEEPER-78 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-78 Project: Zookeeper Issue Type: New Feature Components: java client Affects Versions: 3.0.0 Reporter: james strachan Assignee: james strachan Fix For: 3.2.0 Attachments: patch_with_including_Benjamin's_fix.patch, using_zookeeper_facade.patch, ZOOKEEPER-78.patch, ZOOKEEPER-78.patch, ZOOKEEPER-78.patch Here's a patch which adds a little WriteLock helper class for performing leader elections or creating exclusive locks in some directory znode. Note its an early cut; am sure we can improve it over time. The aim is to avoid folks having to use the low level ZK stuff but provide a simpler high level abstraction. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-60) Get cppunit tests running as part of Hudson CI
[ https://issues.apache.org/jira/browse/ZOOKEEPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt reassigned ZOOKEEPER-60: - Assignee: (was: Patrick Hunt) Giri said me may look into this. There are a few pre-reqs to running the cppunit tests: 1) run ant jar from the trunk first a) generates c/java source for jute, necessary to build/run the c/tests b) run autoconf -if from the src/c dir c) run ./configure from the src/c/dir 2) cppunit is required to run the tests 3) on redhat I had to install autoconf 2.59_2, automake 1.9.4, cppunit 1.12.0 and used gcc 3 (3.4.2 to be exact) in order to run autoreconf/configure/make 4) from src/c run make run-check to run the tests make check will just compile the tests 5) the tests assume that the jar file for the server has been built a) some mock based tests are run that don't use the server jar b) some server based tests are run that do require the jar - see zkServer.sh in the test directory, run by the unit harness 6) afaik the only output of the tests is to the console (success/failure) there are two tests run by make, zktest_st and zktest_mt for the single and multi threaded tests respectively Get cppunit tests running as part of Hudson CI -- Key: ZOOKEEPER-60 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-60 Project: Zookeeper Issue Type: Improvement Components: build Reporter: Patrick Hunt Investigate if it is possible to run cppunit tests as part of Hudson. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-309) core dump using zoo_get_acl()
[ https://issues.apache.org/jira/browse/ZOOKEEPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar reassigned ZOOKEEPER-309: --- Assignee: Mahadev konar core dump using zoo_get_acl() -- Key: ZOOKEEPER-309 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-309 Project: Zookeeper Issue Type: Bug Components: c client Affects Versions: 3.0.0, 3.0.1, 3.1.0 Reporter: Chris Darroch Assignee: Mahadev konar Fix For: 3.1.1, 3.2.0 Attachments: ZOOKEEPER-309.patch, ZOOKEEPER-309.patch The zookeeper_process() function incorrectly calls the c.acl_result member of the completion_list_t structure when handling the completion from a synchronous zoo_get_acl() request. The c.acl_result member is set to SYNCHRONOUS_MARKER, which is a null pointer. The attached patch removes this call. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-309) core dump using zoo_get_acl()
[ https://issues.apache.org/jira/browse/ZOOKEEPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-309: Status: Patch Available (was: Open) core dump using zoo_get_acl() -- Key: ZOOKEEPER-309 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-309 Project: Zookeeper Issue Type: Bug Components: c client Affects Versions: 3.1.0, 3.0.1, 3.0.0 Reporter: Chris Darroch Assignee: Mahadev konar Fix For: 3.1.1, 3.2.0 Attachments: ZOOKEEPER-309.patch, ZOOKEEPER-309.patch The zookeeper_process() function incorrectly calls the c.acl_result member of the completion_list_t structure when handling the completion from a synchronous zoo_get_acl() request. The c.acl_result member is set to SYNCHRONOUS_MARKER, which is a null pointer. The attached patch removes this call. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-309) core dump using zoo_get_acl()
[ https://issues.apache.org/jira/browse/ZOOKEEPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681110#action_12681110 ] Mahadev konar commented on ZOOKEEPER-309: - also forgot to mention that the tests fail with segmenetation fault without chris's patch and pass with the patch.. core dump using zoo_get_acl() -- Key: ZOOKEEPER-309 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-309 Project: Zookeeper Issue Type: Bug Components: c client Affects Versions: 3.0.0, 3.0.1, 3.1.0 Reporter: Chris Darroch Assignee: Mahadev konar Fix For: 3.1.1, 3.2.0 Attachments: ZOOKEEPER-309.patch, ZOOKEEPER-309.patch The zookeeper_process() function incorrectly calls the c.acl_result member of the completion_list_t structure when handling the completion from a synchronous zoo_get_acl() request. The c.acl_result member is set to SYNCHRONOUS_MARKER, which is a null pointer. The attached patch removes this call. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-309) core dump using zoo_get_acl()
[ https://issues.apache.org/jira/browse/ZOOKEEPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-309: --- Resolution: Fixed Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Available) +1, good to see we are testing acls now in c client. ;-) Committed revision 752729. Committed revision 752730. core dump using zoo_get_acl() -- Key: ZOOKEEPER-309 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-309 Project: Zookeeper Issue Type: Bug Components: c client Affects Versions: 3.0.0, 3.0.1, 3.1.0 Reporter: Chris Darroch Assignee: Mahadev konar Fix For: 3.1.1, 3.2.0 Attachments: ZOOKEEPER-309.patch, ZOOKEEPER-309.patch The zookeeper_process() function incorrectly calls the c.acl_result member of the completion_list_t structure when handling the completion from a synchronous zoo_get_acl() request. The c.acl_result member is set to SYNCHRONOUS_MARKER, which is a null pointer. The attached patch removes this call. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-87) Follower does not shut itself down if its too far behind the leader.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-87: -- Component/s: quorum Follower does not shut itself down if its too far behind the leader. Key: ZOOKEEPER-87 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-87 Project: Zookeeper Issue Type: Bug Components: quorum Reporter: Mahadev konar Assignee: Mahadev konar Priority: Critical Fix For: 3.2.0 Currently, the follower if lagging behind keeps sending pings to the leader it will stay alive and will keep getting further and further behind the leader. The follower should shut itself down if it is not able to keep up to the leader within some limit so that gurantee of updates can be made to the clients connected to different servers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-30) Hooks for atomic broadcast protocol
[ https://issues.apache.org/jira/browse/ZOOKEEPER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-30: -- Component/s: quorum Hooks for atomic broadcast protocol --- Key: ZOOKEEPER-30 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-30 Project: Zookeeper Issue Type: New Feature Components: quorum Reporter: Patrick Hunt Assignee: Mahadev konar Moved from SourceForge to Apache. http://sourceforge.net/tracker/index.php?func=detailaid=1938788group_id=209147atid=1008547 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-152) Improve unit tests for leader election
[ https://issues.apache.org/jira/browse/ZOOKEEPER-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-152: --- Component/s: quorum Improve unit tests for leader election -- Key: ZOOKEEPER-152 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-152 Project: Zookeeper Issue Type: Improvement Components: quorum Reporter: Flavio Paiva Junqueira Priority: Minor There are two possible tasks here: 1- Change the algorithm tested on QuorumTest.java; 2- Add tests for the other supported algorithms. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-166) Content needed: Logging
[ https://issues.apache.org/jira/browse/ZOOKEEPER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-166: --- Component/s: documentation Content needed: Logging - Key: ZOOKEEPER-166 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-166 Project: Zookeeper Issue Type: Sub-task Components: documentation Reporter: Robbie Scott Original Estimate: 8h Remaining Estimate: 8h Content/information needed on Logging, from the point of view of the ZooKeeper Administrator -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-164) Content needed: Administering
[ https://issues.apache.org/jira/browse/ZOOKEEPER-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-164: --- Component/s: documentation Content needed: Administering --- Key: ZOOKEEPER-164 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-164 Project: Zookeeper Issue Type: Sub-task Components: documentation Reporter: Robbie Scott Original Estimate: 8h Remaining Estimate: 8h Content/Information needed on the day to day running, management, administering of a ZooKeeper deployment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-162) Content needed: Provisioning
[ https://issues.apache.org/jira/browse/ZOOKEEPER-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-162: --- Component/s: documentation Content needed: Provisioning Key: ZOOKEEPER-162 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-162 Project: Zookeeper Issue Type: Sub-task Components: documentation Reporter: Robbie Scott Original Estimate: 8h Remaining Estimate: 8h I need the content for the ZooKeeper Admin guide, for the section on Provisioning your zookeeper deployment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-237) Add a Chroot request
[ https://issues.apache.org/jira/browse/ZOOKEEPER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-237: --- Component/s: server java client c client Add a Chroot request Key: ZOOKEEPER-237 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-237 Project: Zookeeper Issue Type: New Feature Components: c client, java client, server Reporter: Benjamin Reed Priority: Minor It would be nice to be able to root ZooKeeper handles at specific points in the namespace, so that applications that use ZooKeeper can work in their own rooted subtree. For example, if ops decides that application X can use the subtree /apps/X and application Y can use the subtree /apps/Y, X can to a chroot to /apps/X and then all its path references can be rooted at /apps/X. Thus when X creates the path /myid, it will actually be creating the path /apps/X/myid. There are two ways we can expose this mechanism: 1) We can simply add a chroot(String path) API, or 2) we can integrate into a service identifier scheme for example zk://server1:2181,server2:2181/my/root. I like the second form personally. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-236) SSL Support for Atomic Broadcast protocol
[ https://issues.apache.org/jira/browse/ZOOKEEPER-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-236: --- Component/s: server quorum SSL Support for Atomic Broadcast protocol - Key: ZOOKEEPER-236 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-236 Project: Zookeeper Issue Type: New Feature Components: quorum, server Reporter: Benjamin Reed Priority: Minor We should have the ability to use SSL to authenticate and encrypt the traffic between ZooKeeper servers. For the most part this is a very easy change. We would probably only want to support this for TCP based leader elections. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-235) SSL Support for clients
[ https://issues.apache.org/jira/browse/ZOOKEEPER-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-235: --- Component/s: server java client c client SSL Support for clients --- Key: ZOOKEEPER-235 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-235 Project: Zookeeper Issue Type: New Feature Components: c client, java client, server Reporter: Benjamin Reed Priority: Minor ZooKeeper should be able to support SSL for ZooKeeper clients. As part of the implementation we should also add an X509AuthenticationProvider so that client side certifications can be used for authentication. The tricky part of the implementation will be integrating with the non-blocking NIO calls that we use. There are various web pages that describe how to do it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-233) Create a slimer jar for clients to reduce thier disk footprint.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-233: --- Component/s: java client build Create a slimer jar for clients to reduce thier disk footprint. --- Key: ZOOKEEPER-233 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-233 Project: Zookeeper Issue Type: New Feature Components: build, java client Reporter: Hiram Chirino Priority: Trivial Fix For: 3.2.0 Patrick request I open up this in issue in this [email thread|http://n2.nabble.com/ActiveMQ-is-now-using-ZooKeeper-td1573272.html] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-270) remove NoSyncConnected in KeeperState - it's not used anywhere in the codebase.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-270: --- Component/s: server java client remove NoSyncConnected in KeeperState - it's not used anywhere in the codebase. Key: ZOOKEEPER-270 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-270 Project: Zookeeper Issue Type: Bug Components: java client, server Reporter: Mahadev konar Fix For: 3.2.0 ZOOKEEPER-265 makes some constants deprecated. We should remove the deprecated stuff int the next release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-238) HostAuthenicationProvider should be removed
[ https://issues.apache.org/jira/browse/ZOOKEEPER-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-238: --- Component/s: server HostAuthenicationProvider should be removed --- Key: ZOOKEEPER-238 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-238 Project: Zookeeper Issue Type: Bug Components: server Reporter: Benjamin Reed I think the way the HostAuthenticationProvider is implemented could cause serious performance problems if DNS is slow or broken. The problem is that we need to do a reverse hostname resolution during connection establishment. I suggest it be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-282) the getchildren api in zookeeper should return an iterator.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-282: --- Component/s: server java client c client the getchildren api in zookeeper should return an iterator. --- Key: ZOOKEEPER-282 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-282 Project: Zookeeper Issue Type: Improvement Components: c client, java client, server Affects Versions: 3.0.0, 3.0.1, 3.1.0 Reporter: Mahadev konar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-300) zk jmx code is calling printStackTrace when creating bean name (should not be)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-300: --- Component/s: jmx zk jmx code is calling printStackTrace when creating bean name (should not be) -- Key: ZOOKEEPER-300 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-300 Project: Zookeeper Issue Type: Bug Components: jmx Affects Versions: 3.1.0 Reporter: Patrick Hunt Fix For: 3.2.0 remove printStackTrace from zk jmx code (review the rest of the code at the same time) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-321) optmize session tracking in zookeeper.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-321: --- Component/s: server java client c client Fix Version/s: 3.2.0 optmize session tracking in zookeeper. -- Key: ZOOKEEPER-321 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-321 Project: Zookeeper Issue Type: New Feature Components: c client, java client, server Reporter: Mahadev konar Fix For: 3.2.0 sometimes a lot of zookeeper clients are read only. For such clients we do not need the session tracking in zookeeper. Getting rid of session tracking for such clients will help us sclae much better. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-322) move examples out of docs into contrib/examples
[ https://issues.apache.org/jira/browse/ZOOKEEPER-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-322: --- Component/s: documentation Fix Version/s: 3.2.0 move examples out of docs into contrib/examples - Key: ZOOKEEPER-322 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-322 Project: Zookeeper Issue Type: Improvement Components: documentation Reporter: Mahadev konar Fix For: 3.2.0 move examples out of docs into contrib/examples -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-325) FLENewEpoch test fails.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-325: --- Component/s: quorum FLENewEpoch test fails. --- Key: ZOOKEEPER-325 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-325 Project: Zookeeper Issue Type: Bug Components: quorum Affects Versions: 3.1.0 Environment: linux 2.6.9-5.ELsmp Reporter: Mahadev konar Fix For: 3.2.0 Attachments: TEST-org.apache.zookeeper.test.FLENewEpochTest.txt FLENewEpochTest fails quite frequently on my machine. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-237) Add a Chroot request
[ https://issues.apache.org/jira/browse/ZOOKEEPER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-237: --- Fix Version/s: 3.2.0 Add a Chroot request Key: ZOOKEEPER-237 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-237 Project: Zookeeper Issue Type: New Feature Components: c client, java client, server Reporter: Benjamin Reed Priority: Minor Fix For: 3.2.0 It would be nice to be able to root ZooKeeper handles at specific points in the namespace, so that applications that use ZooKeeper can work in their own rooted subtree. For example, if ops decides that application X can use the subtree /apps/X and application Y can use the subtree /apps/Y, X can to a chroot to /apps/X and then all its path references can be rooted at /apps/X. Thus when X creates the path /myid, it will actually be creating the path /apps/X/myid. There are two ways we can expose this mechanism: 1) We can simply add a chroot(String path) API, or 2) we can integrate into a service identifier scheme for example zk://server1:2181,server2:2181/my/root. I like the second form personally. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-62) Generally improve logging to enable debuggability in the field.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-62: -- Fix Version/s: 3.2.0 Generally improve logging to enable debuggability in the field. --- Key: ZOOKEEPER-62 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-62 Project: Zookeeper Issue Type: Improvement Components: c client, java client, server Reporter: Patrick Hunt Assignee: Flavio Paiva Junqueira Fix For: 3.2.0 Attachments: zoo-log.tgz We need to improve our logging to enable debugging of field issues. Flavio, assigning to you as you are currently looking at some client/server issues that could benefit from better logging. Please attach patches if you see potential areas for improvement. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-59) Synchronized block in NIOServerCnxn
[
https://issues.apache.org/jira/browse/ZOOKEEPER-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-59:
--
Fix Version/s: 3.2.0
Whatever happened with this patch? Seems to have gotten dropped. re-investigate
for 3.2
Synchronized block in NIOServerCnxn
---
Key: ZOOKEEPER-59
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-59
Project: Zookeeper
Issue Type: Bug
Components: server
Reporter: Flavio Paiva Junqueira
Assignee: Flavio Paiva Junqueira
Fix For: 3.2.0
Attachments: ZOOKEEPER-59.patch
There are two synchronized blocks locking on different objects, and to me
they should be guarded by the same object. Here are the parts of the code I'm
talking about:
{noformat}
nioservercnxn.readrequ...@444
...
synchronized (this) {
outstandingRequests++;
// check throttling
if (zk.getInProcess() factory.outstandingLimit) {
disableRecv();
// following lines should not be needed since we are
already
// reading
// } else {
// enableRecv();
}
}
{noformat}
{noformat}
nioservercnxn.sendrespo...@740
...
synchronized (this.factory) {
outstandingRequests--;
// check throttling
if (zk.getInProcess() factory.outstandingLimit
|| outstandingRequests 1) {
sk.selector().wakeup();
enableRecv();
}
}
{noformat}
I think the second one is correct, and the first synchronized block should be
guarded by this.factory.
This could be related to issue ZOOKEEPER-57, but I have no concrete
indication that this is the case so far.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-94) JMX tests are needed to verify that the JMX MBeans work properly
[ https://issues.apache.org/jira/browse/ZOOKEEPER-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-94: -- Affects Version/s: 3.1.1 3.1.0 Fix Version/s: 3.2.0 JMX tests are needed to verify that the JMX MBeans work properly Key: ZOOKEEPER-94 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-94 Project: Zookeeper Issue Type: Bug Components: jmx Affects Versions: 3.1.0, 3.1.1 Reporter: Hiram Chirino Fix For: 3.2.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-304) factor out common methods from zookeeper.java
[ https://issues.apache.org/jira/browse/ZOOKEEPER-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-304: --- Component/s: server java client Fix Version/s: 3.2.0 factor out common methods from zookeeper.java - Key: ZOOKEEPER-304 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-304 Project: Zookeeper Issue Type: Improvement Components: java client, server Affects Versions: 3.1.0 Reporter: Mahadev konar Fix For: 3.2.0 we need to factor out common methods from zookeeper.java to a commons directory for zookeeper so that it can be used both in client and server without each of them depending on each other. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
