[jira] [Commented] (ZOOKEEPER-1177) Enabling a large number of watches for a large number of clients

[Patrick Hunt (JIRA)]

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

Patrick Hunt commented on ZOOKEEPER-1177:
-

Hi [~praste] - there was never a followup that I'm aware of.

> Enabling a large number of watches for a large number of clients
> 
>
> Key: ZOOKEEPER-1177
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1177
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.3.3
>Reporter: Vishal Kathuria
>Assignee: Thawan Kooburat
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-1177.patch, ZOOKEEPER-1177.patch, 
> ZooKeeper-with-fix-for-findbugs-warning.patch, ZooKeeper.patch, 
> Zookeeper-after-resolving-merge-conflicts.patch
>
>
> In my ZooKeeper, I see watch manager consuming several GB of memory and I dug 
> a bit deeper.
> In the scenario I am testing, I have 10K clients connected to an observer. 
> There are about 20K znodes in ZooKeeper, each is about 1K - so about 20M data 
> in total.
> Each client fetches and puts watches on all the znodes. That is 200 million 
> watches.
> It seems a single watch takes about 100  bytes. I am currently at 14528037 
> watches and according to the yourkit profiler, WatchManager has 1.2 G 
> already. This is not going to work as it might end up needing 20G of RAM just 
> for the watches.
> So we need a more compact way of storing watches. Here are the possible 
> solutions.
> 1. Use a bitmap instead of the current hashmap. In this approach, each znode 
> would get a unique id when its gets created. For every session, we can keep 
> track of a bitmap that indicates the set of znodes this session is watching. 
> A bitmap, assuming a 100K znodes, would be 12K. For 10K sessions, we can keep 
> track of watches using 120M instead of 20G.
> 2. This second idea is based on the observation that clients watch znodes in 
> sets (for example all znodes under a folder). Multiple clients watch the same 
> set and the total number of sets is a couple of orders of magnitude smaller 
> than the total number of znodes. In my scenario, there are about 100 sets. So 
> instead of keeping track of watches at the znode level, keep track of it at 
> the set level. It may mean that get may also need to be implemented at the 
> set level. With this, we can save the watches in 100M.
> Are there any other suggestions of solutions?
> Thanks
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] move Apache Zookeeper to git

[Patrick Hunt]

Quick update (more details on the INFRA jira). It might take upwards of 24
hours to do the svn->git migration although our repo isn't that large,
likely less. INFRA can do it, for example, on Saturday around 18:00 UTC.
Any concerns with such an approach?

Patrick

On Sun, Sep 4, 2016 at 9:20 PM, Patrick Hunt  wrote:

> Follow along here: https://issues.apache.org/jira/browse/INFRA-12573
>
> Patrick
>
> On Sun, Sep 4, 2016 at 8:33 AM, Benjamin Reed  wrote:
>
>> with 10 votes for (5 of which are from the PMC) on no votes against. the
>> vote passes.
>>
>> pat please make git happen! :)
>>
>> thanx for voting!
>>
>> On Thu, Sep 1, 2016 at 9:25 AM, Michael Han  wrote:
>>
>> > +1
>> >
>> > On Thu, Sep 1, 2016 at 6:08 AM, Michelle Tan 
>> wrote:
>> >
>> > > +1
>> > >
>> > > On Thu, Sep 1, 2016 at 2:01 PM, Flavio Junqueira 
>> wrote:
>> > >
>> > > > +1
>> > > >
>> > > > > On 01 Sep 2016, at 13:28, Edward Ribeiro <
>> edward.ribe...@gmail.com>
>> > > > wrote:
>> > > > >
>> > > > > +1 (non binding)
>> > > > >
>> > > > > On Thu, Sep 1, 2016 at 3:44 AM, Jordan Zimmerman <
>> > > > jor...@jordanzimmerman.com
>> > > > >> wrote:
>> > > > >
>> > > > >> +1 (non binding)
>> > > > >>
>> > > > >>> On Aug 31, 2016, at 8:29 PM, Benjamin Reed 
>> > wrote:
>> > > > >>>
>> > > > >>> flip the switch to git and update the relevant scripts and docs.
>> > > > >>>
>> > > > >>> i couldn't figure out which timeframe this falls under in the
>> > voting
>> > > > >>> procedure table, but i think it's safe to go with 3 days, so the
>> > vote
>> > > > >> will
>> > > > >>> close on Saturday, September 3 at 6:30pm pdt.
>> > > > >>>
>> > > > >>> +1 from me
>> > > > >>
>> > > > >>
>> > > >
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> > Cheers
>> > Michael.
>> >
>>
>
>

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

[Patrick Hunt (JIRA)]

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

Patrick Hunt commented on ZOOKEEPER-1045:
-

I did additional research on this. In particular I met with Esteban who's very 
familiar with the Hadoop and HBase code. We spent a considerable amount of time 
discussing and looking through the hbase/hadoop code. We couldn't find any 
direct parallels between what they are doing and what we are considering 
however. That said we came up with the following proposal. The idea being to 
simplify the implementation, allow expansion/extension in future, and in 
particular ensure that what we have initially is secure. Here's my proposal:

1) first, authenticate the remote entity (learner) and ensure they have valid 
kerberos credentials - we already have that in the patch.

2) if the learner has a principal of the form user/host@realm we compare just 
the user and realm, and not the host. If a credential with user@realm is 
provided we compare the user and realm similarly.

In neither case will we compare the host. This means that a particular user in 
realm can operate from any host as a quorum peer (if the user and realm match). 
It simplifies things greatly as we don't have to configure each/every ZK server 
in the ensemble with the principal of every other ZK server participating in 
the ensemble. If there are multiple ZK services (ensembles) in a realm then the 
user will need to ensure that differing user names are provided in the 
principal, otherwise servers from "other" ZK clusters could join services they 
are not meant to join. We should ensure that the documentation calls this out.

IIUC our current patch correctly this just means that we need to parse/compare 
the user and realm when authorizing. In future if there is the need to enhance 
this functionality in some way we can add additional configuration options for 
that.

Thoughts?


> Support Quorum Peer mutual authentication via SASL
> --
>
> Key: ZOOKEEPER-1045
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1045
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: server
>Reporter: Eugene Koontz
>Assignee: Rakesh R
>Priority: Critical
> Fix For: 3.4.10, 3.5.3
>
> Attachments: 0001-ZOOKEEPER-1045-br-3-4.patch, 
> 1045_failing_phunt.tar.gz, HOST_RESOLVER-ZK-1045.patch, 
> TEST-org.apache.zookeeper.server.quorum.auth.QuorumAuthUpgradeTest.txt, 
> ZK-1045-test-case-failure-logs.zip, ZOOKEEPER-1045-00.patch, 
> ZOOKEEPER-1045-Rolling Upgrade Design Proposal.pdf, 
> ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, 
> ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, 
> ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, 
> ZOOKEEPER-1045TestValidationDesign.pdf
>
>
> ZOOKEEPER-938 addresses mutual authentication between clients and servers. 
> This bug, on the other hand, is for authentication among quorum peers. 
> Hopefully much of the work done on SASL integration with Zookeeper for 
> ZOOKEEPER-938 can be used as a foundation for this enhancement.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1330) Zookeeper server not serving the client request even after completion of Leader election

[Cameron McKenzie (JIRA)]

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

Cameron McKenzie commented on ZOOKEEPER-1330:
-

Have there been any updates on this? We seem to be running into the same 
problem. The leader election completes after some period but the nodes are 
taking 15+ seconds before they stop logging the "ZooKeeperServer no running" 
message and start processing traffic. This is happening on the leader and 
followers. See logs excerpts below. After this everything seems to go back to 
normal.

>From the leader:

2016-09-04 01:00:41,024 [myid:5] - INFO  
[QuorumPeer[myid=5]/0:0:0:0:0:0:0:0:2181:Leader@358] - LEADING - LEADER 
ELECTION TOOK - 10251

2016-09-04 01:00:48,814 [myid:5] - INFO  
[QuorumPeer[myid=5]/0:0:0:0:0:0:0:0:2181:Leader@943] - Have quorum of 
supporters, sids: [ 1,2,5 ]; starting up and setting last processed zxid: 
0x16000

>From a follower:

2016-09-04 01:00:43,823 [myid:3] - INFO  
[QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2181:Follower@63] - FOLLOWING - LEADER 
ELECTION TOOK - 8684

016-09-04 01:00:57,964 [myid:3] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted 
socket connection from /X.X.X.X:39700
2016-09-04 01:00:57,964 [myid:3] - WARN  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@362] - Exception 
causing close of session 0x0 due to java.io.IOException: ZooKeeperServer not 
running
2016-09-04 01:00:57,964 [myid:3] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007] - Closed socket 
connection for client /X.X.X.X:39700 (no session established for client)
2016-09-04 01:00:58,055 [myid:3] - WARN  
[QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2181:Follower@118] - Got zxid 0x160c80 
expected 0x1



> Zookeeper server not serving the client request even after completion of 
> Leader election
> 
>
> Key: ZOOKEEPER-1330
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1330
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.0
> Environment: 3 zk quorum
>Reporter: amith
>Priority: Minor
> Fix For: 3.5.3, 3.6.0
>
>
> Have a cluster of 3 zookeepers
> 90 clients are connected to the server
> leader got killed and started
> the other 2 zookeeper started FLE and Leader was elected
> But its taking nearly 10 sec for this server to server requests and saying 
> "ZooKeeperServer not running" message..?
> Why is this even after Leader election SERVER IS NOT RUNNING !!
> 2011-12-19 16:12:29,732 [myid:2] - WARN  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2182:NIOServerCnxn@354] - Exception 
> causing close of session 0x0 due to java.io.IOException: ZooKeeperServer not 
> running
> 2011-12-19 16:12:29,733 [myid:2] - INFO  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2182:NIOServerCnxn@1000] - Closed 
> socket connection for client /10.18.47.148:51965 (no session established for 
> client)
> 2011-12-19 16:12:29,753 [myid:2] - INFO  
> [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2182:QuorumPeer@747] - LEADING
> 2011-12-19 16:12:29,762 [myid:2] - INFO  
> [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2182:Leader@58] - TCP NoDelay set to: true
> 2011-12-19 16:12:29,765 [myid:2] - INFO  
> [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2182:ZooKeeperServer@168] - Created 
> server with tickTime 2000 minSessionTimeout 4000 maxSessionTimeout 4 
> datadir ../dataDir/version-2 snapdir ../dataDir/version-2
> 2011-12-19 16:12:29,766 [myid:2] - INFO  
> [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2182:Leader@294] - LEADING - LEADER 
> ELECTION TOOK - 4663
> 2011-12-19 16:12:29,776 [myid:2] - INFO  
> [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2182:FileSnap@83] - Reading snapshot 
> ../dataDir/version-2/snapshot.100013661
> 2011-12-19 16:12:29,831 [myid:2] - INFO  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2182:NIOServerCnxnFactory@213] - 
> Accepted socket connection from /10.18.47.148:51982
> 2011-12-19 16:12:29,831 [myid:2] - WARN  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2182:NIOServerCnxn@354] - Exception 
> causing close of session 0x0 due to java.io.IOException: ZooKeeperServer not 
> running
> 2011-12-19 16:12:29,832 [myid:2] - INFO  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2182:NIOServerCnxn@1000] - Closed 
> socket connection for client /10.18.47.148:51982 (no session established for 
> client)
> 2011-12-19 16:12:29,884 [myid:2] - INFO  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2182:NIOServerCnxnFactory@213] - 
> Accepted socket connection from /10.18.47.148:51989
> 2011-12-19 16:12:29,884 [myid:2] - WARN  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2182:NIOServerCnxn@354] - Exception 
> causing close of session 0x0 due to java.io.IOException: ZooKeeperServer not 
> running



--
This message

[jira] [Commented] (ZOOKEEPER-2169) Enable creation of nodes with TTLs

[Jordan Zimmerman (JIRA)]

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

Jordan Zimmerman commented on ZOOKEEPER-2169:
-

No. I mask out the special ephemeral value from the Stat. If I didn't it could 
break existing apps. 

> Enable creation of nodes with TTLs
> --
>
> Key: ZOOKEEPER-2169
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2169
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: c client, java client, jute, server
>Affects Versions: 3.6.0
>Reporter: Camille Fournier
>Assignee: Jordan Zimmerman
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2169-2.patch, ZOOKEEPER-2169-3.patch, 
> ZOOKEEPER-2169-4.patch, ZOOKEEPER-2169-5.patch, ZOOKEEPER-2169.patch
>
>
> As a user, I would like to be able to create a node that is NOT tied to a 
> session but that WILL expire automatically if action is not taken by some 
> client within a time window.
> I propose this to enable clients interacting with ZK via http or other "thin 
> clients" to create ephemeral-like nodes.
> Some ideas for the design, up for discussion:
> The node should support all normal ZK node operations including ACLs, 
> sequential key generation, etc, however, it should not support the ephemeral 
> flag. The node will be created with a TTL that is updated via a refresh 
> operation. 
> The ZK quorum will watch this node similarly to the way that it watches for 
> session liveness; if the node is not refreshed within the TTL, it will expire.
> QUESTIONS:
> 1) Should we let the refresh operation set the TTL to a different base value?
> 2) If so, should the setting of the TTL to a new base value cause a watch to 
> fire?
> 3) Do we want to allow these nodes to have children or prevent this similar 
> to ephemeral nodes?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2169) Enable creation of nodes with TTLs

[Benjamin Reed (JIRA)]

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

Benjamin Reed commented on ZOOKEEPER-2169:
--

can't you just do a stat to find this out?


> Enable creation of nodes with TTLs
> --
>
> Key: ZOOKEEPER-2169
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2169
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: c client, java client, jute, server
>Affects Versions: 3.6.0
>Reporter: Camille Fournier
>Assignee: Jordan Zimmerman
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2169-2.patch, ZOOKEEPER-2169-3.patch, 
> ZOOKEEPER-2169-4.patch, ZOOKEEPER-2169-5.patch, ZOOKEEPER-2169.patch
>
>
> As a user, I would like to be able to create a node that is NOT tied to a 
> session but that WILL expire automatically if action is not taken by some 
> client within a time window.
> I propose this to enable clients interacting with ZK via http or other "thin 
> clients" to create ephemeral-like nodes.
> Some ideas for the design, up for discussion:
> The node should support all normal ZK node operations including ACLs, 
> sequential key generation, etc, however, it should not support the ephemeral 
> flag. The node will be created with a TTL that is updated via a refresh 
> operation. 
> The ZK quorum will watch this node similarly to the way that it watches for 
> session liveness; if the node is not refreshed within the TTL, it will expire.
> QUESTIONS:
> 1) Should we let the refresh operation set the TTL to a different base value?
> 2) If so, should the setting of the TTL to a new base value cause a watch to 
> fire?
> 3) Do we want to allow these nodes to have children or prevent this similar 
> to ephemeral nodes?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2549) As NettyServerCnxn.sendResponse() allows all the exception to bubble up it can stop main ZK requests processing thread

[Yuliya Feldman (JIRA)]

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

Yuliya Feldman commented on ZOOKEEPER-2549:
---

>>> Should we also do similar updates to NIOServerCnx which swallows every 
>>> exception instead of converting them to IOException, for the purpose of 
>>> consistency?

Sure

>>> Also, for tests, might be good to reset system properties in teardown via 
>>> System.clearProperty.

Yep - will do

> As NettyServerCnxn.sendResponse() allows all the exception to bubble up it 
> can stop main ZK requests processing thread
> --
>
> Key: ZOOKEEPER-2549
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2549
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.1
>Reporter: Yuliya Feldman
>Assignee: Yuliya Feldman
> Attachments: ZOOKEEPER-2549.patch, ZOOKEEPER-2549.patch
>
>
> As NettyServerCnxn.sendResponse() allows all the exception to bubble up it 
> can stop main ZK requests processing thread and make Zookeeper server look 
> like it is hanging, while it just can not process any request anymore.
> Idea is to catch all the exceptions in NettyServerCnxn.sendResponse() , 
> convert them to IOException and allow it propagating up



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: ZOOKEEPER-2558 PreCommit Build #3394

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 450844 lines...]
 [exec] Please justify why no new tests are needed 
for this patch.
 [exec] Also please list what manual steps were 
performed to verify this patch.
 [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 2.0.3) 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 passed 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-Build/3394//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3394//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3394//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] 73c4398a4596e035d6bcfaefe4b7eb14b29498ca logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1605:
 exec returned: 1

Total time: 17 minutes 38 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-2558
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) 
##
All tests passed

[jira] [Commented] (ZOOKEEPER-2558) Potential memory leak in recordio.c

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-2558:
--

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12827267/ZOOKEEPER-2558.patch
  against trunk revision 1757584.

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

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

+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 2.0.3) 
warnings.

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

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

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

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

This message is automatically generated.

> Potential memory leak in recordio.c
> ---
>
> Key: ZOOKEEPER-2558
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2558
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: c client
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>Priority: Minor
> Fix For: 3.4.10, 3.5.3
>
> Attachments: ZOOKEEPER-2558.patch
>
>
> We have code like this in {{create_buffer_iarchive}} and 
> {{create_buffer_oarchive}}:
> {code}
> struct iarchive *ia = malloc(sizeof(*ia));
> struct buff_struct *buff = malloc(sizeof(struct buff_struct));
> if (!ia) return 0;
> if (!buff) {
> free(ia);
> return 0;
> }
> {code}
> If first malloc failed but second succeeds, then the memory allocated with 
> second malloc will not get freed when the function returned. One could argue 
> that if first malloc failed the second will also fail (i.e. when system run 
> out of memory), but I could also see the possibility of the opposite (the 
> first malloc failed because heap fragmentation but the second succeeds).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2549) As NettyServerCnxn.sendResponse() allows all the exception to bubble up it can stop main ZK requests processing thread

[Michael Han (JIRA)]

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

Michael Han commented on ZOOKEEPER-2549:


Should we also do similar updates to NIOServerCnx which swallows every 
exception instead of converting them to IOException, for the purpose of 
consistency?

Also, for tests, might be good to reset system properties in teardown via 
System.clearProperty.

> As NettyServerCnxn.sendResponse() allows all the exception to bubble up it 
> can stop main ZK requests processing thread
> --
>
> Key: ZOOKEEPER-2549
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2549
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.1
>Reporter: Yuliya Feldman
>Assignee: Yuliya Feldman
> Attachments: ZOOKEEPER-2549.patch, ZOOKEEPER-2549.patch
>
>
> As NettyServerCnxn.sendResponse() allows all the exception to bubble up it 
> can stop main ZK requests processing thread and make Zookeeper server look 
> like it is hanging, while it just can not process any request anymore.
> Idea is to catch all the exceptions in NettyServerCnxn.sendResponse() , 
> convert them to IOException and allow it propagating up



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2549) As NettyServerCnxn.sendResponse() allows all the exception to bubble up it can stop main ZK requests processing thread

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-2549:
--

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12827265/ZOOKEEPER-2549.patch
  against trunk revision 1757584.

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

+1 tests included.  The patch appears to include 4 new or modified 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 2.0.3) 
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-Build/3393//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3393//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3393//console

This message is automatically generated.

> As NettyServerCnxn.sendResponse() allows all the exception to bubble up it 
> can stop main ZK requests processing thread
> --
>
> Key: ZOOKEEPER-2549
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2549
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.1
>Reporter: Yuliya Feldman
>Assignee: Yuliya Feldman
> Attachments: ZOOKEEPER-2549.patch, ZOOKEEPER-2549.patch
>
>
> As NettyServerCnxn.sendResponse() allows all the exception to bubble up it 
> can stop main ZK requests processing thread and make Zookeeper server look 
> like it is hanging, while it just can not process any request anymore.
> Idea is to catch all the exceptions in NettyServerCnxn.sendResponse() , 
> convert them to IOException and allow it propagating up



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: ZOOKEEPER-2549 PreCommit Build #3393

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 454032 lines...]
 [exec] +1 tests included.  The patch appears to include 4 new or 
modified 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 2.0.3) 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-Build/3393//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3393//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3393//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] 1ca13e81ee2a2cd3175c4aa31972f236b5400bd5 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1605:
 exec returned: 1

Total time: 19 minutes 41 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Compressed 559.54 KB of artifacts by 28.6% relative to #3386
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-2549
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) 
##
3 tests failed.
FAILED:  
org.apache.zookeeper.server.ZxidRolloverTest.testRolloverThenLeaderRestart

Error Message:
waiting for server up

Stack Trace:
junit.framework.AssertionFailedError: waiting for server up
at 
org.apache.zookeeper.server.ZxidRolloverTest.start(ZxidRolloverTest.java:159)
at 
org.apache.zookeeper.server.ZxidRolloverTest.testRolloverThenLeaderRestart(ZxidRolloverTest.java:370)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)


FAILED:  org.apache.zookeeper.test.ReconfigTest.testQuorumSystemChange

Error Message:
KeeperErrorCode = Session expired for 

Stack Trace:
org.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode = 
Session expired for 
at org.apache.zookeeper.KeeperException.create(KeeperException.java:131)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
at org.apache.zookeeper.ZooKeeper.reconfig(ZooKeeper.java:2153)
at org.apache.zookeeper.ZooKeeper.reconfig(ZooKeeper.java:2169)
at org.apache.zookeeper.test.ReconfigTest.reconfig(ReconfigTest.java:74)
at 
org.apache.zookeeper.test.ReconfigTest.testQuorumSystemChange(ReconfigTest.java:806)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)


FAILED:  org.apache.zookeeper.test.LETest.testLE

Error Message:
Threads didn't join

[jira] [Updated] (ZOOKEEPER-2558) Potential memory leak in recordio.c

[Michael Han (JIRA)]

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

Michael Han updated ZOOKEEPER-2558:
---
Attachment: ZOOKEEPER-2558.patch

Not a big deal here, but good to stick to better practice. Attach a patch.

> Potential memory leak in recordio.c
> ---
>
> Key: ZOOKEEPER-2558
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2558
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: c client
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>Priority: Minor
> Fix For: 3.4.10, 3.5.3
>
> Attachments: ZOOKEEPER-2558.patch
>
>
> We have code like this in {{create_buffer_iarchive}} and 
> {{create_buffer_oarchive}}:
> {code}
> struct iarchive *ia = malloc(sizeof(*ia));
> struct buff_struct *buff = malloc(sizeof(struct buff_struct));
> if (!ia) return 0;
> if (!buff) {
> free(ia);
> return 0;
> }
> {code}
> If first malloc failed but second succeeds, then the memory allocated with 
> second malloc will not get freed when the function returned. One could argue 
> that if first malloc failed the second will also fail (i.e. when system run 
> out of memory), but I could also see the possibility of the opposite (the 
> first malloc failed because heap fragmentation but the second succeeds).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ZOOKEEPER-2558) Potential memory leak in recordio.c

[Michael Han (JIRA)]

Michael Han created ZOOKEEPER-2558:
--

 Summary: Potential memory leak in recordio.c
 Key: ZOOKEEPER-2558
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2558
 Project: ZooKeeper
  Issue Type: Bug
  Components: c client
Affects Versions: 3.5.2, 3.4.9
Reporter: Michael Han
Assignee: Michael Han
Priority: Minor
 Fix For: 3.4.10, 3.5.3


We have code like this in {{create_buffer_iarchive}} and 
{{create_buffer_oarchive}}:

{code}
struct iarchive *ia = malloc(sizeof(*ia));
struct buff_struct *buff = malloc(sizeof(struct buff_struct));
if (!ia) return 0;
if (!buff) {
free(ia);
return 0;
}
{code}

If first malloc failed but second succeeds, then the memory allocated with 
second malloc will not get freed when the function returned. One could argue 
that if first malloc failed the second will also fail (i.e. when system run out 
of memory), but I could also see the possibility of the opposite (the first 
malloc failed because heap fragmentation but the second succeeds).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2549) As NettyServerCnxn.sendResponse() allows all the exception to bubble up it can stop main ZK requests processing thread

[Yuliya Feldman (JIRA)]

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

Yuliya Feldman updated ZOOKEEPER-2549:
--
Attachment: ZOOKEEPER-2549.patch

Reattaching just to trigger the build

> As NettyServerCnxn.sendResponse() allows all the exception to bubble up it 
> can stop main ZK requests processing thread
> --
>
> Key: ZOOKEEPER-2549
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2549
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.1
>Reporter: Yuliya Feldman
>Assignee: Yuliya Feldman
> Attachments: ZOOKEEPER-2549.patch, ZOOKEEPER-2549.patch
>
>
> As NettyServerCnxn.sendResponse() allows all the exception to bubble up it 
> can stop main ZK requests processing thread and make Zookeeper server look 
> like it is hanging, while it just can not process any request anymore.
> Idea is to catch all the exceptions in NettyServerCnxn.sendResponse() , 
> convert them to IOException and allow it propagating up



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1177) Enabling a large number of watches for a large number of clients

[Pushkar Raste (JIRA)]

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

Pushkar Raste commented on ZOOKEEPER-1177:
--

[~phunt] - Is this issue fixed. I was wondering how many watches zookeeper can 
handle before we start noticing performance issues and can across this open 
ticket. 

> Enabling a large number of watches for a large number of clients
> 
>
> Key: ZOOKEEPER-1177
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1177
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.3.3
>Reporter: Vishal Kathuria
>Assignee: Thawan Kooburat
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-1177.patch, ZOOKEEPER-1177.patch, 
> ZooKeeper-with-fix-for-findbugs-warning.patch, ZooKeeper.patch, 
> Zookeeper-after-resolving-merge-conflicts.patch
>
>
> In my ZooKeeper, I see watch manager consuming several GB of memory and I dug 
> a bit deeper.
> In the scenario I am testing, I have 10K clients connected to an observer. 
> There are about 20K znodes in ZooKeeper, each is about 1K - so about 20M data 
> in total.
> Each client fetches and puts watches on all the znodes. That is 200 million 
> watches.
> It seems a single watch takes about 100  bytes. I am currently at 14528037 
> watches and according to the yourkit profiler, WatchManager has 1.2 G 
> already. This is not going to work as it might end up needing 20G of RAM just 
> for the watches.
> So we need a more compact way of storing watches. Here are the possible 
> solutions.
> 1. Use a bitmap instead of the current hashmap. In this approach, each znode 
> would get a unique id when its gets created. For every session, we can keep 
> track of a bitmap that indicates the set of znodes this session is watching. 
> A bitmap, assuming a 100K znodes, would be 12K. For 10K sessions, we can keep 
> track of watches using 120M instead of 20G.
> 2. This second idea is based on the observation that clients watch znodes in 
> sets (for example all znodes under a folder). Multiple clients watch the same 
> set and the total number of sets is a couple of orders of magnitude smaller 
> than the total number of znodes. In my scenario, there are about 100 sets. So 
> instead of keeping track of watches at the znode level, keep track of it at 
> the set level. It may mean that get may also need to be implemented at the 
> set level. With this, we can save the watches in 100M.
> Are there any other suggestions of solutions?
> Thanks
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: ZOOKEEPER-2557 PreCommit Build #3392

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 438767 lines...]
 [exec] +1 tests included.  The patch appears to include 1 new or 
modified 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 2.0.3) 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-Build/3392//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3392//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3392//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] ae7e0b68cd862eb13574b40ab9df7d013932bde2 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1605:
 exec returned: 1

Total time: 17 minutes 55 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Compressed 559.16 KB of artifacts by 40.1% relative to #3386
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-2557
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) 
##
7 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.ReconfigLegacyTest.testConfigFileBackwardCompatibility

Error Message:
waiting for server 1 being up

Stack Trace:
junit.framework.AssertionFailedError: waiting for server 1 being up
at 
org.apache.zookeeper.server.quorum.ReconfigLegacyTest.testConfigFileBackwardCompatibility(ReconfigLegacyTest.java:86)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)


FAILED:  org.apache.zookeeper.test.ReconfigTest.testQuorumSystemChange

Error Message:
KeeperErrorCode = Session expired for 

Stack Trace:
org.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode = 
Session expired for 
at org.apache.zookeeper.KeeperException.create(KeeperException.java:131)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
at org.apache.zookeeper.ZooKeeper.reconfig(ZooKeeper.java:2153)
at org.apache.zookeeper.ZooKeeper.reconfig(ZooKeeper.java:2169)
at org.apache.zookeeper.test.ReconfigTest.reconfig(ReconfigTest.java:74)
at 
org.apache.zookeeper.test.ReconfigTest.testQuorumSystemChange(ReconfigTest.java:806)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)


FAILED:  org.apache.zookeeper.test.ReconfigTest.testRemoveAddTwo

Error Message:
waiting for server up

Stack Trace:
junit.frame

[jira] [Commented] (ZOOKEEPER-2557) Update gitignore to account for other file extensions

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-2557:
--

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12827214/ZOOKEEPER-2557.patch
  against trunk revision 1757584.

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

+1 tests included.  The patch appears to include 1 new or modified 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 2.0.3) 
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-Build/3392//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3392//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3392//console

This message is automatically generated.

> Update gitignore to account for other file extensions
> -
>
> Key: ZOOKEEPER-2557
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2557
> Project: ZooKeeper
>  Issue Type: Improvement
>Affects Versions: 3.4.8
>Reporter: Edward Ribeiro
>Assignee: Edward Ribeiro
>Priority: Trivial
>  Labels: easyfix
> Attachments: ZOOKEEPER-2557.patch
>
>
> We are in the process of moving from subversion to git, but I have seen that 
> the current ZK's {{gitignore}} doesn't account for many spurious types of 
> files (e.g., *.swp, *.tmp) as well as other files created by IDEs (Eclipse, 
> Intellij and NetBeans), among other file extensions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2557) Update gitignore to account for other file extensions

[Edward Ribeiro (JIRA)]

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

Edward Ribeiro updated ZOOKEEPER-2557:
--
Labels: easyfix  (was: )

> Update gitignore to account for other file extensions
> -
>
> Key: ZOOKEEPER-2557
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2557
> Project: ZooKeeper
>  Issue Type: Improvement
>Affects Versions: 3.4.8
>Reporter: Edward Ribeiro
>Assignee: Edward Ribeiro
>Priority: Trivial
>  Labels: easyfix
> Attachments: ZOOKEEPER-2557.patch
>
>
> We are in the process of moving from subversion to git, but I have seen that 
> the current ZK's {{gitignore}} doesn't account for many spurious types of 
> files (e.g., *.swp, *.tmp) as well as other files created by IDEs (Eclipse, 
> Intellij and NetBeans), among other file extensions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2557) Update gitignore to account for other file extensions

[Edward Ribeiro (JIRA)]

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

Edward Ribeiro updated ZOOKEEPER-2557:
--
Labels: easyfix  (was: )

> Update gitignore to account for other file extensions
> -
>
> Key: ZOOKEEPER-2557
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2557
> Project: ZooKeeper
>  Issue Type: Improvement
>Affects Versions: 3.4.8
>Reporter: Edward Ribeiro
>Assignee: Edward Ribeiro
>Priority: Trivial
>  Labels: easyfix
> Attachments: ZOOKEEPER-2557.patch
>
>
> We are in the process of moving from subversion to git, but I have seen that 
> the current ZK's {{gitignore}} doesn't account for many spurious types of 
> files (e.g., *.swp, *.tmp) as well as other files created by IDEs (Eclipse, 
> Intellij and NetBeans), among other file extensions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch34_jdk7 - Build # 1214 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/1214/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 185505 lines...]
[junit] 2016-09-06 19:42:46,223 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2016-09-06 19:42:46,223 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-09-06 19:42:46,224 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-09-06 19:42:46,225 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2016-09-06 19:42:46,225 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-09-06 19:42:46,225 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-09-06 19:42:46,226 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-09-06 19:42:46,226 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/branch-3.4/build/test/tmp/test7015310737559744914.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/branch-3.4/build/test/tmp/test7015310737559744914.junit.dir/version-2
[junit] 2016-09-06 19:42:46,230 [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] 2016-09-06 19:42:46,230 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-09-06 19:42:46,231 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:44237
[junit] 2016-09-06 19:42:46,231 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:44237
[junit] 2016-09-06 19:42:46,232 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-09-06 19:42:46,232 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:44237 (no session established for client)
[junit] 2016-09-06 19:42:46,233 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-09-06 19:42:46,235 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-09-06 19:42:46,235 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-09-06 19:42:46,235 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-09-06 19:42:46,236 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-09-06 19:42:46,236 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 32616
[junit] 2016-09-06 19:42:46,237 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-09-06 19:42:46,237 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-09-06 19:42:46,237 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2016-09-06 19:42:46,306 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x1570106333c closed
[junit] 2016-09-06 19:42:46,306 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2016-09-06 19:42:46,306 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-09-06 19:42:46,306 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x1570106333c
[junit] 2016-09-06 19:42:46,307 [myid:] - INFO  [main:ZooKeeperServer@497] 
- shutting down
[junit] 2016-09-06 19:42:46,307 [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] 2016-09-06 19:42:46,307 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-09-06 19:42:46,307 [myid:] - INFO  
[main:PrepRequestProcessor@765] - Shutting down
[junit] 2016-09-06 19:42:46,307 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2016-09-06 19:42:46,307 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-09-06 19:42:46,308 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2

ZooKeeper_branch34_solaris - Build # 1281 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_solaris/1281/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 170158 lines...]
[junit] 2016-09-06 19:10:04,734 [myid:] - INFO  [main:ZooKeeperServer@497] 
- shutting down
[junit] 2016-09-06 19:10:04,734 [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] 2016-09-06 19:10:04,735 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-09-06 19:10:04,735 [myid:] - INFO  
[main:PrepRequestProcessor@765] - Shutting down
[junit] 2016-09-06 19:10:04,735 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2016-09-06 19:10:04,735 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-09-06 19:10:04,735 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2016-09-06 19:10:04,735 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2016-09-06 19:10:04,736 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-09-06 19:10:04,736 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-09-06 19:10:04,737 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2016-09-06 19:10:04,738 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-09-06 19:10:04,738 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-09-06 19:10:04,738 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-09-06 19:10:04,739 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test2327481011409407375.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test2327481011409407375.junit.dir/version-2
[junit] 2016-09-06 19:10:04,743 [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] 2016-09-06 19:10:04,743 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-09-06 19:10:04,744 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:44156
[junit] 2016-09-06 19:10:04,744 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:44156
[junit] 2016-09-06 19:10:04,744 [myid:] - INFO  
[Thread-5:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-09-06 19:10:04,747 [myid:] - INFO  
[Thread-5:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:44156 (no session established for client)
[junit] 2016-09-06 19:10:04,747 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-09-06 19:10:04,748 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-09-06 19:10:04,749 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-09-06 19:10:04,749 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-09-06 19:10:04,749 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-09-06 19:10:04,749 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 9208
[junit] 2016-09-06 19:10:04,750 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-09-06 19:10:04,750 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-09-06 19:10:04,750 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2016-09-06 19:10:04,812 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15700e84370 closed
[junit] 2016-09-06 19:10:04,813 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2016-09-06 19:10:04,813 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15700e84370
[junit] 2016-09-06 19:10:04,814 [myid:] - INFO  [main:ZooKeeperServer@497] 
- shutting down
[junit] 2016-09-06 19:10:04,814

[jira] [Commented] (ZOOKEEPER-2554) reconfig can not add new server as observer

[Arshad Mohammad (JIRA)]

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

Arshad Mohammad commented on ZOOKEEPER-2554:


It is fine. Thanks [~shralex].

> reconfig can not add new server as observer
> ---
>
> Key: ZOOKEEPER-2554
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2554
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.0, 3.5.1, 3.5.2
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Critical
> Attachments: ReconfigObserverTest.java, ZOOKEEPER-2554-01.patch
>
>
> Try to add new observer server using reconfig API, server gets added as 
> participant.
> STEPS:
> # create 3 node cluster.
> {code}
> server.0=127.0.0.1:11223:11224:participant;127.0.0.1:11222
> server.1=127.0.0.1:11226:11227:participant;127.0.0.1:11225
> server.2=127.0.0.1:11229:11230:participant;127.0.0.1:11228
> {code}
> # Suppose the 2 is the leader in the above cluster. Configure the new server 
> as
> {code}
> server.2=127.0.0.1:11229:11230:participant;127.0.0.1:11228
> server.3=127.0.0.1:11232:11233:observer;127.0.0.1:11231
> {code}
> # Connect to 1 and execute the reconfig command
> {code}
> zkClient.reconfig("server.3=127.0.0.1:11232:11233:observer;127.0.0.1:11231", 
> null, null, -1, null, null);
> {code}
> # Verify sever 3. It was supposed to run as observer but it is running as 
> participant



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2502) Flaky Test: org.apache.zookeeper.server.quorum.CnxManagerTest.testCnxFromFutureVersion

[Michael Han (JIRA)]

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

Michael Han commented on ZOOKEEPER-2502:


Thanks Pat for reviewing and committing the patch!

> Flaky Test: 
> org.apache.zookeeper.server.quorum.CnxManagerTest.testCnxFromFutureVersion
> --
>
> Key: ZOOKEEPER-2502
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2502
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-test
> Fix For: 3.4.10
>
> Attachments: ZOOKEEPER-2502.patch, ZOOKEEPER-2502.patch
>
>
> {noformat}
> Error Message
> Broken pipe
> Stacktrace
> java.io.IOException: Broken pipe
>   at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
>   at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
>   at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
>   at sun.nio.ch.IOUtil.write(IOUtil.java:65)
>   at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:466)
>   at java.nio.channels.Channels.writeFullyImpl(Channels.java:78)
>   at java.nio.channels.Channels.writeFully(Channels.java:98)
>   at java.nio.channels.Channels.access$000(Channels.java:61)
>   at java.nio.channels.Channels$1.write(Channels.java:174)
>   at java.io.OutputStream.write(OutputStream.java:75)
>   at java.nio.channels.Channels$1.write(Channels.java:155)
>   at java.io.DataOutputStream.writeInt(DataOutputStream.java:198)
>   at 
> org.apache.zookeeper.server.quorum.CnxManagerTest.testCnxFromFutureVersion(CnxManagerTest.java:318)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:55)
> Standard Output
> 2016-07-12 22:34:46,623 [myid:] - INFO  [main:ZKTestCase$1@50] - STARTING 
> testCnxFromFutureVersion
> 2016-07-12 22:34:46,627 [myid:] - INFO  [main:PortAssignment@32] - assigning 
> port 11221
> 2016-07-12 22:34:46,630 [myid:] - INFO  [main:PortAssignment@32] - assigning 
> port 11222
> 2016-07-12 22:34:46,631 [myid:] - INFO  [main:PortAssignment@32] - assigning 
> port 11223
> 2016-07-12 22:34:46,643 [myid:] - INFO  [main:QuorumPeer$QuorumServer@149] - 
> Resolved hostname: 0.0.0.0 to address: /0.0.0.0
> 2016-07-12 22:34:46,658 [myid:] - INFO  [main:PortAssignment@32] - assigning 
> port 11224
> 2016-07-12 22:34:46,658 [myid:] - INFO  [main:PortAssignment@32] - assigning 
> port 11225
> 2016-07-12 22:34:46,659 [myid:] - INFO  [main:PortAssignment@32] - assigning 
> port 11226
> 2016-07-12 22:34:46,659 [myid:] - INFO  [main:QuorumPeer$QuorumServer@149] - 
> Resolved hostname: 0.0.0.0 to address: /0.0.0.0
> 2016-07-12 22:34:46,659 [myid:] - INFO  [main:PortAssignment@32] - assigning 
> port 11227
> 2016-07-12 22:34:46,659 [myid:] - INFO  [main:PortAssignment@32] - assigning 
> port 11228
> 2016-07-12 22:34:46,659 [myid:] - INFO  [main:PortAssignment@32] - assigning 
> port 11229
> 2016-07-12 22:34:46,660 [myid:] - INFO  [main:QuorumPeer$QuorumServer@149] - 
> Resolved hostname: 0.0.0.0 to address: /0.0.0.0
> 2016-07-12 22:34:46,660 [myid:] - INFO  
> [main:JUnit4ZKTestRunner$LoggedInvokeMethod@53] - RUNNING TEST METHOD 
> testCnxFromFutureVersion
> 2016-07-12 22:34:46,672 [myid:] - INFO  [main:NIOServerCnxnFactory@89] - 
> binding to port 0.0.0.0/0.0.0.0:11225
> 2016-07-12 22:34:46,692 [myid:] - INFO  [main:CnxManagerTest@301] - Election 
> port: 11226
> 2016-07-12 22:34:46,692 [myid:] - INFO  
> [ListenerThread:QuorumCnxManager$Listener@534] - My election bind port: 
> /0.0.0.0:11226
> 2016-07-12 22:34:47,696 [myid:] - INFO  
> [/0.0.0.0:11226:QuorumCnxManager$Listener@541] - Received connection request 
> /140.211.11.27:48724
> 2016-07-12 22:34:49,700 [myid:] - WARN  [/0.0.0.0:11226:QuorumCnxManager@274] 
> - Exception reading or writing challenge: java.net.SocketTimeoutException: 
> Read timed out
> 2016-07-12 22:34:52,700 [myid:] - INFO  
> [main:JUnit4ZKTestRunner$LoggedInvokeMethod@74] - TEST METHOD FAILED 
> testCnxFromFutureVersion
> java.io.IOException: Broken pipe
>   at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
>   at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
>   at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
>   at sun.nio.ch.IOUtil.write(IOUtil.java:65)
>   at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:466)
>   at java.nio.channels.Channels.writeFullyImpl(Channels.java:78)
>   at java.nio.channels.Channels.writeFully(Channels.java:98)
>   at java.nio.channels.Channels.access$000(Channels.java:61)
>   at java.nio.channels.Channels$1.write(Channels.java:174)
>   at java.i

[jira] [Commented] (ZOOKEEPER-2554) reconfig can not add new server as observer

[Alexander Shraer (JIRA)]

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

Alexander Shraer commented on ZOOKEEPER-2554:
-

Marking this as 'not a problem' for now. Please reopen if you still disagree.

> reconfig can not add new server as observer
> ---
>
> Key: ZOOKEEPER-2554
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2554
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.0, 3.5.1, 3.5.2
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Critical
> Attachments: ReconfigObserverTest.java, ZOOKEEPER-2554-01.patch
>
>
> Try to add new observer server using reconfig API, server gets added as 
> participant.
> STEPS:
> # create 3 node cluster.
> {code}
> server.0=127.0.0.1:11223:11224:participant;127.0.0.1:11222
> server.1=127.0.0.1:11226:11227:participant;127.0.0.1:11225
> server.2=127.0.0.1:11229:11230:participant;127.0.0.1:11228
> {code}
> # Suppose the 2 is the leader in the above cluster. Configure the new server 
> as
> {code}
> server.2=127.0.0.1:11229:11230:participant;127.0.0.1:11228
> server.3=127.0.0.1:11232:11233:observer;127.0.0.1:11231
> {code}
> # Connect to 1 and execute the reconfig command
> {code}
> zkClient.reconfig("server.3=127.0.0.1:11232:11233:observer;127.0.0.1:11231", 
> null, null, -1, null, null);
> {code}
> # Verify sever 3. It was supposed to run as observer but it is running as 
> participant



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ZOOKEEPER-2554) reconfig can not add new server as observer

[Alexander Shraer (JIRA)]

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

Alexander Shraer resolved ZOOKEEPER-2554.
-
Resolution: Not A Problem

> reconfig can not add new server as observer
> ---
>
> Key: ZOOKEEPER-2554
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2554
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.0, 3.5.1, 3.5.2
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Critical
> Attachments: ReconfigObserverTest.java, ZOOKEEPER-2554-01.patch
>
>
> Try to add new observer server using reconfig API, server gets added as 
> participant.
> STEPS:
> # create 3 node cluster.
> {code}
> server.0=127.0.0.1:11223:11224:participant;127.0.0.1:11222
> server.1=127.0.0.1:11226:11227:participant;127.0.0.1:11225
> server.2=127.0.0.1:11229:11230:participant;127.0.0.1:11228
> {code}
> # Suppose the 2 is the leader in the above cluster. Configure the new server 
> as
> {code}
> server.2=127.0.0.1:11229:11230:participant;127.0.0.1:11228
> server.3=127.0.0.1:11232:11233:observer;127.0.0.1:11231
> {code}
> # Connect to 1 and execute the reconfig command
> {code}
> zkClient.reconfig("server.3=127.0.0.1:11232:11233:observer;127.0.0.1:11231", 
> null, null, -1, null, null);
> {code}
> # Verify sever 3. It was supposed to run as observer but it is running as 
> participant



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [ANNOUNCE] Apache ZooKeeper 3.4.9

[Chris Nauroth]

Thanks very much, Rakesh!

--Chris Nauroth

On 9/3/16, 9:32 PM, "Rakesh Radhakrishnan"  wrote:

The Apache ZooKeeper team is proud to announce Apache ZooKeeper version
3.4.9.

ZooKeeper is a high-performance coordination service for distributed
applications. It exposes common services - such as naming,
configuration management, synchronization, and group services - in a
simple interface so you don't have to write them from scratch. You can
use it off-the-shelf to implement consensus, group management, leader
election, and presence protocols. And you can build on it for your
own, specific needs.

For ZooKeeper release details and downloads, visit:
http://zookeeper.apache.org/releases.html

ZooKeeper 3.4.9 Release Notes are at:
http://zookeeper.apache.org/doc/r3.4.9/releasenotes.html

We would like to thank the contributors that made the release possible.

Regards,
The ZooKeeper Team

ZooKeeper_branch35_solaris - Build # 236 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_solaris/236/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 100205 lines...]
[junit] 2016-09-06 16:51:27,253 [myid:1] - INFO  
[QuorumPeer[myid=1](plain=/127.0.0.1:11300)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id1]
[junit] 2016-09-06 16:51:27,254 [myid:1] - INFO  
[QuorumPeer[myid=1](plain=/127.0.0.1:11300)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id1,name1=replica.1]
[junit] 2016-09-06 16:51:27,254 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/127.0.0.1:11303)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id2,name1=replica.2,name2=Follower,name3=InMemoryDataTree]
[junit] 2016-09-06 16:51:27,254 [myid:1] - INFO  
[QuorumPeer[myid=1](plain=/127.0.0.1:11300)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id1,name1=replica.0]
[junit] 2016-09-06 16:51:27,254 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/127.0.0.1:11303)(secure=disabled):SyncRequestProcessor@191]
 - Shutting down
[junit] 2016-09-06 16:51:27,254 [myid:1] - INFO  
[QuorumPeer[myid=1](plain=/127.0.0.1:11300)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id1,name1=replica.2]
[junit] 2016-09-06 16:51:27,254 [myid:2] - INFO  
[SyncThread:2:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2016-09-06 16:51:27,255 [myid:2] - WARN  
[QuorumPeer[myid=2](plain=/127.0.0.1:11303)(secure=disabled):QuorumPeer@1158] - 
PeerState set to LOOKING
[junit] 2016-09-06 16:51:27,255 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/127.0.0.1:11303)(secure=disabled):QuorumPeer@1033] - 
LOOKING
[junit] 2016-09-06 16:51:27,351 [myid:] - INFO  [main:ZooKeeper@1313] - 
Session: 0x1237d64c79e closed
[junit] 2016-09-06 16:51:27,351 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1237d64c79e
[junit] 2016-09-06 16:51:27,351 [myid:] - INFO  [main:QuorumBase@394] - 
Shutting down quorum peer 
QuorumPeer[myid=2](plain=/127.0.0.1:11303)(secure=disabled)
[junit] 2016-09-06 16:51:27,352 [myid:2] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-09-06 16:51:27,354 [myid:2] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-09-06 16:51:27,354 [myid:2] - INFO  
[NIOServerCxnFactory.AcceptThread:localhost/127.0.0.1:11303:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2016-09-06 16:51:27,355 [myid:2] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-09-06 16:51:27,357 [myid:2] - INFO  
[localhost/127.0.0.1:11305:QuorumCnxManager$Listener@659] - Leaving listener
[junit] 2016-09-06 16:51:27,357 [myid:] - INFO  [main:QuorumBase@398] - 
Shutting down leader election 
QuorumPeer[myid=2](plain=/127.0.0.1:11303)(secure=disabled)
[junit] 2016-09-06 16:51:27,357 [myid:] - INFO  [main:QuorumBase@403] - 
Waiting for QuorumPeer[myid=2](plain=/127.0.0.1:11303)(secure=disabled) to exit 
thread
[junit] 2016-09-06 16:51:27,721 [myid:1] - INFO  
[WorkerReceiver[myid=1]:FastLeaderElection$Messenger$WorkerReceiver@440] - 
WorkerReceiver is down
[junit] 2016-09-06 16:51:27,721 [myid:0] - INFO  
[WorkerReceiver[myid=0]:FastLeaderElection$Messenger$WorkerReceiver@440] - 
WorkerReceiver is down
[junit] 2016-09-06 16:51:27,721 [myid:2] - INFO  
[WorkerSender[myid=2]:FastLeaderElection$Messenger$WorkerSender@470] - 
WorkerSender is down
[junit] 2016-09-06 16:51:27,721 [myid:2] - INFO  
[WorkerReceiver[myid=2]:FastLeaderElection$Messenger$WorkerReceiver@440] - 
WorkerReceiver is down
[junit] 2016-09-06 16:51:27,721 [myid:0] - INFO  
[WorkerSender[myid=0]:FastLeaderElection$Messenger$WorkerSender@470] - 
WorkerSender is down
[junit] 2016-09-06 16:51:27,721 [myid:1] - INFO  
[WorkerSender[myid=1]:FastLeaderElection$Messenger$WorkerSender@470] - 
WorkerSender is down
[junit] 2016-09-06 16:51:28,261 [myid:1] - INFO  
[SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop!
[junit] 2016-09-06 16:51:28,315 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/127.0.0.1:11303)(secure=disabled):FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test5501137576673997156.junit.dir/data/version-2/snapshot.1
[junit] 2016-09-06 16:51:28,382

[jira] [Updated] (ZOOKEEPER-2557) Update gitignore to account for other file extensions

[Edward Ribeiro (JIRA)]

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

Edward Ribeiro updated ZOOKEEPER-2557:
--
Affects Version/s: 3.4.8

> Update gitignore to account for other file extensions
> -
>
> Key: ZOOKEEPER-2557
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2557
> Project: ZooKeeper
>  Issue Type: Improvement
>Affects Versions: 3.4.8
>Reporter: Edward Ribeiro
>Assignee: Edward Ribeiro
>Priority: Trivial
> Attachments: ZOOKEEPER-2557.patch
>
>
> We are in the process of moving from subversion to git, but I have seen that 
> the current ZK's {{gitignore}} doesn't account for many spurious types of 
> files (e.g., *.swp, *.tmp) as well as other files created by IDEs (Eclipse, 
> Intellij and NetBeans), among other file extensions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2557) Update gitignore to account for other file extensions

[Edward Ribeiro (JIRA)]

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

Edward Ribeiro updated ZOOKEEPER-2557:
--
Attachment: ZOOKEEPER-2557.patch

Besides some well known extensions (.swp, .bak), I have included more files 
extensions from https://github.com/github/gitignore. My only concern here is if 
 .class, .ear, .war and .jar files should be included or not in the gitignore 
file.

> Update gitignore to account for other file extensions
> -
>
> Key: ZOOKEEPER-2557
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2557
> Project: ZooKeeper
>  Issue Type: Improvement
>Reporter: Edward Ribeiro
>Assignee: Edward Ribeiro
>Priority: Trivial
> Attachments: ZOOKEEPER-2557.patch
>
>
> We are in the process of moving from subversion to git, but I have seen that 
> the current ZK's {{gitignore}} doesn't account for many spurious types of 
> files (e.g., *.swp, *.tmp) as well as other files created by IDEs (Eclipse, 
> Intellij and NetBeans), among other file extensions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (ZOOKEEPER-2557) Update gitignore to account for other file extensions

[Edward Ribeiro (JIRA)]

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

Edward Ribeiro reassigned ZOOKEEPER-2557:
-

Assignee: Edward Ribeiro

> Update gitignore to account for other file extensions
> -
>
> Key: ZOOKEEPER-2557
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2557
> Project: ZooKeeper
>  Issue Type: Improvement
>Reporter: Edward Ribeiro
>Assignee: Edward Ribeiro
>Priority: Trivial
>
> We are in the process of moving from subversion to git, but I have seen that 
> the current ZK's {{gitignore}} doesn't account for many spurious types of 
> files (e.g., *.swp, *.tmp) as well as other files created by IDEs (Eclipse, 
> Intellij and NetBeans), among other file extensions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ZOOKEEPER-2557) Update gitignore to account for other file extensions

[Edward Ribeiro (JIRA)]

Edward Ribeiro created ZOOKEEPER-2557:
-

 Summary: Update gitignore to account for other file extensions
 Key: ZOOKEEPER-2557
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2557
 Project: ZooKeeper
  Issue Type: Improvement
Reporter: Edward Ribeiro
Priority: Trivial


We are in the process of moving from subversion to git, but I have seen that 
the current ZK's {{gitignore}} doesn't account for many spurious types of files 
(e.g., *.swp, *.tmp) as well as other files created by IDEs (Eclipse, Intellij 
and NetBeans), among other file extensions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (ZOOKEEPER-2552) Revisit release note doc and remove the items which are not related to the released version

[Edward Ribeiro (JIRA)]

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

Edward Ribeiro reassigned ZOOKEEPER-2552:
-

Assignee: Edward Ribeiro  (was: Rakesh R)

> Revisit release note doc and remove the items which are not related to the 
> released version
> ---
>
> Key: ZOOKEEPER-2552
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2552
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Rakesh R
>Assignee: Edward Ribeiro
> Fix For: 3.4.10
>
> Attachments: closed.py
>
>
> Couple of issues listed on http://zookeeper.apache.org/
> doc/r3.4.9/releasenotes.html that are either 'Open' or 'Patch available'. For 
> example, issues were wrongly marked as "3.4.8" fix version in jira and has 
> caused the trouble.
> This jira to cross check all the jira issues present in the release note and 
> check the correctness.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2552) Revisit release note doc and remove the items which are not related to the released version

[Edward Ribeiro (JIRA)]

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

Edward Ribeiro commented on ZOOKEEPER-2552:
---

Thanks for suggestion [~rakeshr]. It's highly appreciated, I will take note. 
Maybe we can add this piece of info to the docs at 
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute ?

Excuse me for the dumb question, but I thought it would be just a matter of 
--alter-- (removing) the fix version of the affected versions. What files would 
this patch touch? I am okay with preparing a patch for it, btw.

> Revisit release note doc and remove the items which are not related to the 
> released version
> ---
>
> Key: ZOOKEEPER-2552
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2552
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.10
>
> Attachments: closed.py
>
>
> Couple of issues listed on http://zookeeper.apache.org/
> doc/r3.4.9/releasenotes.html that are either 'Open' or 'Patch available'. For 
> example, issues were wrongly marked as "3.4.8" fix version in jira and has 
> caused the trouble.
> This jira to cross check all the jira issues present in the release note and 
> check the correctness.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Issue Comment Deleted] (ZOOKEEPER-2552) Revisit release note doc and remove the items which are not related to the released version

[Edward Ribeiro (JIRA)]

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

Edward Ribeiro updated ZOOKEEPER-2552:
--
Comment: was deleted

(was: Thanks for suggestion [~rakeshr]. It's highly appreciated, I will take 
note. Maybe we can add this piece of info to the docs at 
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute ?

Excuse me for the dumb question, but I thought it would be just a matter of 
--alter-- (removing) the fix version of the affected versions. What files would 
this patch touch? I am okay with preparing a patch for it, btw.)

> Revisit release note doc and remove the items which are not related to the 
> released version
> ---
>
> Key: ZOOKEEPER-2552
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2552
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.10
>
> Attachments: closed.py
>
>
> Couple of issues listed on http://zookeeper.apache.org/
> doc/r3.4.9/releasenotes.html that are either 'Open' or 'Patch available'. For 
> example, issues were wrongly marked as "3.4.8" fix version in jira and has 
> caused the trouble.
> This jira to cross check all the jira issues present in the release note and 
> check the correctness.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ZOOKEEPER-2552) Revisit release note doc and remove the items which are not related to the released version

[Edward Ribeiro (JIRA)]

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

Edward Ribeiro edited comment on ZOOKEEPER-2552 at 9/6/16 3:41 PM:
---

Thanks for suggestion [~rakeshr]. It's highly appreciated, I will take note. 
Maybe we can add this piece of info to the docs at 
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute ?

Excuse me for the dumb question, but I thought it would be just a matter of 
--alter-- (removing) the fix version of the affected JIRAs. What files would 
this patch touch? I am okay with preparing a patch for it, btw.


was (Author: eribeiro):
Thanks for suggestion [~rakeshr]. It's highly appreciated, I will take note. 
Maybe we can add this piece of info to the docs at 
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute ?

Excuse me for the dumb question, but I thought it would be just a matter of 
--alter-- (removing) the fix version of the affected versions. What files would 
this patch touch? I am okay with preparing a patch for it, btw.

> Revisit release note doc and remove the items which are not related to the 
> released version
> ---
>
> Key: ZOOKEEPER-2552
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2552
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.10
>
> Attachments: closed.py
>
>
> Couple of issues listed on http://zookeeper.apache.org/
> doc/r3.4.9/releasenotes.html that are either 'Open' or 'Patch available'. For 
> example, issues were wrongly marked as "3.4.8" fix version in jira and has 
> caused the trouble.
> This jira to cross check all the jira issues present in the release note and 
> check the correctness.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2552) Revisit release note doc and remove the items which are not related to the released version

[Edward Ribeiro (JIRA)]

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

Edward Ribeiro commented on ZOOKEEPER-2552:
---

Thanks for suggestion [~rakeshr]. It's highly appreciated, I will take note. 
Maybe we can add this piece of info to the docs at 
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute ?

Excuse me for the dumb question, but I thought it would be just a matter of 
--alter-- (removing) the fix version of the affected versions. What files would 
this patch touch? I am okay with preparing a patch for it, btw.

> Revisit release note doc and remove the items which are not related to the 
> released version
> ---
>
> Key: ZOOKEEPER-2552
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2552
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.10
>
> Attachments: closed.py
>
>
> Couple of issues listed on http://zookeeper.apache.org/
> doc/r3.4.9/releasenotes.html that are either 'Open' or 'Patch available'. For 
> example, issues were wrongly marked as "3.4.8" fix version in jira and has 
> caused the trouble.
> This jira to cross check all the jira issues present in the release note and 
> check the correctness.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2552) Revisit release note doc and remove the items which are not related to the released version

[Rakesh R (JIRA)]

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

Rakesh R commented on ZOOKEEPER-2552:
-

Thanks again [~eribeiro] for identifying all these. Would you be interested in 
preparing a patch? if yes, please assign the the issue to yourself and I will 
help in reviews.

Also, just a suggestion. While creating the jira, probably contributor can mark 
the affected version(s) and later the reviewer will mark the fix version(s). I 
feel that would avoid similar problems in future.

> Revisit release note doc and remove the items which are not related to the 
> released version
> ---
>
> Key: ZOOKEEPER-2552
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2552
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.10
>
> Attachments: closed.py
>
>
> Couple of issues listed on http://zookeeper.apache.org/
> doc/r3.4.9/releasenotes.html that are either 'Open' or 'Patch available'. For 
> example, issues were wrongly marked as "3.4.8" fix version in jira and has 
> caused the trouble.
> This jira to cross check all the jira issues present in the release note and 
> check the correctness.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ZOOKEEPER-2552) Revisit release note doc and remove the items which are not related to the released version

[Edward Ribeiro (JIRA)]

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

Edward Ribeiro edited comment on ZOOKEEPER-2552 at 9/6/16 2:01 PM:
---

I added a {{sleep}} time between url fetches so that I *hopefully* don't 
flood/DoS the JIRA server.

*UPDATE:* running my naive script, these are the issues it identified (had to 
restart at least three times because connection was reset by peer, probably 
some anti-DoS feature so I included a snippet to bypass the URLs already 
visited). 

Patch Available  https://issues.apache.org/jira/browse/ZOOKEEPER-2391
Patch Available  https://issues.apache.org/jira/browse/ZOOKEEPER-2468
Open  https://issues.apache.org/jira/browse/ZOOKEEPER-2512
Open  https://issues.apache.org/jira/browse/ZOOKEEPER-2236
Open  https://issues.apache.org/jira/browse/ZOOKEEPER-2327
Open  https://issues.apache.org/jira/browse/ZOOKEEPER-2313

*UPDATE 2:* pushed my issues (ZOOKEEPER-2512 & ZOOKEEPER-2313) to 3.5.3. ;)



was (Author: eribeiro):
I added a {{sleep}} time between url fetches so that I *hopefully* don't 
flood/DoS the JIRA server.

*UPDATE:* running my naive script, these are the issues it identified (had to 
restart at least three times because connection was reset by peer, probably 
some anti-DoS feature so I included a snippet to bypass the URLs already 
visited). 

Patch Available  https://issues.apache.org/jira/browse/ZOOKEEPER-2391
Patch Available  https://issues.apache.org/jira/browse/ZOOKEEPER-2468
Open  https://issues.apache.org/jira/browse/ZOOKEEPER-2512
Open  https://issues.apache.org/jira/browse/ZOOKEEPER-2236
Open  https://issues.apache.org/jira/browse/ZOOKEEPER-2327
Open  https://issues.apache.org/jira/browse/ZOOKEEPER-2313


> Revisit release note doc and remove the items which are not related to the 
> released version
> ---
>
> Key: ZOOKEEPER-2552
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2552
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.10
>
> Attachments: closed.py
>
>
> Couple of issues listed on http://zookeeper.apache.org/
> doc/r3.4.9/releasenotes.html that are either 'Open' or 'Patch available'. For 
> example, issues were wrongly marked as "3.4.8" fix version in jira and has 
> caused the trouble.
> This jira to cross check all the jira issues present in the release note and 
> check the correctness.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch34_solaris - Build # 1280 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_solaris/1280/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 167821 lines...]
[junit] 2016-09-06 13:55:52,983 [myid:] - INFO  [main:ZooKeeperServer@497] 
- shutting down
[junit] 2016-09-06 13:55:52,983 [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] 2016-09-06 13:55:52,983 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-09-06 13:55:52,983 [myid:] - INFO  
[main:PrepRequestProcessor@765] - Shutting down
[junit] 2016-09-06 13:55:52,983 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2016-09-06 13:55:52,983 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-09-06 13:55:52,984 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2016-09-06 13:55:52,984 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2016-09-06 13:55:52,984 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-09-06 13:55:52,985 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-09-06 13:55:52,985 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2016-09-06 13:55:52,986 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-09-06 13:55:52,986 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-09-06 13:55:52,986 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-09-06 13:55:52,986 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test4597129345131500348.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test4597129345131500348.junit.dir/version-2
[junit] 2016-09-06 13:55:52,989 [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] 2016-09-06 13:55:52,989 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-09-06 13:55:52,989 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:33018
[junit] 2016-09-06 13:55:52,990 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:33018
[junit] 2016-09-06 13:55:52,990 [myid:] - INFO  
[Thread-5:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-09-06 13:55:52,990 [myid:] - INFO  
[Thread-5:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:33018 (no session established for client)
[junit] 2016-09-06 13:55:52,990 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-09-06 13:55:52,992 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-09-06 13:55:52,992 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-09-06 13:55:52,992 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-09-06 13:55:52,992 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-09-06 13:55:52,992 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 8953
[junit] 2016-09-06 13:55:52,992 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-09-06 13:55:52,993 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-09-06 13:55:52,993 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2016-09-06 13:55:53,072 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x156ffc89d5c closed
[junit] 2016-09-06 13:55:53,072 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x156ffc89d5c
[junit] 2016-09-06 13:55:53,072 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2016-09-06 13:55:53,073 [myid:] - INFO  [main:ZooKeeperServer@497] 
- shutting down
[junit] 2016-09-06 13:55:53,073

[jira] [Updated] (ZOOKEEPER-2512) Allow Jetty dependency to use HTTPS and Basic Auth

[Edward Ribeiro (JIRA)]

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

Edward Ribeiro updated ZOOKEEPER-2512:
--
Fix Version/s: (was: 3.5.1)
   (was: 3.4.8)
   (was: 3.5.0)
   3.5.3

> Allow Jetty dependency to use HTTPS and Basic Auth
> --
>
> Key: ZOOKEEPER-2512
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2512
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.5.2
>Reporter: Edward Ribeiro
>Assignee: Edward Ribeiro
>  Labels: security
> Fix For: 3.5.3
>
>
> If ZOOKEEPER-2489 gets committed then it would be nice to allow more flexible 
> configuration of https and basic authentication to JettyAdminServer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2280) NettyServerCnxnFactory doesn't honor maxClientCnxns param

[Edward Ribeiro (JIRA)]

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

Edward Ribeiro updated ZOOKEEPER-2280:
--
Fix Version/s: (was: 3.5.1)
   3.5.3

> NettyServerCnxnFactory doesn't honor maxClientCnxns param
> -
>
> Key: ZOOKEEPER-2280
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2280
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.6, 3.5.0, 3.5.1
>Reporter: Edward Ribeiro
>Assignee: Edward Ribeiro
> Fix For: 3.5.3
>
> Attachments: ZOOKEEPER-2280.2.patch, ZOOKEEPER-2280.patch
>
>
> Even though NettyServerCnxnFactory has maxClientCnxns (default to 60) it 
> doesn't enforce this limit in the code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2313) Refactor ZooKeeperServerBean and its subclasses (LeaderBean, ObserverBean, FollowerBean)

[Edward Ribeiro (JIRA)]

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

Edward Ribeiro updated ZOOKEEPER-2313:
--
Fix Version/s: (was: 3.4.6)
   3.5.3

> Refactor ZooKeeperServerBean and its subclasses (LeaderBean, ObserverBean, 
> FollowerBean)
> 
>
> Key: ZOOKEEPER-2313
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2313
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.4.6
>Reporter: Edward Ribeiro
>Assignee: Edward Ribeiro
>Priority: Minor
> Fix For: 3.5.3
>
>
> Following the work on ZOOKEEPER-2142, the goal of this ticket is to add a new 
> constructor to ZooKeeperServerBean to pass the name as the parameter, so 
> classes that extend from ZooKeeperServerBean shouldn't need to implement 
> getName() method. Also, ObserverBean seems to be in the wrong package, it 
> should be under server.quorum rather than just server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch35_jdk8 - Build # 218 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/218/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 419288 lines...]
[junit] 2016-09-06 12:19:36,476 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:14159
[junit] 2016-09-06 12:19:36,480 [myid:] - INFO  [main:ZooKeeperServer@529] 
- shutting down
[junit] 2016-09-06 12:19:36,480 [myid:] - ERROR [main:ZooKeeperServer@501] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-09-06 12:19:36,480 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2016-09-06 12:19:36,480 [myid:] - INFO  
[main:PrepRequestProcessor@965] - Shutting down
[junit] 2016-09-06 12:19:36,480 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2016-09-06 12:19:36,481 [myid:] - INFO  [ProcessThread(sid:0 
cport:14159)::PrepRequestProcessor@154] - PrepRequestProcessor exited loop!
[junit] 2016-09-06 12:19:36,488 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2016-09-06 12:19:36,489 [myid:] - INFO  
[main:FinalRequestProcessor@479] - shutdown of request processor complete
[junit] 2016-09-06 12:19:36,490 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port14159,name1=InMemoryDataTree]
[junit] 2016-09-06 12:19:36,490 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port14159]
[junit] 2016-09-06 12:19:36,511 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 14159
[junit] 2016-09-06 12:19:36,511 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-09-06 12:19:36,530 [myid:] - INFO  [main:ClientBase@568] - 
fdcount after test is: 5212 at start it was 5212
[junit] 2016-09-06 12:19:36,531 [myid:] - INFO  [main:ZKTestCase$1@65] - 
SUCCEEDED testWatcherAutoResetWithLocal
[junit] 2016-09-06 12:19:36,531 [myid:] - INFO  [main:ZKTestCase$1@60] - 
FINISHED testWatcherAutoResetWithLocal
[junit] Tests run: 101, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
504.971 sec, Thread: 2, Class: org.apache.zookeeper.test.NettyNettySuiteTest
[junit] 2016-09-06 12:19:36,761 [myid:127.0.0.1:14036] - INFO  
[main-SendThread(127.0.0.1:14036):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:14036. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-09-06 12:19:36,762 [myid:] - INFO  [New I/O boss 
#9438:ClientCnxnSocketNetty$1@127] - future isn't success, cause: {}
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:14036
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[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] 2016-09-06 12:19:36,762 [myid:] - WARN  [New I/O boss 
#9438:ClientCnxnSocketNetty$ZKClientHandler@439] - Exception caught: [id: 
0x0b8922de] EXCEPTION: java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:14036
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:14036
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
 

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

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 433492 lines...]
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[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] 2016-09-06 12:07:19,075 [myid:] - INFO  [New I/O worker 
#8206:ClientCnxnSocketNetty$ZKClientHandler@384] - channel is disconnected: 
[id: 0x58c59226, /127.0.0.1:49334 :> 127.0.0.1/127.0.0.1:16681]
[junit] 2016-09-06 12:07:19,076 [myid:] - INFO  [New I/O worker 
#8206:ClientCnxnSocketNetty@208] - channel is told closing
[junit] 2016-09-06 12:07:19,076 [myid:127.0.0.1:16681] - INFO  
[main-SendThread(127.0.0.1:16681):ClientCnxn$SendThread@1231] - channel for 
sessionid 0x100a93074bf is lost, closing socket connection and attempting 
reconnect
[junit] 2016-09-06 12:07:19,132 [myid:127.0.0.1:16608] - INFO  
[main-SendThread(127.0.0.1:16608):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:16608. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-09-06 12:07:19,133 [myid:] - INFO  [New I/O boss 
#66:ClientCnxnSocketNetty$1@127] - future isn't success, cause: {}
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:16608
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[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] 2016-09-06 12:07:19,133 [myid:] - WARN  [New I/O boss 
#66:ClientCnxnSocketNetty$ZKClientHandler@439] - Exception caught: [id: 
0x8e3ee792] EXCEPTION: java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:16608
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:16608
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[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] 2016-09-06 12:07:19,134 [myid:] - INFO  [New I/O boss 
#66:ClientCnxnSocketNetty@208] - channel is told closing
[junit] 2016-09-06 12:07:19,134 [myid:127.0.0.1:16608] - INFO  
[main-SendThread(127.0.0.1:16608):ClientCnxn$SendThread@1231] - channel for 
sessionid 0x100a92c1637 is los

[jira] [Updated] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime

[Rakesh Kumar Singh (JIRA)]

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

Rakesh Kumar Singh updated ZOOKEEPER-2556:
--
Description: 
peerType remains as "observer" in zoo.cfg even though we change the node from 
observer to participant runtime

Steps to reproduce:-
1. Start zookeeper in cluster with one node as observer by configuring 
peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181
2. Start the cluster
3. start a client and change the node from observer to participant, the 
configuration related to peertype remained same though other things like 
clientport got from zoo.cfg

>reconfig -remove 2 -add 2=10.18.219.50:2888:3888:participant;2181

We should either remove this parameter or update with correct node type at run 
time

  was:
peerType remains as "observer" in zoo.cfg even though we change the node from 
observer to participant runtime

Steps to reproduce:-
1. Start zookeeper in cluster with one node as observer by configuring 
peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181
2. Start the cluster
3. start a client and change the node from observer to participant, the 
configuration related to peertype remained same though other things like 
clientport got from zoo.cfg

We should either remove this parameter or update with correct node type at run 
time


> peerType remains as "observer" in zoo.cfg even though we change the node from 
> observer to participant runtime
> -
>
> Key: ZOOKEEPER-2556
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2556
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.1
>Reporter: Rakesh Kumar Singh
>Priority: Minor
>
> peerType remains as "observer" in zoo.cfg even though we change the node from 
> observer to participant runtime
> Steps to reproduce:-
> 1. Start zookeeper in cluster with one node as observer by configuring 
> peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181
> 2. Start the cluster
> 3. start a client and change the node from observer to participant, the 
> configuration related to peertype remained same though other things like 
> clientport got from zoo.cfg
> >reconfig -remove 2 -add 2=10.18.219.50:2888:3888:participant;2181
> We should either remove this parameter or update with correct node type at 
> run time



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime

[Rakesh Kumar Singh (JIRA)]

Rakesh Kumar Singh created ZOOKEEPER-2556:
-

 Summary: peerType remains as "observer" in zoo.cfg even though we 
change the node from observer to participant runtime
 Key: ZOOKEEPER-2556
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2556
 Project: ZooKeeper
  Issue Type: Bug
  Components: server
Affects Versions: 3.5.1
Reporter: Rakesh Kumar Singh
Priority: Minor


peerType remains as "observer" in zoo.cfg even though we change the node from 
observer to participant runtime

Steps to reproduce:-
1. Start zookeeper in cluster with one node as observer by configuring 
peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181
2. Start the cluster
3. start a client and change the node from observer to participant, the 
configuration related to peertype remained same though other things like 
clientport got from zoo.cfg

We should either remove this parameter or update with correct node type at run 
time



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch35_openjdk7 - Build # 216 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/216/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 444508 lines...]
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2016-09-06 10:29:51,661 [myid:127.0.0.1:22066] - INFO  
[main-SendThread(127.0.0.1:22066):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:22066. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-09-06 10:29:51,662 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:/127.0.0.1:22066:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:57297
[junit] 2016-09-06 10:29:51,662 [myid:127.0.0.1:22066] - INFO  
[main-SendThread(127.0.0.1:22066):ClientCnxn$SendThread@948] - Socket 
connection established, initiating session, client: /127.0.0.1:57297, server: 
127.0.0.1/127.0.0.1:22066
[junit] 2016-09-06 10:29:51,662 [myid:] - WARN  
[NIOWorkerThread-8:NIOServerCnxn@369] - Exception causing close of session 0x0: 
ZooKeeperServer not running
[junit] 2016-09-06 10:29:51,663 [myid:] - INFO  
[NIOWorkerThread-8:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:57297 (no session established for client)
[junit] 2016-09-06 10:29:51,663 [myid:127.0.0.1:22066] - INFO  
[main-SendThread(127.0.0.1:22066):ClientCnxn$SendThread@1231] - Unable to read 
additional data from server sessionid 0x0, likely server has closed socket, 
closing socket connection and attempting reconnect
[junit] 2016-09-06 10:29:52,026 [myid:127.0.0.1:22045] - INFO  
[main-SendThread(127.0.0.1:22045):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:22045. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-09-06 10:29:52,026 [myid:127.0.0.1:22045] - WARN  
[main-SendThread(127.0.0.1:22045):ClientCnxn$SendThread@1235] - Session 
0x200917c18f5 for server 127.0.0.1/127.0.0.1:22045, 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:744)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2016-09-06 10:29:52,884 [myid:127.0.0.1:22066] - INFO  
[main-SendThread(127.0.0.1:22066):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:22066. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-09-06 10:29:52,885 [myid:127.0.0.1:22066] - INFO  
[main-SendThread(127.0.0.1:22066):ClientCnxn$SendThread@948] - Socket 
connection established, initiating session, client: /127.0.0.1:57979, server: 
127.0.0.1/127.0.0.1:22066
[junit] 2016-09-06 10:29:52,885 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:/127.0.0.1:22066:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:57979
[junit] 2016-09-06 10:29:52,885 [myid:] - WARN  
[NIOWorkerThread-9:NIOServerCnxn@369] - Exception causing close of session 0x0: 
ZooKeeperServer not running
[junit] 2016-09-06 10:29:52,885 [myid:] - INFO  
[NIOWorkerThread-9:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:57979 (no session established for client)
[junit] 2016-09-06 10:29:52,885 [myid:127.0.0.1:22066] - INFO  
[main-SendThread(127.0.0.1:22066):ClientCnxn$SendThread@1231] - Unable to read 
additional data from server sessionid 0x0, likely server has closed socket, 
closing socket connection and attempting reconnect
[junit] 2016-09-06 10:29:53,210 [myid:127.0.0.1:22048] - INFO  
[main-SendThread(127.0.0.1:22048):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:22048. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-09-06 10:29:53,211 [myid:127.0.0.1:22048] - WARN  
[main-SendThread(127.0.0.1:22048):ClientCnxn$SendThread@1235] - Session 
0x300917c17e1 for server 127.0.0.1/127.0.0.1:22048, 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.

[jira] [Updated] (ZOOKEEPER-2555) zookeeper started in observer mode takes long time to come to observer state once leader restarted and so client connected to observer mode has to wait for longer tim

[Rakesh Kumar Singh (JIRA)]

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

Rakesh Kumar Singh updated ZOOKEEPER-2555:
--
Description: 
zookeeper started in observer mode takes long time (some times 25 seconds) to 
come to observer state once leader restarted and so client connected to 
observer mode has to wait for longer time to get service

Steps to reproduce:-
1. Start zookeeper in cluster mode in which one node is in observer mode
2. stop the leader node (some times we need to wait for 30 secs to reproduce 
this issue)
3. Start the leader node
4. Check the observer node status -
It will be in 
"Error contacting service. It is probably not running."

and takes long time (25 secs) to come to observer mode. And hence client 
connected to this node will not get service during this time.
Log at observer node is as below:-

2016-09-06 17:49:14,774 [myid:2] - WARN  
[WorkerSender[myid=2]:QuorumCnxManager@459] - Cannot open channel to 3 at 
election address /10.18.221.194:3888
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at 
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
at java.net.Socket.connect(Socket.java:579)
at 
org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:444)
at 
org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:485)
at 
org.apache.zookeeper.server.quorum.QuorumCnxManager.toSend(QuorumCnxManager.java:421)
at 
org.apache.zookeeper.server.quorum.FastLeaderElection$Messenger$WorkerSender.process(FastLeaderElection.java:486)
at 
org.apache.zookeeper.server.quorum.FastLeaderElection$Messenger$WorkerSender.run(FastLeaderElection.java:465)
at java.lang.Thread.run(Thread.java:722)
{color:red}2016-09-06 17:49:14,776 [myid:2] - INFO  
[WorkerReceiver[myid=2]:FastLeaderElection@688] - Notification: 2 (message 
format version), 3 (n.leader), 0x2a0001 (n.zxid), 0x7 (n.round), LOOKING 
(n.state), 1 (n.sid), 0x2b (n.peerEPoch), LOOKING (my state)1 (n.config 
version)
2016-09-06 17:49:40,377 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):FastLeaderElection@928]
 - Notification time out: 51200 {color}
2016-09-06 17:49:40,378 [myid:2] - INFO  
[WorkerSender[myid=2]:QuorumCnxManager@278] - Have smaller server identifier, 
so dropping the connection: (3, 2)
2016-09-06 17:49:40,379 [myid:2] - INFO  
[WorkerReceiver[myid=2]:FastLeaderElection@688] - Notification: 2 (message 
format version), 3 (n.leader), 0x2a0001 (n.zxid), 0x7 (n.round), FOLLOWING 
(n.state), 1 (n.sid), 0x2c (n.peerEPoch), LOOKING (my state)1 (n.config 
version)
2016-09-06 17:49:40,381 [myid:2] - INFO  
[/10.18.219.50:3888:QuorumCnxManager$Listener@637] - Received connection 
request /10.18.221.194:34085
2016-09-06 17:49:40,388 [myid:2] - INFO  
[WorkerReceiver[myid=2]:FastLeaderElection@688] - Notification: 2 (message 
format version), 3 (n.leader), 0x2a0001 (n.zxid), 0x7 (n.round), LEADING 
(n.state), 3 (n.sid), 0x2c (n.peerEPoch), LOOKING (my state)1 (n.config 
version)
2016-09-06 17:49:40,388 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):MBeanRegistry@119]
 - Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id2,name1=replica.2,name2=LeaderElection]
2016-09-06 17:49:40,389 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):QuorumPeer@1049]
 - OBSERVING
2016-09-06 17:49:40,389 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@858]
 - minSessionTimeout set to 4000
2016-09-06 17:49:40,389 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@867]
 - maxSessionTimeout set to 4
2016-09-06 17:49:40,389 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@156]
 - Created server with tickTime 2000 minSessionTimeout 4000 maxSessionTimeout 
4 datadir 
/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/data/version-2 
snapdir 
/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/data/version-2
2016-09-06 17:49:40,389 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ObserverZooKeeperServer@56]
 - syncEnabled =true
2016-09-06 17:49:40,389 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):Observer@72] 
- Observing /10.18.221.194:2888
2016-09-06 17:49:40,396 [myid:2] - INFO  
[QuorumPeer[myid=2](p

[jira] [Created] (ZOOKEEPER-2555) zookeeper started in observer mode takes long time to come to observer state once leader restarted and so client connected to observer mode has to wait for longer tim

[Rakesh Kumar Singh (JIRA)]

Rakesh Kumar Singh created ZOOKEEPER-2555:
-

 Summary: zookeeper started in observer mode takes long time to 
come to observer state once leader restarted and so client connected to 
observer mode has to wait for longer time to get service
 Key: ZOOKEEPER-2555
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2555
 Project: ZooKeeper
  Issue Type: Bug
  Components: server
Affects Versions: 3.5.1
Reporter: Rakesh Kumar Singh


zookeeper started in observer mode takes long time (some times 25 seconds) to 
come to observer state once leader restarted and so client connected to 
observer mode has to wait for longer time to get service

Steps to reproduce:-
1. Start zookeeper in cluster mode in which one node is in observer mode
2. stop the leader node (some times we need to wait for 30 secs to reproduce 
this issue)
3. Start the leader node
4. Check the observer node status -
It will be in 
"Error contacting service. It is probably not running."

and takes long time (25 secs) to come to observer mode. And hence client 
connected to this node will not get service during this time.
Log at observer node is as below:-

2016-09-06 17:49:14,774 [myid:2] - WARN  
[WorkerSender[myid=2]:QuorumCnxManager@459] - Cannot open channel to 3 at 
election address /10.18.221.194:3888
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at 
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
at java.net.Socket.connect(Socket.java:579)
at 
org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:444)
at 
org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:485)
at 
org.apache.zookeeper.server.quorum.QuorumCnxManager.toSend(QuorumCnxManager.java:421)
at 
org.apache.zookeeper.server.quorum.FastLeaderElection$Messenger$WorkerSender.process(FastLeaderElection.java:486)
at 
org.apache.zookeeper.server.quorum.FastLeaderElection$Messenger$WorkerSender.run(FastLeaderElection.java:465)
at java.lang.Thread.run(Thread.java:722)
2016-09-06 17:49:14,776 [myid:2] - INFO  
[WorkerReceiver[myid=2]:FastLeaderElection@688] - Notification: 2 (message 
format version), 3 (n.leader), 0x2a0001 (n.zxid), 0x7 (n.round), LOOKING 
(n.state), 1 (n.sid), 0x2b (n.peerEPoch), LOOKING (my state)1 (n.config 
version)
2016-09-06 17:49:40,377 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):FastLeaderElection@928]
 - Notification time out: 51200
2016-09-06 17:49:40,378 [myid:2] - INFO  
[WorkerSender[myid=2]:QuorumCnxManager@278] - Have smaller server identifier, 
so dropping the connection: (3, 2)
2016-09-06 17:49:40,379 [myid:2] - INFO  
[WorkerReceiver[myid=2]:FastLeaderElection@688] - Notification: 2 (message 
format version), 3 (n.leader), 0x2a0001 (n.zxid), 0x7 (n.round), FOLLOWING 
(n.state), 1 (n.sid), 0x2c (n.peerEPoch), LOOKING (my state)1 (n.config 
version)
2016-09-06 17:49:40,381 [myid:2] - INFO  
[/10.18.219.50:3888:QuorumCnxManager$Listener@637] - Received connection 
request /10.18.221.194:34085
2016-09-06 17:49:40,388 [myid:2] - INFO  
[WorkerReceiver[myid=2]:FastLeaderElection@688] - Notification: 2 (message 
format version), 3 (n.leader), 0x2a0001 (n.zxid), 0x7 (n.round), LEADING 
(n.state), 3 (n.sid), 0x2c (n.peerEPoch), LOOKING (my state)1 (n.config 
version)
2016-09-06 17:49:40,388 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):MBeanRegistry@119]
 - Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id2,name1=replica.2,name2=LeaderElection]
2016-09-06 17:49:40,389 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):QuorumPeer@1049]
 - OBSERVING
2016-09-06 17:49:40,389 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@858]
 - minSessionTimeout set to 4000
2016-09-06 17:49:40,389 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@867]
 - maxSessionTimeout set to 4
2016-09-06 17:49:40,389 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@156]
 - Created server with tickTime 2000 minSessionTimeout 4000 maxSessionTimeout 
4 datadir 
/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/data/version-2 
snapdir 
/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/data/version-2
2016-09-06 17:49:40,389 [myid:2] - INFO  
[QuorumPeer[myid=2](

ZooKeeper_branch35_jdk7 - Build # 650 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_jdk7/650/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 414159 lines...]
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioWorker.writeFromTaskLoop(AbstractNioWorker.java:151)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioChannel$WriteTask.run(AbstractNioChannel.java:315)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:391)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:315)
[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:1145)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2016-09-06 09:08:49,101 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port22238,name1=Connections,name2=127.0.0.1,name3=0x10091403193]
[junit] 2016-09-06 09:08:49,201 [myid:] - INFO  [main:ZooKeeper@1313] - 
Session: 0x10091403193 closed
[junit] 2016-09-06 09:08:49,201 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 140841
[junit] 2016-09-06 09:08:49,201 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x10091403193
[junit] 2016-09-06 09:08:49,201 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 1644
[junit] 2016-09-06 09:08:49,202 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2016-09-06 09:08:49,202 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-09-06 09:08:49,202 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-09-06 09:08:49,202 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:22238
[junit] 2016-09-06 09:08:49,205 [myid:] - INFO  [main:ZooKeeperServer@529] 
- shutting down
[junit] 2016-09-06 09:08:49,205 [myid:] - ERROR [main:ZooKeeperServer@501] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-09-06 09:08:49,205 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2016-09-06 09:08:49,206 [myid:] - INFO  
[main:PrepRequestProcessor@965] - Shutting down
[junit] 2016-09-06 09:08:49,206 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2016-09-06 09:08:49,206 [myid:] - INFO  [ProcessThread(sid:0 
cport:22238)::PrepRequestProcessor@154] - PrepRequestProcessor exited loop!
[junit] 2016-09-06 09:08:49,206 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2016-09-06 09:08:49,206 [myid:] - INFO  
[main:FinalRequestProcessor@479] - shutdown of request processor complete
[junit] 2016-09-06 09:08:49,206 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port22238,name1=InMemoryDataTree]
[junit] 2016-09-06 09:08:49,206 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port22238]
[junit] 2016-09-06 09:08:49,207 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 22238
[junit] 2016-09-06 09:08:49,207 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-09-06 09:08:49,213 [myid:] - INFO  [main:ClientBase@568] - 
fdcount after test is: 4818 at start it was 4823
[junit] 2016-09-06 09:08:49,213 [myid:] - INFO  [main:ZKTestCase$1@65] - 
SUCCEEDED testWatcherAutoResetWithLocal
[junit] 2016-09-06 09:08:49,213 [myid:] - INFO  [main:ZKTestCase$1@60] - 
FINISHED testWatcherAutoResetWithLocal
[junit] Tests run: 101, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
495.535 sec, Thread: 5, Class: org.apache.zookeeper.test.NioNettySuiteTest
[junit] 2016-09-06 09:08:49,547 [myid:127.0.0.1:22115] - INFO  
[main-SendThread(127.0.0.1:22115):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:22115. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-09-06 09:08:49,548 [myid:127.0.0.1:22115] - WARN  
[main-SendThr

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

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1297/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 430728 lines...]
[junit] 2016-09-06 08:27:01,223 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-09-06 08:27:01,223 [myid:] - INFO  [main:ClientBase@361] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-09-06 08:27:01,224 [myid:] - INFO  [main:ZooKeeperServer@889] 
- minSessionTimeout set to 6000
[junit] 2016-09-06 08:27:01,224 [myid:] - INFO  [main:ZooKeeperServer@898] 
- maxSessionTimeout set to 6
[junit] 2016-09-06 08:27:01,224 [myid:] - INFO  [main:ZooKeeperServer@159] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test8603195656695249419.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test8603195656695249419.junit.dir/version-2
[junit] 2016-09-06 08:27:01,225 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test8603195656695249419.junit.dir/version-2/snapshot.b
[junit] 2016-09-06 08:27:01,227 [myid:] - INFO  [main:FileTxnSnapLog@298] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test8603195656695249419.junit.dir/version-2/snapshot.b
[junit] 2016-09-06 08:27:01,228 [myid:] - ERROR [main:ZooKeeperServer@501] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-09-06 08:27:01,228 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-09-06 08:27:01,229 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:58814
[junit] 2016-09-06 08:27:01,229 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:58814
[junit] 2016-09-06 08:27:01,230 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-09-06 08:27:01,230 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:58814 (no session established for client)
[junit] 2016-09-06 08:27:01,230 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-09-06 08:27:01,231 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-09-06 08:27:01,232 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-09-06 08:27:01,232 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-09-06 08:27:01,232 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-09-06 08:27:01,232 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17809
[junit] 2016-09-06 08:27:01,233 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-09-06 08:27:01,233 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-09-06 08:27:01,233 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-09-06 08:27:01,261 [myid:] - INFO  
[SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop!
[junit] 2016-09-06 08:27:01,261 [myid:] - INFO  
[SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop!
[junit] 2016-09-06 08:27:01,302 [myid:] - INFO  [main:ZooKeeper@1313] - 
Session: 0x1237b970312 closed
[junit] 2016-09-06 08:27:01,302 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1237b970312
[junit] 2016-09-06 08:27:01,302 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-09-06 08:27:01,303 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2016-09-06 08:27:01,303 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-09-06 08:27:01,303 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-09-06