date:20170322

[jira] [Commented] (ZOOKEEPER-2706) checkstyle broken on branch-3.4

2017-03-22 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937736#comment-15937736
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2706:
---

Github user afine closed the pull request at:

https://github.com/apache/zookeeper/pull/181


> checkstyle broken on branch-3.4
> ---
>
> Key: ZOOKEEPER-2706
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2706
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Abraham Fine
>Assignee: Abraham Fine
> Fix For: 3.4.10
>
>
> While working on ZOOKEEPER-2696, [~rakeshr] and I noticed that checkstyle is 
> failing to execute on branch-3.4 with the following error:
> {code}
> BUILD FAILED
> /Users/abefine/cloudera_code/zookeeper/build.xml:1595: Unable to create a 
> Checker: cannot initialize module PackageHtml - Unable to instantiate 
> PackageHtml
> {code}
> This should essentially be a backport of ZOOKEEPER-412



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper pull request #181: ZOOKEEPER-2706: checkstyle broken on branch-3.4

2017-03-22 Thread afine

Github user afine closed the pull request at:

https://github.com/apache/zookeeper/pull/181


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Resolved] (ZOOKEEPER-2706) checkstyle broken on branch-3.4

2017-03-22 Thread Rakesh R (JIRA)


 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rakesh R resolved ZOOKEEPER-2706.
-
   Resolution: Fixed
Fix Version/s: 3.4.10

Issue resolved by pull request 181
[https://github.com/apache/zookeeper/pull/181]

> checkstyle broken on branch-3.4
> ---
>
> Key: ZOOKEEPER-2706
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2706
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Abraham Fine
>Assignee: Abraham Fine
> Fix For: 3.4.10
>
>
> While working on ZOOKEEPER-2696, [~rakeshr] and I noticed that checkstyle is 
> failing to execute on branch-3.4 with the following error:
> {code}
> BUILD FAILED
> /Users/abefine/cloudera_code/zookeeper/build.xml:1595: Unable to create a 
> Checker: cannot initialize module PackageHtml - Unable to instantiate 
> PackageHtml
> {code}
> This should essentially be a backport of ZOOKEEPER-412



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Failed: ZOOKEEPER- PreCommit Build #472

2017-03-22 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/472/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 2.04 KB...]
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:828)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to H0(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:822)
at 
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256)
at com.sun.proxy.$Proxy96.checkoutBranch(Unknown Source)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl.checkoutBranch(RemoteGitImpl.java:324)
at 
com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:78)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:995)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1102)
at hudson.scm.SCM.checkout(SCM.java:495)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1278)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1728)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Caused by: hudson.plugins.git.GitException: Command "git checkout -f 
origin/trunk" returned status code 1:
stdout: 
stderr: error: pathspec 'origin/trunk' did not match any file(s) known to git.

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1793)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$800(CliGitAPIImpl.java:64)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2060)
at 
org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:81)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:894)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:869)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:828)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Archiving artifacts
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
[description-setter] Could not determine description.
Putting comment on the pull request
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Commented] (ZOOKEEPER-2735) Typo fixes in some scripts

2017-03-22 Thread Hadoop QA (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937572#comment-15937572
 ] 

Hadoop QA commented on ZOOKEEPER-2735:
--

-1 overall.  GitHub Pull Request  Build
  

+1 @author.  The patch does not contain any @author tags.

+0 tests included.  The patch appears to be a documentation patch that 
doesn't require tests.

+1 javadoc.  The javadoc tool did not generate any warning messages.

+1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

+1 findbugs.  The patch does not introduce any new Findbugs (version 3.0.1) 
warnings.

+1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

-1 core tests.  The patch failed core unit tests.

+1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/471//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/471//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/471//console

This message is automatically generated.

> Typo fixes in some scripts
> --
>
> Key: ZOOKEEPER-2735
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2735
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: documentation
>Reporter: Woojin Joe
>Priority: Trivial
>
> There are same typos in shell files follows:
> * https://github.com/apache/zookeeper/blob/master/bin/zkCleanup.sh#L28
> * https://github.com/apache/zookeeper/blob/master/bin/zkCli.sh#L28
> * https://github.com/apache/zookeeper/blob/master/bin/zkServer.sh#L25
> TO-BE
> need to be changed from *POSTIX* to *POSIX*



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Failed: ZOOKEEPER- PreCommit Build #471

2017-03-22 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/471/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 69.43 MB...]
 [exec] +0 tests included.  The patch appears to be a documentation 
patch that doesn't require tests.
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 3.0.1) warnings.
 [exec] 
 [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
 [exec] 
 [exec] -1 core tests.  The patch failed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/471//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/471//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/471//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Comment added.
 [exec] f7e3d9de1efb5d9a9960e7b19998a56ba8b8e5ce logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1642:
 exec returned: 1

Total time: 19 minutes 31 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2735
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

Re: Apache ZooKeeper release 3.4.10 candidate 0

2017-03-22 Thread Rakesh Radhakrishnan

Thanks a lot Pat for the feedback. I will prepare another release
candidate, today(IST).


Thanks,
Rakesh

On Thu, Mar 23, 2017 at 12:33 AM, Patrick Hunt  wrote:

> FYI I just tested the latest branch 3.4 which includes the fix for 2712 and
> the tests all passed. Kudos!
>
> Patrick
>
> On Wed, Mar 8, 2017 at 9:11 PM, Rakesh Radhakrishnan 
> wrote:
>
> > Thank you Pat and Michael for voting and comments. We are *not* releasing
> > this candidate.
> >
> > Need to fix MiniKdc test failures.
> > https://issues.apache.org/jira/browse/ZOOKEEPER-2712
> >
> > I'll create another candidate once this is fixed.
> >
> >
> > Rakesh
> >
> > On Thu, Mar 9, 2017 at 12:08 AM, Michael Han  wrote:
> >
> > > I am -1 on this one as well.
> > >
> > > I think we have had bad build
> > >  for
> branch-3.4
> > > for
> > > a while.
> > > These tests consistently fail after build 1423:
> > >
> > >
> > >-
> > >org.apache.zookeeper.server.quorum.auth.QuorumKerberosHostB
> > > asedAuthTest.testValidCredentials
> > > > > /testReport/junit/org.apache.zookeeper.server.quorum.auth/Q
> > > uorumKerberosHostBasedAuthTest/testValidCredentials/>
> > >-
> > >org.apache.zookeeper.server.quorum.auth.QuorumKerberosHostB
> > > asedAuthTest.testConnectBadServer
> > > > > /testReport/junit/org.apache.zookeeper.server.quorum.auth/Q
> > > uorumKerberosHostBasedAuthTest/testConnectBadServer/>
> > >-
> > >org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthT
> > > est.testValidCredentials
> > > > > /testReport/junit/org.apache.zookeeper.server.quorum.auth/Q
> > > uorumKerberosAuthTest/testValidCredentials/>
> > >
> > >
> > > A brief look up indicates commit b26eaf3492a43821f648d8a8f87d8a
> > c3488f1cef
> > >  > > f648d8a8f87d8ac3488f1cef>
> > > might be the culprit.
> > > I think these tests need to be green before we can cut another RC
> build.
> > >
> > >
> > > On Wed, Mar 8, 2017 at 8:59 AM, Patrick Hunt  wrote:
> > >
> > > > -1 - I'm seeing this test fail consistently on my Mac (the other
> tests
> > > all
> > > > seem to be passing on the java side)
> > > >
> > > > Lots of the "server not up" messages followed by:
> > > >
> > > > 2017-03-08 08:54:58,507 [myid:] - INFO  [Thread-1:FourLetterWordMain@
> > 62]
> > > -
> > > > connecting to 127.0.0.1 11224
> > > > 2017-03-08 08:54:58,508 [myid:] - INFO  [Thread-1:ClientBase@245] -
> > > server
> > > > 127.0.0.1:11224 not up java.net.ConnectException: Connection refused
> > > > (Connection refused)
> > > > 2017-03-08 08:54:58,508 [myid:] - INFO
> > > >  [Thread-1:JUnit4ZKTestRunner$LoggedInvokeMethod@74] - TEST METHOD
> > > FAILED
> > > > testValidCredentials
> > > > java.lang.AssertionError: waiting for server 1 being up
> > > >
> > > >
> > > > On Wed, Mar 8, 2017 at 3:09 AM, Rakesh Radhakrishnan <
> > rake...@apache.org
> > > >
> > > > wrote:
> > > >
> > > > > This is a bug fix release candidate for 3.4.10. It fixes 39 issues,
> > > > > including
> > > > > security feature QuorumPeer mutual authentication via SASL and
> other
> > > > > potential bugs.
> > > > >
> > > > > The full release notes are available at:
> > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > > projectId=12310801=12338036
> > > > >
> > > > > *** Please download, test and vote by March 14th 2017, 23:59 UTC+0.
> > ***
> > > > >
> > > > > Source files:
> > > > > http://people.apache.org/~rakeshr/zookeeper-3.4.10-candidate-0/
> > > > >
> > > > > Maven staging repo:
> > > > > https://repository.apache.org/content/groups/staging/org/
> > > > > apache/zookeeper/zookeeper/3.4.10/
> > > > >
> > > > > The release candidate tag in git to be voted upon:
> release-3.4.10-rc0
> > > > > https://github.com/apache/zookeeper/tree/release-3.4.10-rc0
> > > > >
> > > > > ZooKeeper's KEYS file containing PGP keys we use to sign the
> release:
> > > > > http://www.apache.org/dist/zookeeper/KEYS
> > > > >
> > > > > Should we release this candidate?
> > > > >
> > > > >
> > > > > Rakesh
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Cheers
> > > Michael.
> > >
> >
>

[jira] [Commented] (ZOOKEEPER-2706) checkstyle broken on branch-3.4

2017-03-22 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937561#comment-15937561
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2706:
---

Github user rakeshadr commented on the issue:

https://github.com/apache/zookeeper/pull/181
  
Thank you @afine for the quick reply. +1 lgtm. I will merge this shortly.


> checkstyle broken on branch-3.4
> ---
>
> Key: ZOOKEEPER-2706
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2706
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> While working on ZOOKEEPER-2696, [~rakeshr] and I noticed that checkstyle is 
> failing to execute on branch-3.4 with the following error:
> {code}
> BUILD FAILED
> /Users/abefine/cloudera_code/zookeeper/build.xml:1595: Unable to create a 
> Checker: cannot initialize module PackageHtml - Unable to instantiate 
> PackageHtml
> {code}
> This should essentially be a backport of ZOOKEEPER-412



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #181: ZOOKEEPER-2706: checkstyle broken on branch-3.4

2017-03-22 Thread rakeshadr

Github user rakeshadr commented on the issue:

https://github.com/apache/zookeeper/pull/181
  
Thank you @afine for the quick reply. +1 lgtm. I will merge this shortly.


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2735) Typo fixes in some scripts

2017-03-22 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937549#comment-15937549
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2735:
---

GitHub user not-for-me opened a pull request:

https://github.com/apache/zookeeper/pull/204

ZOOKEEPER-2735: fix typos in shell scripts

This PR contains corrections for some spelling typos in shell scripts.

I also create issue in 
JIRA[ZOOKEEPER-2735)](https://issues.apache.org/jira/browse/ZOOKEEPER-2735)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/not-for-me/zookeeper master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zookeeper/pull/204.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #204


commit 781424c342273d4e3b3ee4db82a2f937e6a89db4
Author: woojin.joe 
Date:   2017-03-23T01:30:51Z

ZOOKEEPER-2735: fix typos in shell scripts




> Typo fixes in some scripts
> --
>
> Key: ZOOKEEPER-2735
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2735
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: documentation
>Reporter: Woojin Joe
>Priority: Trivial
>
> There are same typos in shell files follows:
> * https://github.com/apache/zookeeper/blob/master/bin/zkCleanup.sh#L28
> * https://github.com/apache/zookeeper/blob/master/bin/zkCli.sh#L28
> * https://github.com/apache/zookeeper/blob/master/bin/zkServer.sh#L25
> TO-BE
> need to be changed from *POSTIX* to *POSIX*



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ZOOKEEPER-2735) Typo fixes in some scripts

2017-03-22 Thread Woojin Joe (JIRA)


 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Woojin Joe updated ZOOKEEPER-2735:
--
Description: 
There are same typos in shell files follows:
* https://github.com/apache/zookeeper/blob/master/bin/zkCleanup.sh#L28
* https://github.com/apache/zookeeper/blob/master/bin/zkCli.sh#L28
* https://github.com/apache/zookeeper/blob/master/bin/zkServer.sh#L25

TO-BE
need to be changed from *POSTIX* to *POSIX*

  was:
There are same typos in shell files follows:
* https://github.com/apache/zookeeper/blob/master/bin/zkCleanup.sh#L28
* https://github.com/apache/zookeeper/blob/master/bin/zkCli.sh#L28
* https://github.com/apache/zookeeper/blob/master/bin/zkServer.sh#L25

TO-BE
need to be changed from **POSTIX** to *POSIX


> Typo fixes in some scripts
> --
>
> Key: ZOOKEEPER-2735
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2735
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: documentation
>Reporter: Woojin Joe
>Priority: Trivial
>
> There are same typos in shell files follows:
> * https://github.com/apache/zookeeper/blob/master/bin/zkCleanup.sh#L28
> * https://github.com/apache/zookeeper/blob/master/bin/zkCli.sh#L28
> * https://github.com/apache/zookeeper/blob/master/bin/zkServer.sh#L25
> TO-BE
> need to be changed from *POSTIX* to *POSIX*



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ZOOKEEPER-2735) Typo fixes in some scripts

2017-03-22 Thread Woojin Joe (JIRA)

Woojin Joe created ZOOKEEPER-2735:
-

 Summary: Typo fixes in some scripts
 Key: ZOOKEEPER-2735
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2735
 Project: ZooKeeper
  Issue Type: Bug
  Components: documentation
Reporter: Woojin Joe
Priority: Trivial


There are same typos in shell files follows:
* https://github.com/apache/zookeeper/blob/master/bin/zkCleanup.sh#L28
* https://github.com/apache/zookeeper/blob/master/bin/zkCli.sh#L28
* https://github.com/apache/zookeeper/blob/master/bin/zkServer.sh#L25

TO-BE
need to be changed from **POSTIX** to *POSIX



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

ZooKeeper_branch34 - Build # 1887 - Failure

2017-03-22 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper_branch34/1887/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 31.55 MB...]
[junit] 2017-03-23 00:20:04,012 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-03-23 00:20:04,012 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-03-23 00:20:04,013 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-03-23 00:20:04,013 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-03-23 00:20:04,014 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-03-23 00:20:04,014 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-23 00:20:04,015 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-03-23 00:20:04,017 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-03-23 00:20:04,017 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-03-23 00:20:04,018 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-03-23 00:20:04,018 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-03-23 00:20:04,018 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/test/tmp/test6680795016649859133.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/test/tmp/test6680795016649859133.junit.dir/version-2
[junit] 2017-03-23 00:20:04,022 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-23 00:20:04,023 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-23 00:20:04,023 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:46992
[junit] 2017-03-23 00:20:04,024 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@883] - Processing 
stat command from /127.0.0.1:46992
[junit] 2017-03-23 00:20:04,024 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-03-23 00:20:04,024 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1044] - Closed socket connection for client 
/127.0.0.1:46992 (no session established for client)
[junit] 2017-03-23 00:20:04,025 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-03-23 00:20:04,027 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-03-23 00:20:04,027 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-03-23 00:20:04,027 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-03-23 00:20:04,027 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-03-23 00:20:04,027 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35681
[junit] 2017-03-23 00:20:04,028 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-03-23 00:20:04,028 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-03-23 00:20:04,028 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-03-23 00:20:04,096 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15af888de79 closed
[junit] 2017-03-23 00:20:04,096 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-03-23 00:20:04,097 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15af888de79
[junit] 2017-03-23 00:20:04,097 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-03-23 00:20:04,097 [myid:] - INFO  [main:ZooKeeperServer@505] 
- shutting down
[junit] 2017-03-23 00:20:04,097 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-23 00:20:04,097 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-03-23 00:20:04,098 [myid:] - INFO

[jira] [Commented] (ZOOKEEPER-2706) checkstyle broken on branch-3.4

2017-03-22 Thread Hadoop QA (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937303#comment-15937303
 ] 

Hadoop QA commented on ZOOKEEPER-2706:
--

-1 overall.  GitHub Pull Request  Build
  

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 3 new or modified tests.

-1 javadoc.  The javadoc tool appears to have generated 1 warning messages.

+1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

-1 findbugs.  The patch appears to introduce 97 new Findbugs (version 
3.0.1) warnings.

+1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

-1 core tests.  The patch failed core unit tests.

+1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/470//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/470//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/470//console

This message is automatically generated.

> checkstyle broken on branch-3.4
> ---
>
> Key: ZOOKEEPER-2706
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2706
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> While working on ZOOKEEPER-2696, [~rakeshr] and I noticed that checkstyle is 
> failing to execute on branch-3.4 with the following error:
> {code}
> BUILD FAILED
> /Users/abefine/cloudera_code/zookeeper/build.xml:1595: Unable to create a 
> Checker: cannot initialize module PackageHtml - Unable to instantiate 
> PackageHtml
> {code}
> This should essentially be a backport of ZOOKEEPER-412



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2706) checkstyle broken on branch-3.4

2017-03-22 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937256#comment-15937256
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2706:
---

Github user afine commented on the issue:

https://github.com/apache/zookeeper/pull/181
  
This should be working on java 6 and 7 now.


> checkstyle broken on branch-3.4
> ---
>
> Key: ZOOKEEPER-2706
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2706
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> While working on ZOOKEEPER-2696, [~rakeshr] and I noticed that checkstyle is 
> failing to execute on branch-3.4 with the following error:
> {code}
> BUILD FAILED
> /Users/abefine/cloudera_code/zookeeper/build.xml:1595: Unable to create a 
> Checker: cannot initialize module PackageHtml - Unable to instantiate 
> PackageHtml
> {code}
> This should essentially be a backport of ZOOKEEPER-412



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #181: ZOOKEEPER-2706: checkstyle broken on branch-3.4

2017-03-22 Thread afine

Github user afine commented on the issue:

https://github.com/apache/zookeeper/pull/181
  
This should be working on java 6 and 7 now.


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

ZooKeeper-trunk-openjdk7 - Build # 1411 - Failure

2017-03-22 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1411/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 64.47 MB...]
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2017-03-22 20:03:00,527 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port27626,name1=Connections,name2=127.0.0.1,name3=0x10322947ff8]
[junit] 2017-03-22 20:03:00,537 [myid:127.0.0.1:27503] - INFO  
[main-SendThread(127.0.0.1:27503):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:27503. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-22 20:03:00,538 [myid:127.0.0.1:27503] - WARN  
[main-SendThread(127.0.0.1:27503):ClientCnxn$SendThread@1235] - Session 
0x1032291080e for server 127.0.0.1/127.0.0.1:27503, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-03-22 20:03:00,626 [myid:] - INFO  [main:ZooKeeper@1324] - 
Session: 0x10322947ff8 closed
[junit] 2017-03-22 20:03:00,626 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x10322947ff8
[junit] 2017-03-22 20:03:00,626 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 214248
[junit] 2017-03-22 20:03:00,627 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 2426
[junit] 2017-03-22 20:03:00,627 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-03-22 20:03:00,627 [myid:] - INFO  [main:ClientBase@558] - 
tearDown starting
[junit] 2017-03-22 20:03:00,627 [myid:] - INFO  [main:ClientBase@528] - 
STOPPING server
[junit] 2017-03-22 20:03:00,627 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:27626
[junit] 2017-03-22 20:03:00,633 [myid:] - INFO  [main:ZooKeeperServer@542] 
- shutting down
[junit] 2017-03-22 20:03:00,633 [myid:] - ERROR [main:ZooKeeperServer@506] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-22 20:03:00,633 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-03-22 20:03:00,633 [myid:] - INFO  
[main:PrepRequestProcessor@1008] - Shutting down
[junit] 2017-03-22 20:03:00,634 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-03-22 20:03:00,634 [myid:] - INFO  [ProcessThread(sid:0 
cport:27626)::PrepRequestProcessor@157] - PrepRequestProcessor exited loop!
[junit] 2017-03-22 20:03:00,634 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-03-22 20:03:00,634 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2017-03-22 20:03:00,634 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port27626,name1=InMemoryDataTree]
[junit] 2017-03-22 20:03:00,634 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port27626]
[junit] 2017-03-22 20:03:00,634 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 27626
[junit] 2017-03-22 20:03:00,635 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2017-03-22 20:03:00,641 [myid:] - INFO  [main:ClientBase@583] - 
fdcount after test is: 7131 at start it was 7135
[junit] 2017-03-22 20:03:00,641 [myid:] - INFO  [main:ZKTestCase$1@68] - 
SUCCEEDED testWatcherAutoResetWithLocal
[junit] 2017-03-22 20:03:00,641 [myid:] - INFO  [main:ZKTestCase$1@63] - 
FINISHED testWatcherAutoResetWithLocal
[junit] Tests run: 103, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
497.022 sec, Thread: 7, Class: org.apache.zookeeper.test.NioNettySuiteTest
[junit] 2017-03-22 20:03:00,938

Re: Disabling snapshots in ZooKeeper

2017-03-22 Thread Patrick Hunt

I don't believe it's a matter of disabling the feature, it never existed.
IIRC, synchronizing followers may include sending them the snapshot, which
is streamed from the disk in the "on disk" form.

Patrick

On Thu, Mar 9, 2017 at 9:28 PM, Rakesh Radhakrishnan 
wrote:

> Hi Aishwarya,
>
> >Is there a way to disable snapshots
> Its interesting, just curious to know the thought process behind disabling
> snapshot feature. Thanks!
>
>
> Rakesh
>
>
>
> On Fri, Mar 10, 2017 at 10:52 AM, Michael Han  wrote:
>
> > >> Is there a way to disable snapshots when the Zookeeper process
> restarts?
> > Snapshot is a mandatory feature so there is no configuration option to
> > disable it afaik.
> >
> > >>  is it safe to just comment zk.takeSnapshot()
> > This should work in theory, if there is no snapshot ZK will rely on
> > transaction log file for recovery. But I never tried it though.
> >
> > On Thu, Mar 9, 2017 at 5:05 PM, Aishwarya Ganesan 
> > wrote:
> >
> > > Hi all,
> > >
> > > Is there a way to disable snapshots when the Zookeeper process
> restarts?
> > > Setting snapCount to a large value doesn't help as Zookeeper takes
> > > a snapshot on startup.
> > >
> > > In order to achieve this, is it safe to just comment zk.takeSnapshot()
> in
> > > the code?
> > >
> > > Thanks,
> > > Aishwarya
> > >
> >
> >
> >
> > --
> > Cheers
> > Michael.
> >
>

[jira] [Assigned] (ZOOKEEPER-2726) Patch for ZOOKEEPER-2693 introduces potential race condition

2017-03-22 Thread Patrick Hunt (JIRA)


 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt reassigned ZOOKEEPER-2726:
---

Assignee: Kyle Nusbaum

> Patch for ZOOKEEPER-2693 introduces potential race condition
> 
>
> Key: ZOOKEEPER-2726
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2726
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Kyle Nusbaum
>Assignee: Kyle Nusbaum
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
>
> We noticed when porting the patch, that isEnabled is not thread-safe. 
> Synchronizing it and resetWhitelist should solve the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: 3.5.3: alpha or beta?

2017-03-22 Thread Patrick Hunt

I don't remember ever agreeing that 3.5 is in beta. If people feel
comfortable with that transition I think we should formalize it. See my
comment here:
https://issues.apache.org/jira/browse/ZOOKEEPER-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936850#comment-15936850

Patrick

On Fri, Mar 17, 2017 at 8:45 AM, Liang Han  wrote:

> Hi all,
>
> I noticed that in JIRA the 3.5.3 is still tagged as Alpha [1]. Also this is
> mentioned in last board meeting [2] that 3.5.3 will be last Alpha release,
> as opposed to a new beta release.
>
> I thought sometime back we agreed that 3.5.3 would be a beta release,
> because we intended to lock the APIs for this release? 3.5.3-beta was
> originally mentioned a couple years ago when 3.5 series releases was
> planned [3] where the semantic of alpha and beta was also clarified, but I
> can't find any traces on why 3.5.3 was named Alpha on JIRA.
>
> Should we make 3.5.3 another alpha release, or a beta release?
>
> [1]
> https://issues.apache.org/jira/browse/ZOOKEEPER/?selectedTab
> =com.atlassian.jira.jira-projects-plugin:versions-panel
> [2] https://whimsy.apache.org/board/minutes/ZooKeeper.html
> [3]
> http://markmail.org/message/vnb5pvszgm4cty67#query:+page:1+
> mid:ymxliy2rrwjc2pmo+state:results
>
> --
> Cheers
> Michael.
>

Re: Apache ZooKeeper release 3.4.10 candidate 0

2017-03-22 Thread Patrick Hunt

FYI I just tested the latest branch 3.4 which includes the fix for 2712 and
the tests all passed. Kudos!

Patrick

On Wed, Mar 8, 2017 at 9:11 PM, Rakesh Radhakrishnan 
wrote:

> Thank you Pat and Michael for voting and comments. We are *not* releasing
> this candidate.
>
> Need to fix MiniKdc test failures.
> https://issues.apache.org/jira/browse/ZOOKEEPER-2712
>
> I'll create another candidate once this is fixed.
>
>
> Rakesh
>
> On Thu, Mar 9, 2017 at 12:08 AM, Michael Han  wrote:
>
> > I am -1 on this one as well.
> >
> > I think we have had bad build
> >  for branch-3.4
> > for
> > a while.
> > These tests consistently fail after build 1423:
> >
> >
> >-
> >org.apache.zookeeper.server.quorum.auth.QuorumKerberosHostB
> > asedAuthTest.testValidCredentials
> > > /testReport/junit/org.apache.zookeeper.server.quorum.auth/Q
> > uorumKerberosHostBasedAuthTest/testValidCredentials/>
> >-
> >org.apache.zookeeper.server.quorum.auth.QuorumKerberosHostB
> > asedAuthTest.testConnectBadServer
> > > /testReport/junit/org.apache.zookeeper.server.quorum.auth/Q
> > uorumKerberosHostBasedAuthTest/testConnectBadServer/>
> >-
> >org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthT
> > est.testValidCredentials
> > > /testReport/junit/org.apache.zookeeper.server.quorum.auth/Q
> > uorumKerberosAuthTest/testValidCredentials/>
> >
> >
> > A brief look up indicates commit b26eaf3492a43821f648d8a8f87d8a
> c3488f1cef
> >  > f648d8a8f87d8ac3488f1cef>
> > might be the culprit.
> > I think these tests need to be green before we can cut another RC build.
> >
> >
> > On Wed, Mar 8, 2017 at 8:59 AM, Patrick Hunt  wrote:
> >
> > > -1 - I'm seeing this test fail consistently on my Mac (the other tests
> > all
> > > seem to be passing on the java side)
> > >
> > > Lots of the "server not up" messages followed by:
> > >
> > > 2017-03-08 08:54:58,507 [myid:] - INFO  [Thread-1:FourLetterWordMain@
> 62]
> > -
> > > connecting to 127.0.0.1 11224
> > > 2017-03-08 08:54:58,508 [myid:] - INFO  [Thread-1:ClientBase@245] -
> > server
> > > 127.0.0.1:11224 not up java.net.ConnectException: Connection refused
> > > (Connection refused)
> > > 2017-03-08 08:54:58,508 [myid:] - INFO
> > >  [Thread-1:JUnit4ZKTestRunner$LoggedInvokeMethod@74] - TEST METHOD
> > FAILED
> > > testValidCredentials
> > > java.lang.AssertionError: waiting for server 1 being up
> > >
> > >
> > > On Wed, Mar 8, 2017 at 3:09 AM, Rakesh Radhakrishnan <
> rake...@apache.org
> > >
> > > wrote:
> > >
> > > > This is a bug fix release candidate for 3.4.10. It fixes 39 issues,
> > > > including
> > > > security feature QuorumPeer mutual authentication via SASL and other
> > > > potential bugs.
> > > >
> > > > The full release notes are available at:
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > projectId=12310801=12338036
> > > >
> > > > *** Please download, test and vote by March 14th 2017, 23:59 UTC+0.
> ***
> > > >
> > > > Source files:
> > > > http://people.apache.org/~rakeshr/zookeeper-3.4.10-candidate-0/
> > > >
> > > > Maven staging repo:
> > > > https://repository.apache.org/content/groups/staging/org/
> > > > apache/zookeeper/zookeeper/3.4.10/
> > > >
> > > > The release candidate tag in git to be voted upon: release-3.4.10-rc0
> > > > https://github.com/apache/zookeeper/tree/release-3.4.10-rc0
> > > >
> > > > ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> > > > http://www.apache.org/dist/zookeeper/KEYS
> > > >
> > > > Should we release this candidate?
> > > >
> > > >
> > > > Rakesh
> > > >
> > >
> >
> >
> >
> > --
> > Cheers
> > Michael.
> >
>

Re: Snapshot build please?

2017-03-22 Thread Patrick Hunt

I honestly don't remember. My recommendation would be to look at what other
projects are doing in this regard (iirc some publish nightly? that might be
a good idea...) and try to copy their policies/process. Check the wiki and
see if we ever documented anything around this, whether we have or not I'd
recommend capturing it on the wiki so that we can do it going forward.

Patrick

On Tue, Mar 21, 2017 at 11:21 AM, Jordan Zimmerman <
jor...@jordanzimmerman.com> wrote:

> I'm not an ant expert but build.xml has the right endpoints for the Apache
> staging repo. It looks like "ant mvn-deploy" will do the right thing. But,
> hopefully, someone else can confirm.
>
> -Jordan
>
> > On Mar 21, 2017, at 12:33 PM, Michael Han  wrote:
> >
> > Looks like the last snap shot posted on apache repo is back in 2013:
> > https://repository.apache.org/content/repositories/snapshots/org/apache/
> zookeeper/zookeeper/3.5.0-SNAPSHOT/  org/content/repositories/snapshots/org/apache/zookeeper/zookeeper/3.5.0-
> SNAPSHOT/>
> >
> > I don't find anything related to maven central still here
> > https://oss.sonatype.org/content/repositories/snapshots/ <
> https://oss.sonatype.org/content/repositories/snapshots/>.
> >
> > I am happy to help post a snapshot if someone can point me to the
> ZooKeeper
> > documentation regarding how to do this. Current maven publish process is
> > strictly related to the releases.
> >
> >
> > On Mon, Mar 20, 2017 at 6:35 PM, Jordan Zimmerman <
> > jor...@jordanzimmerman.com > wrote:
> >
> >> I recall it was done in the past. Maven Central Snapshots is available
> >> here: https://oss.sonatype.org/content/repositories/snapshots/ <
> https://oss.sonatype.org/content/repositories/snapshots/> <
> >> https://oss.sonatype.org/content/repositories/snapshots/ <
> https://oss.sonatype.org/content/repositories/snapshots/>> - though, I
> >> could be misremembering. Apache has a snapshots directory:
> >> https://repository.apache.org/content/repositories/snapshots <
> https://repository.apache.org/content/repositories/snapshots> <
> >> https://repository.apache.org/content/repositories/snapshots> - Anyway,
> >> if you use the Apache parent pom it gets deployed to the right place.
> But,
> >> I don't know about ZooKeeper's ant file.
> >>
> >> -Jordan
> >>
> >>> On Mar 20, 2017, at 7:46 PM, Liang Han  wrote:
> >>>
> >>> I can't find any of existing snapshot jars on Maven Central. Do we ever
> >>> publish snapshot jars on maven central?
> >>>
> >>> On Mon, Mar 20, 2017 at 9:02 AM, Jordan Zimmerman <
> >>> jor...@jordanzimmerman.com> wrote:
> >>>
>  If you don't mind, can a committer please make a snapshot build of 3.5
>  (branch-3.5) and deploy it to Maven Central? I'd like to work on the
>  Curator portion of TTL Nodes.
> 
>  Thank you!
> 
>  -Jordan
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Cheers
> >>> Michael.
> >>
> >>
> >
> >
> > --
> > Cheers
> > Michael.
>
>

[jira] [Commented] (ZOOKEEPER-2734) 3.5.3 should be a beta release instead of alpha release.

2017-03-22 Thread Patrick Hunt (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936850#comment-15936850
 ] 

Patrick Hunt commented on ZOOKEEPER-2734:
-

Release related decisions are typically controlled by the PMC in coordination 
with the greater community - my recommendation would be to start a VOTE thread 
on the dev (public) list. The question being voted upon would be whether to 
move 3.5 from alpha to beta.

> 3.5.3 should be a beta release instead of alpha release.
> 
>
> Key: ZOOKEEPER-2734
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2734
> Project: ZooKeeper
>  Issue Type: Task
>  Components: build
>Affects Versions: 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>Priority: Blocker
>  Labels: build, release
> Fix For: 3.5.3
>
>
> Currently 3.5.3 is tagged as alpha both in build and JIRA. We should reach a 
> consensus on the tag before release. See the email thread on dev list for 
> more details.
> Deliverable:
> * A consensus on using beta as the version for 3.5.3 release.
> * Update build.xml.
> * Update JIRA (3.5.3-alpha -> 3.5.3-beta).
> Thread on dev list:
> http://mail-archives.apache.org/mod_mbox/zookeeper-dev/201703.mbox/%3CCA%2Bi0x1JZacVMQGd_Jb34jSaw7p_nhWpcx9uzHwCwPPF%2BPPrf3g%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2608) Create CLI option for TTL ephemerals

2017-03-22 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936776#comment-15936776
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2608:
---

Github user Randgalt commented on the issue:

https://github.com/apache/zookeeper/pull/193
  
Also, considering that it's now in `branch-3.5` it would be odd not to 
merge.


> Create CLI option for TTL ephemerals
> 
>
> Key: ZOOKEEPER-2608
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2608
> Project: ZooKeeper
>  Issue Type: Sub-task
>  Components: c client, java client, jute, server
>Reporter: Camille Fournier
>Assignee: Jordan Zimmerman
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2608-2.patch, ZOOKEEPER-2608-3.patch, 
> ZOOKEEPER-2608.patch
>
>
> Need to update CreateCommand to have the TTL node option



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #136: [ZOOKEEPER-1416] Persistent Recursive Watch

2017-03-22 Thread Randgalt

Github user Randgalt commented on the issue:

https://github.com/apache/zookeeper/pull/136
  
Thanks @eribeiro - at minimum it would be good to get feedback. This 
feature will really help the community.


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-1416) Persistent Recursive Watch

2017-03-22 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936774#comment-15936774
 ] 

ASF GitHub Bot commented on ZOOKEEPER-1416:
---

Github user Randgalt commented on the issue:

https://github.com/apache/zookeeper/pull/136
  
Thanks @eribeiro - at minimum it would be good to get feedback. This 
feature will really help the community.


> Persistent Recursive Watch
> --
>
> Key: ZOOKEEPER-1416
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1416
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: c client, documentation, java client, server
>Reporter: Phillip Liu
>Assignee: Jordan Zimmerman
> Attachments: ZOOKEEPER-1416.patch, ZOOKEEPER-1416.patch
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> h4. The Problem
> A ZooKeeper Watch can be placed on a single znode and when the znode changes 
> a Watch event is sent to the client. If there are thousands of znodes being 
> watched, when a client (re)connect, it would have to send thousands of watch 
> requests. At Facebook, we have this problem storing information for thousands 
> of db shards. Consequently a naming service that consumes the db shard 
> definition issues thousands of watch requests each time the service starts 
> and changes client watcher.
> h4. Proposed Solution
> We add the notion of a Persistent Recursive Watch in ZooKeeper. Persistent 
> means no Watch reset is necessary after a watch-fire. Recursive means the 
> Watch applies to the node and descendant nodes. A Persistent Recursive Watch 
> behaves as follows:
> # Recursive Watch supports all Watch semantics: CHILDREN, DATA, and EXISTS.
> # CHILDREN and DATA Recursive Watches can be placed on any znode.
> # EXISTS Recursive Watches can be placed on any path.
> # A Recursive Watch behaves like a auto-watch registrar on the server side. 
> Setting a  Recursive Watch means to set watches on all descendant znodes.
> # When a watch on a descendant fires, no subsequent event is fired until a 
> corresponding getData(..) on the znode is called, then Recursive Watch 
> automically apply the watch on the znode. This maintains the existing Watch 
> semantic on an individual znode.
> # A Recursive Watch overrides any watches placed on a descendant znode. 
> Practically this means the Recursive Watch Watcher callback is the one 
> receiving the event and event is delivered exactly once.
> A goal here is to reduce the number of semantic changes. The guarantee of no 
> intermediate watch event until data is read will be maintained. The only 
> difference is we will automatically re-add the watch after read. At the same 
> time we add the convience of reducing the need to add multiple watches for 
> sibling znodes and in turn reduce the number of watch messages sent from the 
> client to the server.
> There are some implementation details that needs to be hashed out. Initial 
> thinking is to have the Recursive Watch create per-node watches. This will 
> cause a lot of watches to be created on the server side. Currently, each 
> watch is stored as a single bit in a bit set relative to a session - up to 3 
> bits per client per znode. If there are 100m znodes with 100k clients, each 
> watching all nodes, then this strategy will consume approximately 3.75TB of 
> ram distributed across all Observers. Seems expensive.
> Alternatively, a blacklist of paths to not send Watches regardless of Watch 
> setting can be set each time a watch event from a Recursive Watch is fired. 
> The memory utilization is relative to the number of outstanding reads and at 
> worst case it's 1/3 * 3.75TB using the parameters given above.
> Otherwise, a relaxation of no intermediate watch event until read guarantee 
> is required. If the server can send watch events regardless of one has 
> already been fired without corresponding read, then the server can simply 
> fire watch events without tracking.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2734) 3.5.3 should be a beta release instead of alpha release.

2017-03-22 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936762#comment-15936762
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2734:
---

Github user rakeshadr commented on the issue:

https://github.com/apache/zookeeper/pull/201
  
+1 LGTM


> 3.5.3 should be a beta release instead of alpha release.
> 
>
> Key: ZOOKEEPER-2734
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2734
> Project: ZooKeeper
>  Issue Type: Task
>  Components: build
>Affects Versions: 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>Priority: Blocker
>  Labels: build, release
> Fix For: 3.5.3
>
>
> Currently 3.5.3 is tagged as alpha both in build and JIRA. We should reach a 
> consensus on the tag before release. See the email thread on dev list for 
> more details.
> Deliverable:
> * A consensus on using beta as the version for 3.5.3 release.
> * Update build.xml.
> * Update JIRA (3.5.3-alpha -> 3.5.3-beta).
> Thread on dev list:
> http://mail-archives.apache.org/mod_mbox/zookeeper-dev/201703.mbox/%3CCA%2Bi0x1JZacVMQGd_Jb34jSaw7p_nhWpcx9uzHwCwPPF%2BPPrf3g%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Failed: ZOOKEEPER-1416 PreCommit Build #3620

2017-03-22 Thread Apache Jenkins Server

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1416
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3620/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 793 B...]
 > git --version # timeout=10
 > git fetch --tags --progress git://git.apache.org/zookeeper.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 9a6aff269e5c1ac25e1aca1877b06f725799bfee 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 9a6aff269e5c1ac25e1aca1877b06f725799bfee
 > git rev-list 6949af062d5ad3cdb36c86afc3728ede78c8039d # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-Build] $ /bin/bash /tmp/hudson2710265524176402762.sh
/home/jenkins/tools/java/latest1.7/bin/java
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 386178
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
[description-setter] Could not determine description.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
No tests ran.

[GitHub] zookeeper issue #201: ZOOKEEPER-2734: 3.5.3 should be a beta release instead...

2017-03-22 Thread rakeshadr

Github user rakeshadr commented on the issue:

https://github.com/apache/zookeeper/pull/201
  
+1 LGTM


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-1416) Persistent Recursive Watch

2017-03-22 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936752#comment-15936752
 ] 

ASF GitHub Bot commented on ZOOKEEPER-1416:
---

Github user eribeiro commented on the issue:

https://github.com/apache/zookeeper/pull/136
  
Hey @fpj, @phunt, @breed, @skamille (or any PMC/commiter), it would be 
really cool to have this patch by @Randgalt merged, wouldn't it? If you have 
any cycles would you mind to review this one? 

Thanks!!!


> Persistent Recursive Watch
> --
>
> Key: ZOOKEEPER-1416
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1416
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: c client, documentation, java client, server
>Reporter: Phillip Liu
>Assignee: Jordan Zimmerman
> Attachments: ZOOKEEPER-1416.patch, ZOOKEEPER-1416.patch
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> h4. The Problem
> A ZooKeeper Watch can be placed on a single znode and when the znode changes 
> a Watch event is sent to the client. If there are thousands of znodes being 
> watched, when a client (re)connect, it would have to send thousands of watch 
> requests. At Facebook, we have this problem storing information for thousands 
> of db shards. Consequently a naming service that consumes the db shard 
> definition issues thousands of watch requests each time the service starts 
> and changes client watcher.
> h4. Proposed Solution
> We add the notion of a Persistent Recursive Watch in ZooKeeper. Persistent 
> means no Watch reset is necessary after a watch-fire. Recursive means the 
> Watch applies to the node and descendant nodes. A Persistent Recursive Watch 
> behaves as follows:
> # Recursive Watch supports all Watch semantics: CHILDREN, DATA, and EXISTS.
> # CHILDREN and DATA Recursive Watches can be placed on any znode.
> # EXISTS Recursive Watches can be placed on any path.
> # A Recursive Watch behaves like a auto-watch registrar on the server side. 
> Setting a  Recursive Watch means to set watches on all descendant znodes.
> # When a watch on a descendant fires, no subsequent event is fired until a 
> corresponding getData(..) on the znode is called, then Recursive Watch 
> automically apply the watch on the znode. This maintains the existing Watch 
> semantic on an individual znode.
> # A Recursive Watch overrides any watches placed on a descendant znode. 
> Practically this means the Recursive Watch Watcher callback is the one 
> receiving the event and event is delivered exactly once.
> A goal here is to reduce the number of semantic changes. The guarantee of no 
> intermediate watch event until data is read will be maintained. The only 
> difference is we will automatically re-add the watch after read. At the same 
> time we add the convience of reducing the need to add multiple watches for 
> sibling znodes and in turn reduce the number of watch messages sent from the 
> client to the server.
> There are some implementation details that needs to be hashed out. Initial 
> thinking is to have the Recursive Watch create per-node watches. This will 
> cause a lot of watches to be created on the server side. Currently, each 
> watch is stored as a single bit in a bit set relative to a session - up to 3 
> bits per client per znode. If there are 100m znodes with 100k clients, each 
> watching all nodes, then this strategy will consume approximately 3.75TB of 
> ram distributed across all Observers. Seems expensive.
> Alternatively, a blacklist of paths to not send Watches regardless of Watch 
> setting can be set each time a watch event from a Recursive Watch is fired. 
> The memory utilization is relative to the number of outstanding reads and at 
> worst case it's 1/3 * 3.75TB using the parameters given above.
> Otherwise, a relaxation of no intermediate watch event until read guarantee 
> is required. If the server can send watch events regardless of one has 
> already been fired without corresponding read, then the server can simply 
> fire watch events without tracking.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #136: [ZOOKEEPER-1416] Persistent Recursive Watch

2017-03-22 Thread eribeiro

Github user eribeiro commented on the issue:

https://github.com/apache/zookeeper/pull/136
  
Hey @fpj, @phunt, @breed, @skamille (or any PMC/commiter), it would be 
really cool to have this patch by @Randgalt merged, wouldn't it? If you have 
any cycles would you mind to review this one? 

Thanks!!!


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zookeeper issue #193: ZOOKEEPER-2608: CLI option for TTL nodes

2017-03-22 Thread eribeiro

Github user eribeiro commented on the issue:

https://github.com/apache/zookeeper/pull/193
  
Hey @Randgalt, awesome work!

Pinging, @skamille @hanm @arshadmohammad to get their blessing. ;)


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2608) Create CLI option for TTL ephemerals

2017-03-22 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936732#comment-15936732
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2608:
---

Github user eribeiro commented on the issue:

https://github.com/apache/zookeeper/pull/193
  
Hey @Randgalt, awesome work!

Pinging, @skamille @hanm @arshadmohammad to get their blessing. ;)


> Create CLI option for TTL ephemerals
> 
>
> Key: ZOOKEEPER-2608
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2608
> Project: ZooKeeper
>  Issue Type: Sub-task
>  Components: c client, java client, jute, server
>Reporter: Camille Fournier
>Assignee: Jordan Zimmerman
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2608-2.patch, ZOOKEEPER-2608-3.patch, 
> ZOOKEEPER-2608.patch
>
>
> Need to update CreateCommand to have the TTL node option



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

ZooKeeper_branch34_openjdk7 - Build # 1438 - Failure

2017-03-22 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1438/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H18 (ubuntu) in workspace 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7
Cloning the remote Git repository
Cloning repository git://git.apache.org/zookeeper.git
 > git init /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7 # 
 > timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git --version # timeout=10
 > git fetch --tags --progress git://git.apache.org/zookeeper.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
No valid HEAD. Skipping the resetting
 > git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git fetch --tags --progress git://git.apache.org/zookeeper.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/branch-3.4^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/branch-3.4^{commit} # timeout=10
Checking out Revision 5897852dba9bbaf78f73bc34ed9cbea5f7c9029a 
(refs/remotes/origin/branch-3.4)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 5897852dba9bbaf78f73bc34ed9cbea5f7c9029a
 > git rev-list 5897852dba9bbaf78f73bc34ed9cbea5f7c9029a # timeout=10
No emails were triggered.
[ZooKeeper_branch34_openjdk7] $ 
/home/jenkins/tools/ant/apache-ant-1.9.9/bin/ant -Dtest.output=yes 
-Dtest.junit.threads=8 -Dtest.junit.output.format=xml -Djavac.target=1.7 clean 
test-core-java
Error: JAVA_HOME is not defined correctly.
  We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
Build step 'Invoke Ant' marked build as failure
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

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

2017-03-22 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/988/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 63.32 MB...]
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
[junit] at 
org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2017-03-22 11:55:18,304 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port14161,name1=Connections,name2=127.0.0.1,name3=0x10072a0bc1b]
[junit] 2017-03-22 11:55:18,404 [myid:] - INFO  [main:ZooKeeper@1324] - 
Session: 0x10072a0bc1b closed
[junit] 2017-03-22 11:55:18,404 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 186661
[junit] 2017-03-22 11:55:18,404 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 1643
[junit] 2017-03-22 11:55:18,405 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-03-22 11:55:18,404 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x10072a0bc1b
[junit] 2017-03-22 11:55:18,405 [myid:] - INFO  [main:ClientBase@558] - 
tearDown starting
[junit] 2017-03-22 11:55:18,405 [myid:] - INFO  [main:ClientBase@528] - 
STOPPING server
[junit] 2017-03-22 11:55:18,405 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:14161
[junit] 2017-03-22 11:55:18,410 [myid:] - INFO  [main:ZooKeeperServer@542] 
- shutting down
[junit] 2017-03-22 11:55:18,411 [myid:] - ERROR [main:ZooKeeperServer@506] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-22 11:55:18,411 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-03-22 11:55:18,411 [myid:] - INFO  
[main:PrepRequestProcessor@1008] - Shutting down
[junit] 2017-03-22 11:55:18,411 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-03-22 11:55:18,412 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-03-22 11:55:18,412 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2017-03-22 11:55:18,412 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port14161,name1=InMemoryDataTree]
[junit] 2017-03-22 11:55:18,412 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port14161]
[junit] 2017-03-22 11:55:18,411 [myid:] - INFO  [ProcessThread(sid:0 
cport:14161)::PrepRequestProcessor@157] - PrepRequestProcessor exited loop!
[junit] 2017-03-22 11:55:18,412 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 14161
[junit] 2017-03-22 11:55:18,413 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2017-03-22 11:55:18,415 [myid:127.0.0.1:14038] - INFO  
[main-SendThread(127.0.0.1:14038):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:14038. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-22 11:55:18,415 [myid:127.0.0.1:14038] - WARN  
[main-SendThread(127.0.0.1:14038):ClientCnxn$SendThread@1235] - Session 
0x100729d6fc5 for server 127.0.0.1/127.0.0.1:14038, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-03-22 11:55:18,418 [myid:] - INFO  [main:ClientBase@583] - 
fdcount after test is: 4830 at start it was 4834
[junit] 2017-03-22 11:55:18,418 [myid:] - INFO  [main:ZKTestCase$1@68] - 
SUCCEEDED testWatcherAutoResetWithLocal
[junit] 2017-03-22 11:55:18,418 [myid:] - INFO  [main:ZKTestCase$1@63] - 
FINISHED testWatcherAutoResetWithLocal
[junit] Tests run:

[GitHub] zookeeper pull request #181: ZOOKEEPER-2706: checkstyle broken on branch-3.4

2017-03-22 Thread rakeshadr

Github user rakeshadr commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/181#discussion_r107370339
  
--- Diff: ivy.xml ---
@@ -58,7 +58,7 @@
 
  
-https://zookeeper.apache.org/doc/r3.4.9/zookeeperAdmin.html#sc_supportedPlatforms`

```
/home/max/Projects/zk/git/b-3.4/build.xml:1592: 
java.lang.UnsupportedClassVersionError: 
com/puppycrawl/tools/checkstyle/ant/CheckstyleAntTask : Unsupported major.minor 
version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:637)

```


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zookeeper pull request #200: ZOOKEEPER-2712: MiniKdc test case intermittentl...

2017-03-22 Thread rakeshadr

Github user rakeshadr closed the pull request at:

https://github.com/apache/zookeeper/pull/200


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

37 matches

Mail list logo