[jira] Created: (ZOOKEEPER-740) zkpython leading to segfault on zookeeper
zkpython leading to segfault on zookeeper - Key: ZOOKEEPER-740 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-740 Project: Zookeeper Issue Type: Bug Affects Versions: 3.3.0 Reporter: Federico Priority: Critical Fix For: 3.3.1 The program that we are implementing uses the python binding for zookeeper but sometimes it crash with segfault; here is the bt from gdb: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xad244b70 (LWP 28216)] 0x080611d5 in PyObject_Call (func=0x862fab0, arg=0x8837194, kw=0x0) at ../Objects/abstract.c:2488 2488../Objects/abstract.c: No such file or directory. in ../Objects/abstract.c (gdb) bt #0 0x080611d5 in PyObject_Call (func=0x862fab0, arg=0x8837194, kw=0x0) at ../Objects/abstract.c:2488 #1 0x080d6ef2 in PyEval_CallObjectWithKeywords (func=0x862fab0, arg=0x8837194, kw=0x0) at ../Python/ceval.c:3575 #2 0x080612a0 in PyObject_CallObject (o=0x862fab0, a=0x8837194) at ../Objects/abstract.c:2480 #3 0x0047af42 in watcher_dispatch (zzh=0x86174e0, type=-1, state=1, path=0x86337c8 "", context=0x8588660) at src/c/zookeeper.c:314 #4 0x00496559 in do_foreach_watcher (zh=0x86174e0, type=-1, state=1, path=0x86337c8 "", list=0xa5354140) at src/zk_hashtable.c:275 #5 deliverWatchers (zh=0x86174e0, type=-1, state=1, path=0x86337c8 "", list=0xa5354140) at src/zk_hashtable.c:317 #6 0x0048ae3c in process_completions (zh=0x86174e0) at src/zookeeper.c:1766 #7 0x0049706b in do_completion (v=0x86174e0) at src/mt_adaptor.c:333 #8 0x0013380e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #9 0x002578de in clone () from /lib/tls/i686/cmov/libc.so.6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ZOOKEEPER-729) Recursively delete a znode - zkCli.sh rmr /node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Kay updated ZOOKEEPER-729: -- Attachment: ZOOKEEPER-729.patch > Recursively delete a znode - zkCli.sh rmr /node > > > Key: ZOOKEEPER-729 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-729 > Project: Zookeeper > Issue Type: New Feature > Components: java client >Reporter: Kay Kay >Assignee: Kay Kay > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-729.patch, ZOOKEEPER-729.patch, > ZOOKEEPER-729.patch, ZOOKEEPER-729.patch, ZOOKEEPER-729.patch > > > Recursively delete a given znode in zookeeper, from the command-line. > New operation "rmr" added to zkclient. > $ ./zkCli.sh rmr /node -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ZOOKEEPER-729) Recursively delete a znode - zkCli.sh rmr /node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Kay updated ZOOKEEPER-729: -- Status: Open (was: Patch Available) > Recursively delete a znode - zkCli.sh rmr /node > > > Key: ZOOKEEPER-729 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-729 > Project: Zookeeper > Issue Type: New Feature > Components: java client >Reporter: Kay Kay >Assignee: Kay Kay > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-729.patch, ZOOKEEPER-729.patch, > ZOOKEEPER-729.patch, ZOOKEEPER-729.patch, ZOOKEEPER-729.patch > > > Recursively delete a given znode in zookeeper, from the command-line. > New operation "rmr" added to zkclient. > $ ./zkCli.sh rmr /node -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ZOOKEEPER-729) Recursively delete a znode - zkCli.sh rmr /node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Kay updated ZOOKEEPER-729: -- Attachment: (was: ZOOKEEPER-729.patch) > Recursively delete a znode - zkCli.sh rmr /node > > > Key: ZOOKEEPER-729 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-729 > Project: Zookeeper > Issue Type: New Feature > Components: java client >Reporter: Kay Kay >Assignee: Kay Kay > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-729.patch, ZOOKEEPER-729.patch, > ZOOKEEPER-729.patch, ZOOKEEPER-729.patch, ZOOKEEPER-729.patch > > > Recursively delete a given znode in zookeeper, from the command-line. > New operation "rmr" added to zkclient. > $ ./zkCli.sh rmr /node -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ZOOKEEPER-729) Recursively delete a znode - zkCli.sh rmr /node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Kay updated ZOOKEEPER-729: -- Attachment: ZOOKEEPER-729.patch > Recursively delete a znode - zkCli.sh rmr /node > > > Key: ZOOKEEPER-729 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-729 > Project: Zookeeper > Issue Type: New Feature > Components: java client >Reporter: Kay Kay >Assignee: Kay Kay > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-729.patch, ZOOKEEPER-729.patch, > ZOOKEEPER-729.patch, ZOOKEEPER-729.patch, ZOOKEEPER-729.patch > > > Recursively delete a given znode in zookeeper, from the command-line. > New operation "rmr" added to zkclient. > $ ./zkCli.sh rmr /node -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ZOOKEEPER-729) Recursively delete a znode - zkCli.sh rmr /node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Kay updated ZOOKEEPER-729: -- Status: Patch Available (was: Open) > Recursively delete a znode - zkCli.sh rmr /node > > > Key: ZOOKEEPER-729 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-729 > Project: Zookeeper > Issue Type: New Feature > Components: java client >Reporter: Kay Kay >Assignee: Kay Kay > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-729.patch, ZOOKEEPER-729.patch, > ZOOKEEPER-729.patch, ZOOKEEPER-729.patch, ZOOKEEPER-729.patch > > > Recursively delete a given znode in zookeeper, from the command-line. > New operation "rmr" added to zkclient. > $ ./zkCli.sh rmr /node -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Sendmail restartd for patch process
Folks, It looks like sendmail process on hudson.zones crashed and all the test patch jobs submitted in the last two days didn't get through. Please resubmit your patch to the test-patch job. -Giri
[jira] Commented: (ZOOKEEPER-729) Recursively delete a znode - zkCli.sh rmr /node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856612#action_12856612 ] Kay Kay commented on ZOOKEEPER-729: --- fyi - build # 55 is green with the latest patch. > Recursively delete a znode - zkCli.sh rmr /node > > > Key: ZOOKEEPER-729 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-729 > Project: Zookeeper > Issue Type: New Feature > Components: java client >Reporter: Kay Kay >Assignee: Kay Kay > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-729.patch, ZOOKEEPER-729.patch, > ZOOKEEPER-729.patch, ZOOKEEPER-729.patch, ZOOKEEPER-729.patch > > > Recursively delete a given znode in zookeeper, from the command-line. > New operation "rmr" added to zkclient. > $ ./zkCli.sh rmr /node -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[GSoC] Zookeeper DNS Server
Hello, My name is Diana Tiriplica and I have applied for the Zookeeper DNS project at Google Summer of Code. I am very enthusiastic about this project and would be very happy if I had been accepted to work on it. I have been in frequent contact with the mentor, Henry Robinson, but would very much appreciate your opinion regarding my application. Is there anything else you would like from me ? What do you think of my proposal ? I am very confident that I am up to this task. Here[1] is a draft of my application. [1]:http://docs.google.com/View?id=ddd8j3v8_25f5qk3rcd Thank you very much and I am looking forward to your feedback! Diana Tiriplica
[jira] Commented: (ZOOKEEPER-740) zkpython leading to segfault on zookeeper
[ https://issues.apache.org/jira/browse/ZOOKEEPER-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856627#action_12856627 ] Henry Robinson commented on ZOOKEEPER-740: -- Thanks for the bug report, Federico. There are a few similar issues with zkpython that are surely related - I must make sure to address them soon. Can you let me know what version of Python and what operating system you are running? > zkpython leading to segfault on zookeeper > - > > Key: ZOOKEEPER-740 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-740 > Project: Zookeeper > Issue Type: Bug >Affects Versions: 3.3.0 >Reporter: Federico >Priority: Critical > Fix For: 3.3.1 > > > The program that we are implementing uses the python binding for zookeeper > but sometimes it crash with segfault; here is the bt from gdb: > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0xad244b70 (LWP 28216)] > 0x080611d5 in PyObject_Call (func=0x862fab0, arg=0x8837194, kw=0x0) > at ../Objects/abstract.c:2488 > 2488../Objects/abstract.c: No such file or directory. > in ../Objects/abstract.c > (gdb) bt > #0 0x080611d5 in PyObject_Call (func=0x862fab0, arg=0x8837194, kw=0x0) > at ../Objects/abstract.c:2488 > #1 0x080d6ef2 in PyEval_CallObjectWithKeywords (func=0x862fab0, > arg=0x8837194, kw=0x0) at ../Python/ceval.c:3575 > #2 0x080612a0 in PyObject_CallObject (o=0x862fab0, a=0x8837194) > at ../Objects/abstract.c:2480 > #3 0x0047af42 in watcher_dispatch (zzh=0x86174e0, type=-1, state=1, > path=0x86337c8 "", context=0x8588660) at src/c/zookeeper.c:314 > #4 0x00496559 in do_foreach_watcher (zh=0x86174e0, type=-1, state=1, > path=0x86337c8 "", list=0xa5354140) at src/zk_hashtable.c:275 > #5 deliverWatchers (zh=0x86174e0, type=-1, state=1, path=0x86337c8 "", > list=0xa5354140) at src/zk_hashtable.c:317 > #6 0x0048ae3c in process_completions (zh=0x86174e0) at src/zookeeper.c:1766 > #7 0x0049706b in do_completion (v=0x86174e0) at src/mt_adaptor.c:333 > #8 0x0013380e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 > #9 0x002578de in clone () from /lib/tls/i686/cmov/libc.so.6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (ZOOKEEPER-679) Offers a node design for interacting with the Java Zookeeper client.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856642#action_12856642 ] Mahadev konar commented on ZOOKEEPER-679: - aaron, i was looking at the patch. I think we should move the source and the tests to src/contrib/ztree. It would be more appropriate as a contrib module. Do you want to upload a new patch with this as a contrib module. Please take a look at src/contrib on how to make this as a contrib module. > Offers a node design for interacting with the Java Zookeeper client. > > > Key: ZOOKEEPER-679 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-679 > Project: Zookeeper > Issue Type: New Feature > Components: contrib, java client, tests >Reporter: Aaron Crow >Assignee: Aaron Crow > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-679.patch, ZOOKEEPER-679.patch, > ZOOKEEPER-679.patch > > > Following up on my conversations with Patrick and Mahadev > (http://n2.nabble.com/Might-I-contribute-a-Node-design-for-the-Java-API-td4567695.html#a4567695). > This patch includes the implementation as well as unit tests. The first unit > test gives a simple high level demo of using the node API. > The current implementation is simple and is only what I need withe current > project I am working on. However, I am very open to any and all suggestions > for improvement. > This is a proposal to support a simplified node (or File) like API into a > Zookeeper tree, by wrapping the Zookeeper Java client. It is similar to > Java's File API design. > Although, I'm trying to make it easier in a few spots. For example, deleting > a Node recursively is done by default. I also lean toward resolving > Exceptions "under the hood" when it seems appropriate. For example, if you > ask a Node if it exists, and its parent doesn't even exist, you just get a > false back (rather than a nasty Exception). > As for watches and ephemeral nodes, my current work does not need these > things so I currently have no handling of them. But if potential users of > the "Node a.k.a. File" design want these things, I'd be open to supporting > them as reasonable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ZOOKEEPER-679) Offers a node design for interacting with the Java Zookeeper client.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-679: Status: Open (was: Patch Available) > Offers a node design for interacting with the Java Zookeeper client. > > > Key: ZOOKEEPER-679 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-679 > Project: Zookeeper > Issue Type: New Feature > Components: contrib, java client, tests >Reporter: Aaron Crow >Assignee: Aaron Crow > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-679.patch, ZOOKEEPER-679.patch, > ZOOKEEPER-679.patch > > > Following up on my conversations with Patrick and Mahadev > (http://n2.nabble.com/Might-I-contribute-a-Node-design-for-the-Java-API-td4567695.html#a4567695). > This patch includes the implementation as well as unit tests. The first unit > test gives a simple high level demo of using the node API. > The current implementation is simple and is only what I need withe current > project I am working on. However, I am very open to any and all suggestions > for improvement. > This is a proposal to support a simplified node (or File) like API into a > Zookeeper tree, by wrapping the Zookeeper Java client. It is similar to > Java's File API design. > Although, I'm trying to make it easier in a few spots. For example, deleting > a Node recursively is done by default. I also lean toward resolving > Exceptions "under the hood" when it seems appropriate. For example, if you > ask a Node if it exists, and its parent doesn't even exist, you just get a > false back (rather than a nasty Exception). > As for watches and ephemeral nodes, my current work does not need these > things so I currently have no handling of them. But if potential users of > the "Node a.k.a. File" design want these things, I'd be open to supporting > them as reasonable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
