[jira] Updated: (ZOOKEEPER-732) Improper translation of error into Python exception
[
https://issues.apache.org/jira/browse/ZOOKEEPER-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Savu updated ZOOKEEPER-732:
--
Attachment: ZOOKEEPER-732.patch
I've fixed the patch to also include {{ZCLOSING}} and {{ZNOTHING}}. It seems
like all the error codes listed in {{zookeeper.h}} {{ZOO_ERRORS}} enum are now
handled by {{err_to_exception}}.
Improper translation of error into Python exception
---
Key: ZOOKEEPER-732
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-732
Project: Zookeeper
Issue Type: Bug
Components: contrib-bindings
Affects Versions: 3.2.2
Reporter: Gustavo Niemeyer
Assignee: Lei Zhang
Priority: Minor
Attachments: ZOOKEEPER-732.patch, ZOOKEEPER-732.patch
Apparently errors returned by the C library are not being correctly converted
into a Python exception in some cases:
zookeeper.get_children(0, /, None)
Traceback (most recent call last):
File stdin, line 1, in module
SystemError: error return without exception set
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-732) Improper translation of error into Python exception
[ https://issues.apache.org/jira/browse/ZOOKEEPER-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated ZOOKEEPER-732: Status: Patch Available (was: Open) Release Note: Client that uses python binding may receive SystemError on session expiration. Affects Version/s: 3.3.0 (was: 3.2.2) Improper translation of error into Python exception --- Key: ZOOKEEPER-732 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-732 Project: Zookeeper Issue Type: Bug Components: contrib-bindings Affects Versions: 3.3.0 Reporter: Gustavo Niemeyer Assignee: Lei Zhang Priority: Minor Attachments: ZOOKEEPER-732.patch, ZOOKEEPER-732.patch Apparently errors returned by the C library are not being correctly converted into a Python exception in some cases: zookeeper.get_children(0, /, None) Traceback (most recent call last): File stdin, line 1, in module SystemError: error return without exception set -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-732) Improper translation of error into Python exception
[ https://issues.apache.org/jira/browse/ZOOKEEPER-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated ZOOKEEPER-732: Status: Resolved (was: Patch Available) Hadoop Flags: [Reviewed] Fix Version/s: 3.3.2 Resolution: Fixed Improper translation of error into Python exception --- Key: ZOOKEEPER-732 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-732 Project: Zookeeper Issue Type: Bug Components: contrib-bindings Affects Versions: 3.3.0 Reporter: Gustavo Niemeyer Assignee: Lei Zhang Priority: Minor Fix For: 3.3.2 Attachments: ZOOKEEPER-732.patch, ZOOKEEPER-732.patch Apparently errors returned by the C library are not being correctly converted into a Python exception in some cases: zookeeper.get_children(0, /, None) Traceback (most recent call last): File stdin, line 1, in module SystemError: error return without exception set -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-809) Improved REST Interface
[ https://issues.apache.org/jira/browse/ZOOKEEPER-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Savu updated ZOOKEEPER-809: -- Attachment: ZOOKEEPER-809.patch In this patch I've added: * a bunch of classes for parsing the configuration file * per context HTTP Digest authentication settings * per context ZooKeeper digest authentication settings * support for chroot when parsing the hostPort string By using these features you can easily create secure channels from your application to ZooKeeper ( HTTPS + Digest Authentication + ZK Auth + chroot). It doesn't support the whole API but it should be really useful for configuration management. Working on: * support for ACLs: read and update * per session ZooKeeper authentication Sample config for a channel: rest.port = 9998 rest.endpoint.1 = /channel;localhost:2181,localhost:2182,localhost:2183/app rest.endpoint.1.http.auth = user:pass,user2:pass2 rest.endpoint.1.zk.digest = appuser:pass .. you should also enable SSL because the browser sends the password as plain text rest.ssl = true rest.ssl.jks = keys/rest.jks rest.ssl.jks.pass = 123456 Improved REST Interface --- Key: ZOOKEEPER-809 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-809 Project: Zookeeper Issue Type: Improvement Components: contrib Reporter: Andrei Savu Assignee: Andrei Savu Attachments: SPEC.txt, SPEC.txt, ZOOKEEPER-809.patch, ZOOKEEPER-809.patch, ZOOKEEPER-809.patch, ZOOKEEPER-809.patch I would like to extend the existing REST Interface to also support: * configuration * ephemeral znodes * watches - PubSubHubbub * ACLs * basic authentication I want to do this because when building web applications that talks directly to ZooKeeper a REST API it's a lot easier to use (there is no protocol mismatch) than an API that uses persistent connections. I plan to use the improved version to build a web-based administrative interface. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-732) Improper translation of error into Python exception
[ https://issues.apache.org/jira/browse/ZOOKEEPER-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12898156#action_12898156 ] Lei Zhang commented on ZOOKEEPER-732: - Thanks Andrei. Patch looks good to me. Improper translation of error into Python exception --- Key: ZOOKEEPER-732 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-732 Project: Zookeeper Issue Type: Bug Components: contrib-bindings Affects Versions: 3.3.0 Reporter: Gustavo Niemeyer Assignee: Lei Zhang Priority: Minor Fix For: 3.3.2 Attachments: ZOOKEEPER-732.patch, ZOOKEEPER-732.patch Apparently errors returned by the C library are not being correctly converted into a Python exception in some cases: zookeeper.get_children(0, /, None) Traceback (most recent call last): File stdin, line 1, in module SystemError: error return without exception set -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-847) Missing ack-Check in Zookeeper create
Missing ack-Check in Zookeeper create - Key: ZOOKEEPER-847 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-847 Project: Zookeeper Issue Type: Bug Components: java client Affects Versions: 3.3.1 Reporter: Patrick Datko I watched the source of zookeeper class and i missed an ack-check in the asynchronous version of the create operation. Is there any reason, that in the asynch version is no check whether the ack is valid, or did someone forget to implement it. It's interesting because we worked on a refactoring of the zookeeper client and don't want to implement a bug. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-808) Web-based Administrative Interface
[ https://issues.apache.org/jira/browse/ZOOKEEPER-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12898257#action_12898257 ] Andrei Savu commented on ZOOKEEPER-808: --- The web-based administrative interface is available on Github as a Hue app. Repository: http://github.com/andreisavu/hue/tree/zookeeper-browser/ Branch: zookeeper-browser App: zkui It requires the lates Hue release (1.0). Web-based Administrative Interface -- Key: ZOOKEEPER-808 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-808 Project: Zookeeper Issue Type: New Feature Components: contrib Reporter: Andrei Savu Assignee: Andrei Savu Implement a web-based administrative interface that should allow the user to perform all the tasks that can be done using the interactive shell (zkCli.sh) from a browser. It should also display cluster and individual server info extracted using the 4letter word commands. I'm going to build starting from the http://github.com/phunt/zookeeper_dashboard implemented by Patrick Hunt. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-847) Missing acl check in zookeeper create
[
https://issues.apache.org/jira/browse/ZOOKEEPER-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Koch updated ZOOKEEPER-847:
--
Summary: Missing acl check in zookeeper create (was: Missing ack-Check
in Zookeeper create)
Description:
I watched the source of the zookeeper class and I missed an acl check in the
asynchronous version of the create operation. Is there any reason, that in the
asynch version is no
check whether the acl is valid, or did someone forget to implement it. It's
interesting because we worked on a refactoring of the zookeeper client and
don't want to implement a bug.
The following code is missing:
if (acl != null acl.size() == 0) {
throw new KeeperException.InvalidACLException();
}
was:
I watched the source of zookeeper class and i missed an ack-check in the
asynchronous version of the create operation. Is there any reason, that in the
asynch version is no
check whether the ack is valid, or did someone forget to implement it. It's
interesting because we worked on a refactoring of the zookeeper client and
don't want to implement a bug.
s/ack/acl/, fixed spelling, added code snippet in question
Missing acl check in zookeeper create
-
Key: ZOOKEEPER-847
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-847
Project: Zookeeper
Issue Type: Bug
Components: java client
Affects Versions: 3.3.1
Reporter: Patrick Datko
I watched the source of the zookeeper class and I missed an acl check in the
asynchronous version of the create operation. Is there any reason, that in
the asynch version is no
check whether the acl is valid, or did someone forget to implement it. It's
interesting because we worked on a refactoring of the zookeeper client and
don't want to implement a bug.
The following code is missing:
if (acl != null acl.size() == 0) {
throw new KeeperException.InvalidACLException();
}
--
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-tabpanelfocusedCommentId=12898471#action_12898471 ] Abmar Barros commented on ZOOKEEPER-702: I was thinking of adding a new parameter to the adaptive methods, that is the minimum window size to begin performing timeout adaptation. As we noticed, adaptive methods can get benefit of a large window size, and there can be premature false suspicion if we do not know the behaviour of the network. In this case, the methods will start using a static timeout until the window reaches a certain size. What do you think? 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, 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] Updated: (ZOOKEEPER-831) BookKeeper: Throttling improved for reads
[ https://issues.apache.org/jira/browse/ZOOKEEPER-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Junqueira updated ZOOKEEPER-831: --- Status: Patch Available (was: Open) BookKeeper: Throttling improved for reads - Key: ZOOKEEPER-831 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-831 Project: Zookeeper Issue Type: Bug Components: contrib-bookkeeper Affects Versions: 3.3.1 Reporter: Flavio Junqueira Assignee: Flavio Junqueira Fix For: 3.4.0 Attachments: ZOOKEEPER-831.patch, ZOOKEEPER-831.patch Reads and writes in BookKeeper are asymmetric: a write request writes one entry, whereas a read request may read multiple requests. The current implementation of throttling only counts the number of read requests instead of counting the number of entries being read. Consequently, a few read requests reading a large number of entries each will spawn a large number of read-entry requests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
