[jira] [Assigned] (ZOOKEEPER-1426) add version command to the zookeeper server
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Szecsi reassigned ZOOKEEPER-1426: --- Assignee: Eli Reisman (was: Peter Szecsi) > add version command to the zookeeper server > --- > > Key: ZOOKEEPER-1426 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1426 > Project: ZooKeeper > Issue Type: Improvement > Components: scripts, server >Affects Versions: 3.3.5 >Reporter: Patrick Hunt >Assignee: Eli Reisman >Priority: Major > Labels: newbie, patch, pull-request-available > Fix For: 3.6.0 > > Attachments: MAPREDUCE-4282-2.patch, ZOOKEEPER-1426-1.patch, > ZOOKEEPER-1426-2.patch, ZOOKEEPER-1426-3.patch > > Time Spent: 3h > Remaining Estimate: 0h > > Add a version command to the zkServer.sh. > Hadoop does this by having a special main class: > org.apache.hadoop.util.VersionInfo > We could do something similar, hook it into our current version information > class (perhaps add main to that class). > Would also need to add a new "version" command to zkServer.sh that calls this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ZOOKEEPER-1426) add version command to the zookeeper server
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Szecsi reassigned ZOOKEEPER-1426: --- Assignee: Peter Szecsi (was: Eli Reisman) > add version command to the zookeeper server > --- > > Key: ZOOKEEPER-1426 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1426 > Project: ZooKeeper > Issue Type: Improvement > Components: scripts, server >Affects Versions: 3.3.5 >Reporter: Patrick Hunt >Assignee: Peter Szecsi >Priority: Major > Labels: newbie, patch, pull-request-available > Fix For: 3.6.0 > > Attachments: MAPREDUCE-4282-2.patch, ZOOKEEPER-1426-1.patch, > ZOOKEEPER-1426-2.patch, ZOOKEEPER-1426-3.patch > > Time Spent: 3h > Remaining Estimate: 0h > > Add a version command to the zkServer.sh. > Hadoop does this by having a special main class: > org.apache.hadoop.util.VersionInfo > We could do something similar, hook it into our current version information > class (perhaps add main to that class). > Would also need to add a new "version" command to zkServer.sh that calls this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ZOOKEEPER-3402) Add a multiRead operation
Peter Szecsi created ZOOKEEPER-3402: --- Summary: Add a multiRead operation Key: ZOOKEEPER-3402 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3402 Project: ZooKeeper Issue Type: Improvement Reporter: Peter Szecsi Assignee: Peter Szecsi There is already an expressed need and desire from the community to support the multi version of the getData and getChildren operations. We could create a multiRead operation which behaves just like the multi, however, only accepts read operations. It would provide a common interface for batched read operations instead of different multi versions and the read operations could be even mixed in one request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ZOOKEEPER-3381) Add multi watchregistration support for multi getChildren
Peter Szecsi created ZOOKEEPER-3381:
---
Summary: Add multi watchregistration support for multi getChildren
Key: ZOOKEEPER-3381
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3381
Project: ZooKeeper
Issue Type: Improvement
Components: java client, tests
Affects Versions: 3.6.0
Reporter: Peter Szecsi
Assignee: Peter Szecsi
Currently, the client API only supports to register one watch attached to one
node for a single request. However, for complete support of the multi version
of the {{GetChildren}} this functionality needs to be extended.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ZOOKEEPER-1407) Support GetData and GetChildren in Multi
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832756#comment-16832756 ] Peter Szecsi commented on ZOOKEEPER-1407: - Hello guys, I have come up with a similar problem for getChildren, and created a Jira for that as well. ([ZOOKEEPER-3361|https://issues.apache.org/jira/browse/ZOOKEEPER-3361]) I hope you don't mind, I have added it as a subtask to this ticket when I found it. There is already a 2 open pull requests for supporting the "multi getChildren" operation in a way or another. ([pr-922|https://github.com/apache/zookeeper/pull/922/], [pr-929|https://github.com/apache/zookeeper/pull/929/]). I would be glad to work on this ticket and implement the multi version of getData as well. Would you be OK with it? Or [~zhi...@ebaysf.com], would you like to finish this yourself? > Support GetData and GetChildren in Multi > > > Key: ZOOKEEPER-1407 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1407 > Project: ZooKeeper > Issue Type: Improvement > Components: java client, server >Reporter: Ted Yu >Assignee: Ted Yu >Priority: Major > Fix For: 3.6.0, 3.5.6 > > Attachments: 1407-v2.txt, 1407-v3.txt, 1407-v4.txt, 1407-v5.txt, > 1407.txt > > > There is use case where GetData and GetChildren would participate in Multi. > We should add support for this case. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ZOOKEEPER-3361) Add multi version of getChildren request
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Szecsi updated ZOOKEEPER-3361:
Issue Type: Sub-task (was: Improvement)
Parent: ZOOKEEPER-1407
> Add multi version of getChildren request
>
>
> Key: ZOOKEEPER-3361
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3361
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: java client, server, tests
>Reporter: Peter Szecsi
>Assignee: Peter Szecsi
>Priority: Minor
> Labels: pull-request-available
> Original Estimate: 336h
> Time Spent: 1h
> Remaining Estimate: 335h
>
> There is already a multi operation for \{{delete, create, setData}}...
> However, \{{getChildren}} has no version of getting the children of multiple
> nodes by one message.
> This could heavily improve the efficiency of a traversal (e.g. breadth-first
> search) when the latency is high (>1ms). In this case, a simple
> \{{deleteAll}} algorithm on 10k nodes takes at least (1ms * 1 * 2 =) 20
> sec, only to acquire the list of the nodes selected for deleting (it has to
> check for every node whether it has children or not).
> I would add a version of \{{getChildren}} function to the ZooKeeper API which
> accepts lists as well (containing node paths) and returns their children and
> introduce a new request type. This way the backward compabilty would not be
> hurt but ZK could provide a more robust solution for those who may have
> latency issues.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ZOOKEEPER-3374) Use GetChildrenList in the BFS utility
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Szecsi updated ZOOKEEPER-3374:
Description:
The multi-version of {{getChildren}} function allows us to traverse a tree
using fewer requests to the server. At the moment, the number of requests for
traversal is the same as the number of nodes, however, this can be changed to
only use up as many requests as the height of the tree.
Currently, {{listSubTreeBFS}} utility function used for the deleteAll command
and this improvement makes it more robust, especially in high latency setups.
was:
The multi-version of getChildren function allows us to traverse a tree using
fewer requests to the server. At the moment, the number of requests for
traversal is the same as the number of nodes, however, this can be changed to
only use up as many requests as the height of the tree.
> Use GetChildrenList in the BFS utility
> --
>
> Key: ZOOKEEPER-3374
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3374
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client
>Affects Versions: 3.6.0
>Reporter: Peter Szecsi
>Assignee: Peter Szecsi
>Priority: Minor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> The multi-version of {{getChildren}} function allows us to traverse a tree
> using fewer requests to the server. At the moment, the number of requests for
> traversal is the same as the number of nodes, however, this can be changed to
> only use up as many requests as the height of the tree.
> Currently, {{listSubTreeBFS}} utility function used for the deleteAll command
> and this improvement makes it more robust, especially in high latency setups.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ZOOKEEPER-3374) Use GetChildrenList in the BFS utility
Peter Szecsi created ZOOKEEPER-3374: --- Summary: Use GetChildrenList in the BFS utility Key: ZOOKEEPER-3374 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3374 Project: ZooKeeper Issue Type: Improvement Components: java client Affects Versions: 3.6.0 Reporter: Peter Szecsi Assignee: Peter Szecsi The multi-version of getChildren function allows us to traverse a tree using fewer requests to the server. At the moment, the number of requests for traversal is the same as the number of nodes, however, this can be changed to only use up as many requests as the height of the tree. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ZOOKEEPER-3361) Add multi version of getChildren request
Peter Szecsi created ZOOKEEPER-3361:
---
Summary: Add multi version of getChildren request
Key: ZOOKEEPER-3361
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3361
Project: ZooKeeper
Issue Type: Improvement
Components: java client, server, tests
Reporter: Peter Szecsi
Assignee: Peter Szecsi
There is already a multi operation for \{{delete, create, setData}}... However,
\{{getChildren}} has no version of getting the children of multiple nodes by
one message.
This could heavily improve the efficiency of a traversal (e.g. breadth-first
search) when the latency is high (>1ms). In this case, a simple \{{deleteAll}}
algorithm on 10k nodes takes at least (1ms * 1 * 2 =) 20 sec, only to
acquire the list of the nodes selected for deleting (it has to check for every
node whether it has children or not).
I would add a version of \{{getChildren}} function to the ZooKeeper API which
accepts lists as well (containing node paths) and returns their children and
introduce a new request type. This way the backward compabilty would not be
hurt but ZK could provide a more robust solution for those who may have latency
issues.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
