[jira] [Commented] (ZOOKEEPER-2251) Add Client side packet response timeout to avoid infinite wait.

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734548#comment-15734548 ] Michael Han commented on ZOOKEEPER-2251: Has anyone that watching this issue able to have a

[GitHub] zookeeper pull request #119: ZOOKEEPER-2251:Add Client side packet response ...

Github user hanm commented on a diff in the pull request: https://github.com/apache/zookeeper/pull/119#discussion_r9147 --- Diff: src/java/main/org/apache/zookeeper/ClientCnxn.java --- @@ -1495,10 +1504,21 @@ public ReplyHeader submitRequest(RequestHeader h, Record request,

[jira] [Commented] (ZOOKEEPER-2251) Add Client side packet response timeout to avoid infinite wait.

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734535#comment-15734535 ] ASF GitHub Bot commented on ZOOKEEPER-2251: --- Github user hanm commented on a diff in the

[jira] [Commented] (ZOOKEEPER-2251) Add Client side packet response timeout to avoid infinite wait.

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734534#comment-15734534 ] ASF GitHub Bot commented on ZOOKEEPER-2251: --- Github user hanm commented on a diff in the

[jira] [Commented] (ZOOKEEPER-2251) Add Client side packet response timeout to avoid infinite wait.

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734533#comment-15734533 ] ASF GitHub Bot commented on ZOOKEEPER-2251: --- Github user hanm commented on a diff in the

[GitHub] zookeeper pull request #119: ZOOKEEPER-2251:Add Client side packet response ...

Github user hanm commented on a diff in the pull request: https://github.com/apache/zookeeper/pull/119#discussion_r91666945 --- Diff: src/java/main/org/apache/zookeeper/KeeperException.java --- @@ -387,6 +389,8 @@ public void setCode(int code) { EPHEMERALONLOCALSESSION

[GitHub] zookeeper pull request #119: ZOOKEEPER-2251:Add Client side packet response ...

Github user hanm commented on a diff in the pull request: https://github.com/apache/zookeeper/pull/119#discussion_r91666999 --- Diff: src/docs/src/documentation/content/xdocs/zookeeperProgrammers.xml --- @@ -1538,6 +1538,24 @@ public abstract class ServerAuthenticationProvider

[jira] [Commented] (ZOOKEEPER-261) Reinitialized servers should not participate in leader election

[ https://issues.apache.org/jira/browse/ZOOKEEPER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734431#comment-15734431 ] ASF GitHub Bot commented on ZOOKEEPER-261: -- Github user hanm commented on the issue:

[GitHub] zookeeper issue #120: ZOOKEEPER-261

Github user hanm commented on the issue: https://github.com/apache/zookeeper/pull/120 lgtm +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

ZooKeeper-trunk-WinVS2008 - Build # 2353 - Still Failing

See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/2353/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 78 lines...] ivy-retrieve: [ivy:retrieve] ::

ZooKeeper_branch34_jdk7 - Build # 1317 - Failure

See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/1317/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 231117 lines...] [junit] 2016-12-09

[jira] [Commented] (ZOOKEEPER-1045) Support Quorum Peer mutual authentication via SASL

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733973#comment-15733973 ] Rakesh R commented on ZOOKEEPER-1045: - Thanks [~hanm] for adding that point. IIUC, this has to be

[jira] [Commented] (ZOOKEEPER-1045) Support Quorum Peer mutual authentication via SASL

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733923#comment-15733923 ] Michael Han commented on ZOOKEEPER-1045: Sounds good. These captures the following up work to

Re: reconfig APIs

Thanks for the replies everyone. Adding the methods back with a deprecation notice solves Curator’s problems so I’ll proceed with that on ZOOKEEPER-2642. -Jordan > On Dec 8, 2016, at 6:56 PM, Michael Han wrote: > > Thanks Jordan for raising the concern. It's a reasonable

[jira] [Commented] (ZOOKEEPER-2517) jute.maxbuffer is ignored

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733566#comment-15733566 ] ASF GitHub Bot commented on ZOOKEEPER-2517: --- Github user hanm commented on the issue:

[GitHub] zookeeper issue #113: ZOOKEEPER-2517:jute.maxbuffer is ignored

Github user hanm commented on the issue: https://github.com/apache/zookeeper/pull/113 @rgs1 this is the blocker issue we were talking about, please take a look at it. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

Success: ZOOKEEPER- PreCommit Build #107

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/107/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 470368 lines...] [exec] +1

[jira] [Commented] (ZOOKEEPER-261) Reinitialized servers should not participate in leader election

[ https://issues.apache.org/jira/browse/ZOOKEEPER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733423#comment-15733423 ] ASF GitHub Bot commented on ZOOKEEPER-261: -- Github user enixon commented on the issue:

[GitHub] zookeeper issue #120: ZOOKEEPER-261

Github user enixon commented on the issue: https://github.com/apache/zookeeper/pull/120 - add documentation on 'zookeeper.db.autocreate' to zookeeperAdmin.xml - extend bin/zkServer-initialize.sh to create the initialize file - treat failure to delete initialization file as

Re: reconfig APIs

Thanks Jordan for raising the concern. It's a reasonable concern with good intention to make user's life easier, which is important to the project. There are two separate issues we need to reach a consensus here: * Move reconfig API The details of why the decision was made is documented in

ZooKeeper_branch35_solaris - Build # 344 - Still Failing

See https://builds.apache.org/job/ZooKeeper_branch35_solaris/344/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 464344 lines...] [junit] 2016-12-08

Re: reconfig APIs

I've only seen a few questions about versioning come up on the ZK lists, they were quickly responded to with pointers to the process. iirc we based our versioning scheme on what Hadoop was/is using. Additionally if we don't allow for alpha time it will further slow progress as there will be no

Re: Upcoming 3.4/3.5 releases.

The inclusion of ZOOKEEPER-2014 has been raised as a problem by Jordan (see the separate thread on this list). I don't feel I can cut a 3.5.3-alpha release until the issue has been resolved by the community. I was hoping to get a release candidate created before vacation starts, so please comment

ZooKeeper_branch34_solaris - Build # 1382 - Still Failing

See https://builds.apache.org/job/ZooKeeper_branch34_solaris/1382/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 187566 lines...] [junit] 2016-12-08

ZooKeeper_branch35_jdk8 - Build # 327 - Failure

See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/327/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 485988 lines...] [junit] 2016-12-08

ZooKeeper-trunk-jdk8 - Build # 849 - Still Failing

See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/849/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 449473 lines...] [junit] at

ZooKeeper_branch35_openjdk7 - Build # 324 - Still Failing

See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/324/ ### ## LAST 60 LINES OF THE CONSOLE ### Started by timer [EnvInject] - Loading node environment

Re: reconfig APIs

> I think people understand what alpha means. With respect, the ZooKeeper team has used “alpha” in a novel way that is sowing considerable confusion. I wrote emails about this a while back. But, here again, is another case where the non-standard usage of “alpha” will cause confusion. To