Success: ZOOKEEPER- PreCommit Build #95

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

[jira] [Commented] (ZOOKEEPER-2325) Data inconsistency if all snapshots empty or missing

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15710994#comment-15710994 ] Hadoop QA commented on ZOOKEEPER-2325: -- +1 overall. GitHub Pull Request Build +1

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

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

Re: How to determine if the node is PERSISTENT & SEQUENTIAL

Hi Edward, I think the key problem is not making it up to date, but copy the information of the sequence. Thinking about the following example: we say source have seq node /test5. Then I copy it to destination cluster, but create a non-seq node instead. After some while, the other application

[jira] [Commented] (ZOOKEEPER-2325) Data inconsistency if all snapshots empty or missing

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

[GitHub] zookeeper pull request #117: ZOOKEEPER-2325: Data inconsistency if all snaps...

Github user lvfangmin commented on a diff in the pull request: https://github.com/apache/zookeeper/pull/117#discussion_r90368114 --- Diff: src/java/main/org/apache/zookeeper/server/persistence/FileTxnSnapLog.java --- @@ -165,8 +165,22 @@ public File getSnapDir() { */

Re: committing doc changes

we could also build the doc as part of the tests. On Wed, Nov 30, 2016 at 3:26 PM, Flavio Junqueira wrote: > As part of the release process, we only copy the documentation, see it here: > > https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToRelease >

Re: committing doc changes

As part of the release process, we only copy the documentation, see it here: https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToRelease I think the reason we have gone this way is to avoid issues compiling the

Re: committing doc changes

yeah, that's a deeper question. pat or flavio can correct me on this, but i think the reason we check it in is so that the website's "trunk" documentation will work. now that we moved to git, i don't thing it works though... i also would just like to only build it when we do releases. On Wed, Nov

Re: committing doc changes

+1 on the idea of separating doc source change with doc binary change. Actually, should we just remove the binary doc from source repository given they are artifacts that's only relevant to a release build (instead of source)? On Wed, Nov 30, 2016 at 2:24 PM, Jordan Zimmerman <

Re: committing doc changes

I wondered about that myself. Why bother building the docs? Isn’t that only needed for packaging/deployment? It ends up making PRs ugly because you have all the unnecessary docs in the diff. -Jordan > On Nov 30, 2016, at 11:23 PM, Benjamin Reed wrote: > > when we commit

committing doc changes

when we commit pull requests with doc changes, i think we should commit the generated doc as a separate commit. what do you all think? i would like to do that to keep the change from the contributors pristine :) and i think it simplifies things a bit. ben

[jira] [Commented] (ZOOKEEPER-2627) Remove ZRWSERVERFOUND from C client and replace handle_error with something more semantically explicit for r/w server reconnect.

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

[GitHub] zookeeper issue #100: ZOOKEEPER-2627:Remove ZRWSERVERFOUND from C client.

Github user hanm commented on the issue: https://github.com/apache/zookeeper/pull/100 cool thanks @breed. @rgs1 Could you please merge & close this PR? --- 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

[GitHub] zookeeper issue #100: ZOOKEEPER-2627:Remove ZRWSERVERFOUND from C client.

Github user breed commented on the issue: https://github.com/apache/zookeeper/pull/100 +1 everything looks good from our side. we don't use that error code. --- 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

[jira] [Commented] (ZOOKEEPER-2627) Remove ZRWSERVERFOUND from C client and replace handle_error with something more semantically explicit for r/w server reconnect.

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

ZooKeeper-trunk-openjdk7 - Build # 1260 - Still Failing

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

[jira] [Comment Edited] (ZOOKEEPER-2230) Connections fo ZooKeeper server becomes slow over time with native GSSAPI

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15709434#comment-15709434 ] Yan Fitterer edited comment on ZOOKEEPER-2230 at 11/30/16 7:03 PM: ---

[jira] [Commented] (ZOOKEEPER-2230) Connections fo ZooKeeper server becomes slow over time with native GSSAPI

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15709434#comment-15709434 ] Yan Fitterer commented on ZOOKEEPER-2230: - [~deepeshreja]: sure. See below. I am working on a

Re: How to determine if the node is PERSISTENT & SEQUENTIAL

The path of ephemeral nodes has a pattern in their suffixes (10 digits with 0 (zero) padding), see https://zookeeper.apache.org/doc/trunk/zookeeperProgrammers.html#Ephemeral+Nodes So you could do a pattern matching and skip those nodes, unless your client applications deliberately create

ZooKeeper_branch35_solaris - Build # 335 - Still Failing

See https://builds.apache.org/job/ZooKeeper_branch35_solaris/335/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 461635 lines...] [junit] 2016-11-30

Re: How to determine if the node is PERSISTENT & SEQUENTIAL

Hi, I don't know how stable and up to date it is, but did you take a look at Guano? https://github.com/d2fn/guano Edward Em 30 de nov de 2016 9:10 AM, "Xie Gang" escreveu: > Hi, > > I need to copy some zk nodes to some other place. But I need to skip those > sequence

How to determine if the node is PERSISTENT & SEQUENTIAL

Hi, I need to copy some zk nodes to some other place. But I need to skip those sequence nodes. It seems that we could not get such information from the client API. Is there any way to do this? Thanks, -- Xie Gang

ZooKeeper_branch35_openjdk7 - Build # 315 - Still Failing

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

ZooKeeper-trunk-solaris - Build # 1405 - Still Failing

See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1405/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 462337 lines...] [junit] 2016-11-30