ZooKeeper_branch34_jdk8 - Build # 1132 - Failure

2017-09-18 Thread Apache Jenkins Server 
See https://builds.apache.org/job/ZooKeeper_branch34_jdk8/1132/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 32.44 MB...]
[junit] at 
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
[junit] at 
java.io.BufferedOutputStream.write(BufferedOutputStream.java:95)
[junit] at 
java.util.zip.CheckedOutputStream.write(CheckedOutputStream.java:60)
[junit] at java.io.DataOutputStream.writeInt(DataOutputStream.java:199)
[junit] at 
org.apache.jute.BinaryOutputArchive.writeInt(BinaryOutputArchive.java:55)
[junit] at 
org.apache.zookeeper.data.StatPersisted.serialize(StatPersisted.java:119)
[junit] at 
org.apache.zookeeper.server.DataNode.serialize(DataNode.java:177)
[junit] at 
org.apache.jute.BinaryOutputArchive.writeRecord(BinaryOutputArchive.java:123)
[junit] at 
org.apache.zookeeper.server.DataTree.serializeNode(DataTree.java:1041)
[junit] at 
org.apache.zookeeper.server.DataTree.serializeNode(DataTree.java:1050)
[junit] at 
org.apache.zookeeper.server.DataTree.serialize(DataTree.java:1061)
[junit] at 
org.apache.zookeeper.server.util.SerializeUtils.serializeSnapshot(SerializeUtils.java:138)
[junit] at 
org.apache.zookeeper.server.persistence.FileSnap.serialize(FileSnap.java:215)
[junit] at 
org.apache.zookeeper.server.persistence.FileSnap.serialize(FileSnap.java:232)
[junit] at 
org.apache.zookeeper.server.persistence.FileTxnSnapLog.save(FileTxnSnapLog.java:250)
[junit] at 
org.apache.zookeeper.server.ZooKeeperServer.takeSnapshot(ZooKeeperServer.java:303)
[junit] at 
org.apache.zookeeper.server.SyncRequestProcessor$1.run(SyncRequestProcessor.java:153)
[junit] 2017-09-18 22:58:38,965 [myid:] - ERROR [Snapshot 
Thread:ZooKeeperServer@305] - Severe unrecoverable error, exiting
[junit] java.io.IOException: No space left on device
[junit] at java.io.FileOutputStream.writeBytes(Native Method)
[junit] at java.io.FileOutputStream.write(FileOutputStream.java:326)
[junit] at 
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
[junit] at 
java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
[junit] at 
org.apache.zookeeper.server.persistence.FileSnap.serialize(FileSnap.java:236)
[junit] at 
org.apache.zookeeper.server.persistence.FileTxnSnapLog.save(FileTxnSnapLog.java:250)
[junit] at 
org.apache.zookeeper.server.ZooKeeperServer.takeSnapshot(ZooKeeperServer.java:303)
[junit] at 
org.apache.zookeeper.server.SyncRequestProcessor$1.run(SyncRequestProcessor.java:153)
[junit] 2017-09-18 22:58:38,965 [myid:] - ERROR [Snapshot 
Thread:ZooKeeperServer@305] - Severe unrecoverable error, exiting
[junit] java.io.IOException: No space left on device
[junit] at java.io.FileOutputStream.writeBytes(Native Method)
[junit] at java.io.FileOutputStream.write(FileOutputStream.java:326)
[junit] at 
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
[junit] at 
java.io.BufferedOutputStream.write(BufferedOutputStream.java:95)
[junit] at 
java.util.zip.CheckedOutputStream.write(CheckedOutputStream.java:60)
[junit] at java.io.DataOutputStream.writeInt(DataOutputStream.java:199)
[junit] at 
org.apache.jute.BinaryOutputArchive.writeInt(BinaryOutputArchive.java:55)
[junit] at 
org.apache.zookeeper.data.StatPersisted.serialize(StatPersisted.java:119)
[junit] at 
org.apache.zookeeper.server.DataNode.serialize(DataNode.java:177)
[junit] at 
org.apache.jute.BinaryOutputArchive.writeRecord(BinaryOutputArchive.java:123)
[junit] at 
org.apache.zookeeper.server.DataTree.serializeNode(DataTree.java:1041)
[junit] at 
org.apache.zookeeper.server.DataTree.serializeNode(DataTree.java:1050)
[junit] at 
org.apache.zookeeper.server.DataTree.serialize(DataTree.java:1061)
[junit] at 
org.apache.zookeeper.server.util.SerializeUtils.serializeSnapshot(SerializeUtils.java:138)
[junit] at 
org.apache.zookeeper.server.persistence.FileSnap.serialize(FileSnap.java:215)
[junit] at 
org.apache.zookeeper.server.persistence.FileSnap.serialize(FileSnap.java:232)
[junit] at 
org.apache.zookeeper.server.persistence.FileTxnSnapLog.save(FileTxnSnapLog.java:250)
[junit] at 
org.apache.zookeeper.server.ZooKeeperServer.takeSnapshot(ZooKeeperServer.java:303)
[junit] at 
org.apache.zookeeper.server.SyncRequestProcessor$1.run(SyncRequestProcessor.java:153)
[junit] 2017-09-18 22:58:38,968 [myid:] - INFO  
[SyncThread:2:ZooKeeperServerListenerImpl@42] - Thread SyncThread:2 exits, 
error code 1
[junit] 2017-09-18 22:58:38,969 [myid:] - INFO  
[SyncThread:2:SyncRequestProcessor@186] - SyncRequestProcessor exited!

[jira] [Commented] (ZOOKEEPER-1281) Stat and srvr 4 letter commands are useless on the leader when leaderServes = false

2017-09-18 Thread Varun Thacker (JIRA) 

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

Varun Thacker commented on ZOOKEEPER-1281:
--

Thanks Jon! I hadn't realized that there was a contrib REST module.

I got it to work by  running 


{code}
~/zookeeper-3.4.9/contrib/rest$ java -cp 
"zookeeper-3.4.9-rest.jar:lib/*:conf/:../../zookeeper-3.4.9.jar"  
org.apache.zookeeper.server.jersey.RestMain
{code}

Something worth documenting

> Stat and srvr 4 letter commands are useless on the leader when leaderServes = 
> false
> ---
>
> Key: ZOOKEEPER-1281
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1281
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.3.3
>Reporter: Daniel Lord
>
> When leaderServes = false the leader responds to the stat/srvr  letter words 
> with simply "this ZooKeeper instance is not currently serving requests".  
> While I agree that is an accurate statement it's not terribly useful for 
> monitoring programs.  Additionally, if members of the ensemble are not 
> currently in the quorum it becomes impossible to tell who is out of the 
> quorum and who is the leader of the quorum.
> I'm not sure if the leader should have a specially formatted response for 
> stat/srvr or if it should simply display less information (no connections for 
> example).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

2017-09-18 Thread Apache Jenkins Server 
See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1623/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H17 (couchdbtest ubuntu xenial) in workspace 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # 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 rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision f33a75db1cc18124b6d0a4ee15967901fa6ec493 
(refs/remotes/origin/master)
Commit message: "ZOOKEEPER-2777: There is a typo in zk.py which prevents from 
using/compiling it"
 > git config core.sparsecheckout # timeout=10
 > git checkout -f f33a75db1cc18124b6d0a4ee15967901fa6ec493
 > git rev-list f33a75db1cc18124b6d0a4ee15967901fa6ec493 # timeout=10
No emails were triggered.
[ZooKeeper-trunk-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.

[jira] [Comment Edited] (ZOOKEEPER-1281) Stat and srvr 4 letter commands are useless on the leader when leaderServes = false

2017-09-18 Thread Jon Bringhurst (JIRA) 

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

Jon Bringhurst edited comment on ZOOKEEPER-1281 at 9/18/17 4:52 PM:


{quote}
Is there a workaround for this that people are using when monitoring their 
Zookeeper ensemble?
{quote}

We've been using Jolokia (http://jolokia.org) attached to the Zookeeper process 
with a Python agent that hits the http endpoint, runs through the 
org.apache.ZooKeeperService mbeans, then finally emits various metrics 
(including if the server is a participant, leader, or observer) to our 
monitoring system.

See https://zookeeper.apache.org/doc/r3.4.6/zookeeperJMX.html to get a 
non-exhaustive list of what metrics you can get from Zookeeper's mbeans. This 
setup has worked well for monitoring our 80+ Zookeeper clusters for several 
years now.


was (Author: jonbringhurst):
{quote}
Is there a workaround for this that people are using when monitoring their 
Zookeeper ensemble?
{quote}

We've been using Jolokia (http://jolokia.org) attached to the Zookeeper process 
with a Python agent that hits the http endpoint, runs through the 
org.apache.ZooKeeperService mbeans, then finally emits various metrics 
(including if the server is a participant, leader, or observer) to our 
monitoring system. See 
https://zookeeper.apache.org/doc/r3.4.6/zookeeperJMX.html to get a 
non-exhaustive list of what metrics you can get from Zookeeper's mbeans. This 
setup has worked well for monitoring our 80+ Zookeeper clusters for several 
years now.

> Stat and srvr 4 letter commands are useless on the leader when leaderServes = 
> false
> ---
>
> Key: ZOOKEEPER-1281
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1281
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.3.3
>Reporter: Daniel Lord
>
> When leaderServes = false the leader responds to the stat/srvr  letter words 
> with simply "this ZooKeeper instance is not currently serving requests".  
> While I agree that is an accurate statement it's not terribly useful for 
> monitoring programs.  Additionally, if members of the ensemble are not 
> currently in the quorum it becomes impossible to tell who is out of the 
> quorum and who is the leader of the quorum.
> I'm not sure if the leader should have a specially formatted response for 
> stat/srvr or if it should simply display less information (no connections for 
> example).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ZOOKEEPER-1281) Stat and srvr 4 letter commands are useless on the leader when leaderServes = false

2017-09-18 Thread Jon Bringhurst (JIRA) 

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

Jon Bringhurst commented on ZOOKEEPER-1281:
---

{quote}
Is there a workaround for this that people are using when monitoring their 
Zookeeper ensemble?
{quote}

We've been using Jolokia (http://jolokia.org) attached to the Zookeeper process 
with a Python agent that hits the http endpoint, runs through the 
org.apache.ZooKeeperService mbeans, then finally emits various metrics 
(including if the server is a participant, leader, or observer) to our 
monitoring system. See 
https://zookeeper.apache.org/doc/r3.4.6/zookeeperJMX.html to get a 
non-exhaustive list of what metrics you can get from Zookeeper's mbeans. This 
setup has worked well for monitoring our 80+ Zookeeper clusters for several 
years now.

> Stat and srvr 4 letter commands are useless on the leader when leaderServes = 
> false
> ---
>
> Key: ZOOKEEPER-1281
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1281
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.3.3
>Reporter: Daniel Lord
>
> When leaderServes = false the leader responds to the stat/srvr  letter words 
> with simply "this ZooKeeper instance is not currently serving requests".  
> While I agree that is an accurate statement it's not terribly useful for 
> monitoring programs.  Additionally, if members of the ensemble are not 
> currently in the quorum it becomes impossible to tell who is out of the 
> quorum and who is the leader of the quorum.
> I'm not sure if the leader should have a specially formatted response for 
> stat/srvr or if it should simply display less information (no connections for 
> example).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

ZooKeeper_branch34_openjdk7 - Build # 1649 - Still Failing

2017-09-18 Thread Apache Jenkins Server 
See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1649/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on qnode1 (ubuntu) in workspace 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # 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 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 2d096b48021223a41349eeb379015f1fecffab24 
(refs/remotes/origin/branch-3.4)
Commit message: "ZOOKEEPER-2875: Add ant task for running OWASP dependency 
report"
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 2d096b48021223a41349eeb379015f1fecffab24
 > git rev-list 2d096b48021223a41349eeb379015f1fecffab24 # 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.

[jira] [Assigned] (ZOOKEEPER-2893) very poor choice of logging if client fails to connect to server

2017-09-18 Thread Mark Fenes (JIRA) 

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

Mark Fenes reassigned ZOOKEEPER-2893:
-

Assignee: Mark Fenes

> very poor choice of logging if client fails to connect to server
> 
>
> Key: ZOOKEEPER-2893
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2893
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.6
>Reporter: Paul Millar
>Assignee: Mark Fenes
>
> We are using ZooKeeper in our project and have received reports that, when 
> suffering a networking problem, log files become flooded with messages like:
> {quote}
> 07 Sep 2017 08:22:00 (System) [] Session 0x45d3151be3600a9 for server null, 
> unexpected error, closing socket connection and attempting reconnect
> java.net.NoRouteToHostException: No route to host
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) 
> ~[na:1.8.0_131]
> at 
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) 
> ~[na:1.8.0_131]
> at 
> org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
>  ~[zookeeper-3.4.6.jar:3.4.6-1569965]
> at 
> org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081) 
> ~[zookeeper-3.4.6.jar:3.4.6-1569965]
> {quote}
> Looking at the code that logs this message ({{ClientCnxn}}), there seems to 
> be quite a few problems here:
> # the code logs a stack-trace, even though there is no bug here.  In our 
> project, we treat all logged stack-traces as bugs,
> # if the networking issue is not fixed promptly, the log files is flooded 
> with these message,
> # The message is built using {{ClientCnxnSocket#getRemoteSocketAddress}}, yet 
> in this case, this does not provide the expected information (yielding 
> {{null}}),
> # The log message fails to include a description of what actually went wrong.
> (Additionally, the code uses string concatenation rather than templating when 
> building the message; however, this is an optimisation issue)
> My suggestion is that this log entry is updated so that it doesn't log a 
> stack-trace, but does include some indication why the connection failed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (ZOOKEEPER-2873) print error and/or abort on invalid server definition

2017-09-18 Thread Mark Fenes (JIRA) 

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

Mark Fenes reassigned ZOOKEEPER-2873:
-

Assignee: Mark Fenes

> print error and/or abort on invalid server definition
> -
>
> Key: ZOOKEEPER-2873
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2873
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.4.10
>Reporter: Christopher Smith
>Assignee: Mark Fenes
>Priority: Minor
>
> While bringing up a new cluster, I managed to fat-finger a sed script and put 
> some lines like this into my config file:
> {code}
> server.1=zookeeper1:2888:2888
> {code}
> This led to a predictable spew of error messages when the client and election 
> components fought over the single port. Since a configuration of this case is 
> *always* an error, I suggest that it would be sensible to abort the server 
> startup if an entry is found with the same port for both client and election. 
> (Logging the error explicitly without shutting down is less helpful because 
> of how fast the logs pile up.)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (ZOOKEEPER-2690) Update documentation source for ZOOKEEPER-2574

2017-09-18 Thread Mark Fenes (JIRA) 

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

Mark Fenes reassigned ZOOKEEPER-2690:
-

Assignee: Mark Fenes

> Update documentation source for ZOOKEEPER-2574
> --
>
> Key: ZOOKEEPER-2690
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2690
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Mark Fenes
>Priority: Minor
>  Labels: newbie
>
> In ZOOKEEPER-2574, the documentation change 
> (https://github.com/apache/zookeeper/pull/111/) was done directly on the 
> generated document files instead of on the document source. This JIRA is 
> created to track the work of porting the doc change on the doc source so the 
> change of the doc will not get lost between releases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (ZOOKEEPER-2900) Error: Could not find or load main class com.netflix.exhibitor.application.ExhibitorMain

2017-09-18 Thread Jordan Zimmerman (JIRA) 

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

Jordan Zimmerman resolved ZOOKEEPER-2900.
-
Resolution: Invalid

[~ANH] This is the Apache ZooKeeper issues database. Exhibitor is a separate 
project from Apache ZooKeeper. https://github.com/soabase/exhibitor

> Error: Could not find or load main class 
> com.netflix.exhibitor.application.ExhibitorMain
> 
>
> Key: ZOOKEEPER-2900
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2900
> Project: ZooKeeper
>  Issue Type: Task
> Environment: Ubuntu Server 16.04 LTS
>Reporter: ANH
>
> i am trying to set up an Exhibitor in an ubuntu server using Gradle . The 
> reference link is mentioned below.
> 1) https://blog.imaginea.com/monitoring-zookeeper-with-exhibitor/
> 2) https://github.com/soabase/exhibitor/wiki/Running-Exhibitor
> java -jar /home/ubuntu/gradle/build/libs/exhibitor-1.6.0.jar -C file-- this 
> commands results in an error { Error: Could not find or load main class 
> com.netflix.exhibitor.application.ExhibitorMain }
> What will be the solution ? 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ZOOKEEPER-2900) Error: Could not find or load main class com.netflix.exhibitor.application.ExhibitorMain

2017-09-18 Thread ANH (JIRA) 

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

ANH commented on ZOOKEEPER-2900:


While doing with maven this is the problem i faced--> The goal you specified 
requires a project to execute but there is no POM in this directory 
(/usr/share/maven). Please verify you invoked Maven from the correct 
directory.Embarrassed with these two issues.


> Error: Could not find or load main class 
> com.netflix.exhibitor.application.ExhibitorMain
> 
>
> Key: ZOOKEEPER-2900
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2900
> Project: ZooKeeper
>  Issue Type: Task
> Environment: Ubuntu Server 16.04 LTS
>Reporter: ANH
>
> i am trying to set up an Exhibitor in an ubuntu server using Gradle . The 
> reference link is mentioned below.
> 1) https://blog.imaginea.com/monitoring-zookeeper-with-exhibitor/
> 2) https://github.com/soabase/exhibitor/wiki/Running-Exhibitor
> java -jar /home/ubuntu/gradle/build/libs/exhibitor-1.6.0.jar -C file-- this 
> commands results in an error { Error: Could not find or load main class 
> com.netflix.exhibitor.application.ExhibitorMain }
> What will be the solution ? 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ZOOKEEPER-2900) Error: Could not find or load main class com.netflix.exhibitor.application.ExhibitorMain

2017-09-18 Thread maoling (JIRA) 

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

maoling commented on ZOOKEEPER-2900:


too embarrassed to see an issue about exhibitor
[~randgalt]

> Error: Could not find or load main class 
> com.netflix.exhibitor.application.ExhibitorMain
> 
>
> Key: ZOOKEEPER-2900
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2900
> Project: ZooKeeper
>  Issue Type: Task
> Environment: Ubuntu Server 16.04 LTS
>Reporter: ANH
>
> i am trying to set up an Exhibitor in an ubuntu server using Gradle . The 
> reference link is mentioned below.
> 1) https://blog.imaginea.com/monitoring-zookeeper-with-exhibitor/
> 2) https://github.com/soabase/exhibitor/wiki/Running-Exhibitor
> java -jar /home/ubuntu/gradle/build/libs/exhibitor-1.6.0.jar -C file-- this 
> commands results in an error { Error: Could not find or load main class 
> com.netflix.exhibitor.application.ExhibitorMain }
> What will be the solution ? 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

ZooKeeper_branch35_jdk8 - Build # 674 - Failure

2017-09-18 Thread Apache Jenkins Server 
See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/674/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 59.02 MB...]
[junit] at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1220)
[junit] at 
java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:335)
[junit] at 
java.util.concurrent.LinkedBlockingQueue.put(LinkedBlockingQueue.java:339)
[junit] at 
org.apache.zookeeper.server.quorum.LearnerHandler.shutdown(LearnerHandler.java:921)
[junit] at 
org.apache.zookeeper.server.quorum.LearnerHandler.run(LearnerHandler.java:642)
[junit] 2017-09-18 12:10:04,067 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-2:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2017-09-18 12:10:04,066 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2017-09-18 12:10:04,067 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2017-09-18 12:10:04,067 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2017-09-18 12:10:04,067 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:/127.0.0.1:14076:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2017-09-18 12:10:04,067 [myid:] - WARN  
[LearnerHandler-/127.0.0.1:43080:LearnerHandler@923] - Ignoring unexpected 
exception
[junit] java.lang.InterruptedException
[junit] at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1220)
[junit] at 
java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:335)
[junit] at 
java.util.concurrent.LinkedBlockingQueue.put(LinkedBlockingQueue.java:339)
[junit] at 
org.apache.zookeeper.server.quorum.LearnerHandler.shutdown(LearnerHandler.java:921)
[junit] at 
org.apache.zookeeper.server.quorum.LearnerHandler.run(LearnerHandler.java:642)
[junit] 2017-09-18 12:10:04,068 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:14076)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.5,name2=Leader]
[junit] 2017-09-18 12:10:04,068 [myid:] - INFO  
[/127.0.0.1:14078:QuorumCnxManager$Listener@892] - Leaving listener
[junit] 2017-09-18 12:10:04,068 [myid:] - WARN  
[QuorumPeer[myid=5](plain=/127.0.0.1:14076)(secure=disabled):QuorumPeer@1230] - 
Unexpected exception
[junit] java.lang.InterruptedException
[junit] at java.lang.Object.wait(Native Method)
[junit] at 
org.apache.zookeeper.server.quorum.Leader.lead(Leader.java:571)
[junit] at 
org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:1227)
[junit] 2017-09-18 12:10:04,068 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:14076)(secure=disabled):Leader@634] - 
Shutting down
[junit] 2017-09-18 12:10:04,068 [myid:] - INFO  [main:QuorumUtil@254] - 
Shutting down leader election 
QuorumPeer[myid=5](plain=/127.0.0.1:14076)(secure=disabled)
[junit] 2017-09-18 12:10:04,068 [myid:] - WARN  
[QuorumPeer[myid=5](plain=/127.0.0.1:14076)(secure=disabled):QuorumPeer@1261] - 
PeerState set to LOOKING
[junit] 2017-09-18 12:10:04,068 [myid:] - WARN  
[QuorumPeer[myid=5](plain=/127.0.0.1:14076)(secure=disabled):QuorumPeer@1243] - 
QuorumPeer main thread exited
[junit] 2017-09-18 12:10:04,068 [myid:] - INFO  [main:QuorumUtil@259] - 
Waiting for QuorumPeer[myid=5](plain=/127.0.0.1:14076)(secure=disabled) to exit 
thread
[junit] 2017-09-18 12:10:04,068 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:14076)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5]
[junit] 2017-09-18 12:10:04,069 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:14076)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.5]
[junit] 2017-09-18 12:10:04,069 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:14076)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.1]
[junit] 2017-09-18 12:10:04,069 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:14076)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.2]
[junit] 2017-09-18 12:10:04,069 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:14076)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean

ZooKeeper-trunk-jdk8 - Build # 1206 - Failure

2017-09-18 Thread Apache Jenkins Server 
See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/1206/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 67.05 MB...]
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-09-18 12:00:55,990 [myid:127.0.0.1:21997] - INFO  
[main-SendThread(127.0.0.1:21997):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:21997. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-09-18 12:00:55,991 [myid:127.0.0.1:21997] - WARN  
[main-SendThread(127.0.0.1:21997):ClientCnxn$SendThread@1235] - Session 
0x10212d7e93b0001 for server 127.0.0.1/127.0.0.1:21997, 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-09-18 12:00:56,291 [myid:127.0.0.1:21994] - INFO  
[main-SendThread(127.0.0.1:21994):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:21994. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-09-18 12:00:56,291 [myid:127.0.0.1:21994] - WARN  
[main-SendThread(127.0.0.1:21994):ClientCnxn$SendThread@1235] - Session 
0x212d7e7070001 for server 127.0.0.1/127.0.0.1:21994, 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-09-18 12:00:57,110 [myid:127.0.0.1:21994] - INFO  
[main-SendThread(127.0.0.1:21994):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:21994. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-09-18 12:00:57,111 [myid:127.0.0.1:21994] - WARN  
[main-SendThread(127.0.0.1:21994):ClientCnxn$SendThread@1235] - Session 
0x212d7e707 for server 127.0.0.1/127.0.0.1:21994, 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-09-18 12:00:57,236 [myid:127.0.0.1:21997] - INFO  
[main-SendThread(127.0.0.1:21997):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:21997. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-09-18 12:00:57,237 [myid:127.0.0.1:21997] - WARN  
[main-SendThread(127.0.0.1:21997):ClientCnxn$SendThread@1235] - Session 
0x10212d7e93b0001 for server 127.0.0.1/127.0.0.1:21997, 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-09-18 12:00:57,490 [myid:127.0.0.1:21997] - INFO  
[main-SendThread(127.0.0.1:21997):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:21997. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-09-18 12:00:57,491 [myid:127.0.0.1:21997] - WARN  
[main-SendThread(127.0.0.1:21997):ClientCnxn$SendThread@1235] - Session 
0x10212d7e93b for server 127.0.0.1/127.0.0.1:21997, 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

[jira] [Commented] (ZOOKEEPER-2892) Improve lazy initialize and close stream for `PrepRequestProcessor`

2017-09-18 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on ZOOKEEPER-2892:
--

-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/1031//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1031//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1031//console

This message is automatically generated.

> Improve lazy initialize and close stream for `PrepRequestProcessor`
> ---
>
> Key: ZOOKEEPER-2892
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2892
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Reporter: Benedict Jin
>Assignee: Benedict Jin
>
> Improve lazy initialize and close stream for `PrepRequestProcessor`
> * Delay the initialization of `ChangeRecord` and `ReconfigRequest` variables
> * Close the `ByteArrayOutputStream` I/O stream



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Failed: ZOOKEEPER- PreCommit Build #1031

2017-09-18 Thread Apache Jenkins Server 
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1031/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.68 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/1031//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1031//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1031//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] fdd4567c59041d603d753c0ebe29f6016288868a 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:1666:
 exec returned: 1

Total time: 14 minutes 29 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-2892
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) 
##
4 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testInconsistentPeerType

Error Message:
Should warn about inconsistent peer type

Stack Trace:
junit.framework.AssertionFailedError: Should warn about inconsistent peer type
at 
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testInconsistentPeerType(QuorumPeerMainTest.java:551)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)


FAILED:  
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testQuorumDefaults

Error Message:
fastleaderelection used

Stack Trace:
junit.framework.AssertionFailedError: fastleaderelection used
at 
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testQuorumDefaults(QuorumPeerMainTest.java:674)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)


FAILED:  
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testBadPeerAddressInQuorum

Error Message:
complains about host

Stack Trace:
junit.framework.AssertionFailedError: complains about host
at 
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testBadPeerAddressInQuorum(QuorumPeerMainTest.java:464)
at

[jira] [Commented] (ZOOKEEPER-2892) Improve lazy initialize and close stream for `PrepRequestProcessor`

2017-09-18 Thread ASF GitHub Bot (JIRA) 

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

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

Github user asdf2014 closed the pull request at:

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


> Improve lazy initialize and close stream for `PrepRequestProcessor`
> ---
>
> Key: ZOOKEEPER-2892
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2892
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Reporter: Benedict Jin
>Assignee: Benedict Jin
>
> Improve lazy initialize and close stream for `PrepRequestProcessor`
> * Delay the initialization of `ChangeRecord` and `ReconfigRequest` variables
> * Close the `ByteArrayOutputStream` I/O stream



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] zookeeper pull request #361: ZOOKEEPER-2892: Improve lazy initialize and clo...

2017-09-18 Thread asdf2014 
Github user asdf2014 closed the pull request at:

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


---

[GitHub] zookeeper pull request #361: ZOOKEEPER-2892: Improve lazy initialize and clo...

2017-09-18 Thread asdf2014 
GitHub user asdf2014 reopened a pull request:

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

ZOOKEEPER-2892: Improve lazy initialize and close stream for 
`PrepRequestProcessor`

Improve lazy initialize and close stream for `PrepRequestProcessor`

* Delay the initialization of `ChangeRecord` and `ReconfigRequest` variables
* Close the `ByteArrayOutputStream` I/O stream

@hanm PTAL

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

$ git pull https://github.com/asdf2014/zookeeper ZOOKEEPER-2892

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

https://github.com/apache/zookeeper/pull/361.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 #361


commit 2237131f3e54cf20eb751ff61ce2cf4f8edc5e3e
Author: asdf2014 
Date:   2017-09-12T01:18:43Z

ZOOKEEPER-2892: Improve lazy initialize & close stream for 
`PrepRequestProcessor`




---

[jira] [Commented] (ZOOKEEPER-2892) Improve lazy initialize and close stream for `PrepRequestProcessor`

2017-09-18 Thread ASF GitHub Bot (JIRA) 

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

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

GitHub user asdf2014 reopened a pull request:

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

ZOOKEEPER-2892: Improve lazy initialize and close stream for 
`PrepRequestProcessor`

Improve lazy initialize and close stream for `PrepRequestProcessor`

* Delay the initialization of `ChangeRecord` and `ReconfigRequest` variables
* Close the `ByteArrayOutputStream` I/O stream

@hanm PTAL

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

$ git pull https://github.com/asdf2014/zookeeper ZOOKEEPER-2892

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

https://github.com/apache/zookeeper/pull/361.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 #361


commit 2237131f3e54cf20eb751ff61ce2cf4f8edc5e3e
Author: asdf2014 
Date:   2017-09-12T01:18:43Z

ZOOKEEPER-2892: Improve lazy initialize & close stream for 
`PrepRequestProcessor`




> Improve lazy initialize and close stream for `PrepRequestProcessor`
> ---
>
> Key: ZOOKEEPER-2892
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2892
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Reporter: Benedict Jin
>Assignee: Benedict Jin
>
> Improve lazy initialize and close stream for `PrepRequestProcessor`
> * Delay the initialization of `ChangeRecord` and `ReconfigRequest` variables
> * Close the `ByteArrayOutputStream` I/O stream



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

ZooKeeper_branch35_openjdk7 - Build # 672 - Failure

2017-09-18 Thread Apache Jenkins Server 
See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/672/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H27 (ubuntu xenial) in workspace 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_openjdk7
Cloning the remote Git repository
Cloning repository git://git.apache.org/zookeeper.git
 > git init /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_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
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.5^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/branch-3.5^{commit} # timeout=10
Checking out Revision b66a12c5ca6f99d7d6e8a9c078ef48beee93017b 
(refs/remotes/origin/branch-3.5)
Commit message: "ZOOKEEPER-2875: Add ant task for running OWASP dependency 
report"
 > git config core.sparsecheckout # timeout=10
 > git checkout -f b66a12c5ca6f99d7d6e8a9c078ef48beee93017b
 > git rev-list b66a12c5ca6f99d7d6e8a9c078ef48beee93017b # timeout=10
No emails were triggered.
[ZooKeeper_branch35_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.

[jira] [Created] (ZOOKEEPER-2900) Error: Could not find or load main class com.netflix.exhibitor.application.ExhibitorMain

2017-09-18 Thread ANH (JIRA) 
ANH created ZOOKEEPER-2900:
--

 Summary: Error: Could not find or load main class 
com.netflix.exhibitor.application.ExhibitorMain
 Key: ZOOKEEPER-2900
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2900
 Project: ZooKeeper
  Issue Type: Task
 Environment: Ubuntu Server 16.04 LTS
Reporter: ANH


i am trying to set up an Exhibitor in an ubuntu server using Gradle . The 
reference link is mentioned below.
1) https://blog.imaginea.com/monitoring-zookeeper-with-exhibitor/
2) https://github.com/soabase/exhibitor/wiki/Running-Exhibitor

java -jar /home/ubuntu/gradle/build/libs/exhibitor-1.6.0.jar -C file-- this 
commands results in an error { Error: Could not find or load main class 
com.netflix.exhibitor.application.ExhibitorMain }
What will be the solution ? 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (ZOOKEEPER-2898) Zookeeper Management

2017-09-18 Thread ANH (JIRA) 

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

ANH updated ZOOKEEPER-2898:
---
Comment: was deleted

(was: I have created a directory named 'maven' , changed directory to maven ( 
cd maven ), downloaded POM files by executing-- wget 
http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd .   i can see that file  
maven-4.0.0.xsd exists inside the directory. 
After giving the mvn clean package command i am getting the error 
" The goal you specified requires a project to execute but there is no POM in 
this directory (/home/ubuntu/maven). Please verify you invoked Maven from the 
correct directory. ". How to rectify it ??
)

> Zookeeper Management
> 
>
> Key: ZOOKEEPER-2898
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2898
> Project: ZooKeeper
>  Issue Type: Improvement
>Affects Versions: 3.4.9
>Reporter: ANH
>
> Is there any zookeeper management and monitoring tool? The results which i 
> got after googling it only leads to monitoring tools for zookeeper eg --> 
> zookeeper dashboard, zkfarmer, signalfx etc. I am already getting the the 
> features of these tools by using sensu. I need a tool like kafkamanager. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)