[jira] [Commented] (ZOOKEEPER-2141) ACL cache in DataTree never removes entries

[Adam Milne-Smith (JIRA)]

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

Adam Milne-Smith commented on ZOOKEEPER-2141:
-

I'll take a look and fix these - thanks

> ACL cache in DataTree never removes entries
> ---
>
> Key: ZOOKEEPER-2141
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2141
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Karol Dudzinski
>Assignee: Karol Dudzinski
> Attachments: ZOOKEEPER-2141.patch, ZOOKEEPER-2141.patch
>
>
> The problem and potential solutions are discussed in 
> http://mail-archives.apache.org/mod_mbox/zookeeper-user/201502.mbox/browser
> I will attach a proposed patch in due course.



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

Re: github.com zookeeper pull requests in "limbo"

[Flavio Junqueira]

+1 for accepting requesting to infra to accept PRs via github. We've done the 
transition in BookKeeper and have been doing it in Kafka for a while, it works 
pretty well.

I'm happy you brought this up, Pay, I've been thinking about it. 

-Flavio

> On 10 Mar 2016, at 00:38, Patrick Hunt  wrote:
> 
> Hi folks. If you look on github.com you'll see a number of pull
> request (41 atm) that are effectively in limbo given we don't accept
> pull requests that way:
> https://github.com/apache/zookeeper/pulls
> 
> rather through our Jira process
> https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute
> 
> someday we might move to git, but for the time being it seems like we
> should do something about this.
> 
> I was thinking about contacting Apache infra and asking them if they
> can turn off accepting pull requests at github.com, just wanted to
> check with dev@ to see if this makes sense or do folks want to do
> something else? If I don't hear back anything negative in the next few
> days I'll ping infra about shutting down acceptance of pull requests
> (may not be possible but I'll check). I'm not talking about removing
> the mirror to be clear, just shutting down accepting pull requests on
> the mirror.
> 
> Patrick
> 
> ps. regardless we probably need to get back to everyone and ask them
> to follow the HTC page I don't seem to be able to close out the
> PRs, just comment on them, so that's going to be a possible issue as
> well arg.

[jira] [Commented] (ZOOKEEPER-2384) Support atomic increment / decrement of znode value

[Nick Hill (JIRA)]

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

Nick Hill commented on ZOOKEEPER-2384:
--

How about: setData (e.g. empty) to increment, setAcl to decrement. You can get 
the current count by subtracting aversion from version in the returned stat, or 
similarly query the count just by using exists()
So then Increment would also work in multi (but I don't think decrement since 
no acl)
Could be an effective hack for some use cases (avoids contention retry issue)

> Support atomic increment / decrement of znode value
> ---
>
> Key: ZOOKEEPER-2384
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2384
> Project: ZooKeeper
>  Issue Type: Improvement
>Reporter: Ted Yu
>
> Use case is to store reference count (integer type) in znode.
> It is desirable to provide support for atomic increment / decrement of the 
> znode value.
> Suggestion from Flavio:
> you can read the znode, keep the version of the znode, update the value, 
> write back conditionally. The condition for the setData operation to succeed 
> is that the version is the same that it read
> While the above is feasible, developer has to implement retry logic 
> him/herself. It is not easy to combine increment / decrement with other 
> operations using multi.



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

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

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 347336 lines...]
[junit] 2016-03-10 06:10:25,649 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-03-10 06:10:25,650 [myid:] - INFO  [main:ClientBase@460] - 
STARTING server
[junit] 2016-03-10 06:10:25,651 [myid:] - INFO  [main:ClientBase@380] - 
CREATING server instance 127.0.0.1:11222
[junit] 2016-03-10 06:10:25,651 [myid:] - INFO  
[main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 
kB direct buffers.
[junit] 2016-03-10 06:10:25,652 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-03-10 06:10:25,652 [myid:] - INFO  [main:ClientBase@355] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-03-10 06:10:25,653 [myid:] - INFO  [main:ZooKeeperServer@858] 
- minSessionTimeout set to 6000
[junit] 2016-03-10 06:10:25,653 [myid:] - INFO  [main:ZooKeeperServer@867] 
- maxSessionTimeout set to 6
[junit] 2016-03-10 06:10:25,653 [myid:] - INFO  [main:ZooKeeperServer@156] 
- 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/test3830599348907704845.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test3830599348907704845.junit.dir/version-2
[junit] 2016-03-10 06:10:25,654 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test3830599348907704845.junit.dir/version-2/snapshot.b
[junit] 2016-03-10 06:10:25,656 [myid:] - INFO  [main:FileTxnSnapLog@298] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test3830599348907704845.junit.dir/version-2/snapshot.b
[junit] 2016-03-10 06:10:25,657 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-03-10 06:10:25,658 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:34394
[junit] 2016-03-10 06:10:25,659 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:34394
[junit] 2016-03-10 06:10:25,659 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-03-10 06:10:25,659 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:34394 (no session established for client)
[junit] 2016-03-10 06:10:25,660 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-03-10 06:10:25,661 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-03-10 06:10:25,661 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-03-10 06:10:25,662 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-03-10 06:10:25,662 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-03-10 06:10:25,662 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17702
[junit] 2016-03-10 06:10:25,662 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-03-10 06:10:25,662 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-03-10 06:10:25,662 [myid:] - INFO  [main:ClientBase@537] - 
tearDown starting
[junit] 2016-03-10 06:10:25,742 [myid:] - INFO  [main:ZooKeeper@1110] - 
Session: 0x11fdc243768 closed
[junit] 2016-03-10 06:10:25,742 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for 
session: 0x11fdc243768
[junit] 2016-03-10 06:10:25,742 [myid:] - INFO  [main:ClientBase@507] - 
STOPPING server
[junit] 2016-03-10 06:10:25,743 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-03-10 06:10:25,743 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-03-10 06:10:25,743 [myid:] - INFO  

[jira] [Commented] (ZOOKEEPER-2087) Few UX improvements in ZooInspector

[Adam Dudczak (JIRA)]

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

Adam Dudczak commented on ZOOKEEPER-2087:
-

Awesome ;-) Thanks Patrick.

> Few UX improvements in ZooInspector
> ---
>
> Key: ZOOKEEPER-2087
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2087
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: contrib
>Affects Versions: 3.4.6
>Reporter: Adam Dudczak
>Assignee: Adam Dudczak
>Priority: Minor
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2087.patch, ZOOKEEPER-2087.patch
>
>
> A few simple changes would simplify using ZooInspector a lot.  
> - Alphabetical order of nodes on a tree view
> - Short term caching of zookeeper nodes for faster rendering of node tree
> - Add/Delete node in context menu of a node
> - Keyboard shortcuts for add/deleting a node
> - Logging information that ZooInspector failed to load nodeViewers



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

ZooKeeper_branch35_jdk8 - Build # 3 - Failure

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 380724 lines...]
[junit] 2016-03-10 06:08:45,202 [myid:] - WARN  
[LearnerHandler-/127.0.0.1:51198:LearnerHandler@903] - Ignoring unexpected 
exception
[junit] java.lang.InterruptedException
[junit] at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1220)
[junit] at 
java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:335)
[junit] at 
java.util.concurrent.LinkedBlockingQueue.put(LinkedBlockingQueue.java:339)
[junit] at 
org.apache.zookeeper.server.quorum.LearnerHandler.shutdown(LearnerHandler.java:901)
[junit] at 
org.apache.zookeeper.server.quorum.LearnerHandler.run(LearnerHandler.java:622)
[junit] 2016-03-10 06:08:45,203 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-03-10 06:08:45,203 [myid:] - WARN  
[LearnerHandler-/127.0.0.1:51183:LearnerHandler@903] - Ignoring unexpected 
exception
[junit] java.lang.InterruptedException
[junit] at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1220)
[junit] at 
java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:335)
[junit] at 
java.util.concurrent.LinkedBlockingQueue.put(LinkedBlockingQueue.java:339)
[junit] at 
org.apache.zookeeper.server.quorum.LearnerHandler.shutdown(LearnerHandler.java:901)
[junit] at 
org.apache.zookeeper.server.quorum.LearnerHandler.run(LearnerHandler.java:622)
[junit] 2016-03-10 06:08:45,203 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:/127.0.0.1:30214:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2016-03-10 06:08:45,203 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-03-10 06:08:45,203 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-03-10 06:08:45,204 [myid:] - INFO  
[/127.0.0.1:30216:QuorumCnxManager$Listener@659] - Leaving listener
[junit] 2016-03-10 06:08:45,204 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.5,name2=Leader]
[junit] 2016-03-10 06:08:45,206 [myid:] - INFO  [main:QuorumUtil@254] - 
Shutting down leader election 
QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled)
[junit] 2016-03-10 06:08:45,206 [myid:] - WARN  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):QuorumPeer@1126] - 
Unexpected exception
[junit] java.lang.InterruptedException
[junit] at java.lang.Object.wait(Native Method)
[junit] at 
org.apache.zookeeper.server.quorum.Leader.lead(Leader.java:559)
[junit] at 
org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:1123)
[junit] 2016-03-10 06:08:45,206 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):Leader@613] - 
Shutting down
[junit] 2016-03-10 06:08:45,206 [myid:] - INFO  [main:QuorumUtil@259] - 
Waiting for QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled) to exit 
thread
[junit] 2016-03-10 06:08:45,206 [myid:] - WARN  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):QuorumPeer@1157] - 
PeerState set to LOOKING
[junit] 2016-03-10 06:08:45,206 [myid:] - WARN  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):QuorumPeer@1139] - 
QuorumPeer main thread exited
[junit] 2016-03-10 06:08:45,206 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5]
[junit] 2016-03-10 06:08:45,207 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.5]
[junit] 2016-03-10 06:08:45,207 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.1]
[junit] 2016-03-10 06:08:45,207 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.2]
[junit] 2016-03-10 06:08:45,207 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):MBeanRegistry@128] 
- 

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

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/1887/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 574 lines...]
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:18)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
at 
org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
at 
org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387)
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:158)
... 14 more
Caused by: org.tmatesoft.sqljet.core.SqlJetException: SCHEMA: error code is 
SCHEMA
at 
org.tmatesoft.sqljet.core.internal.table.SqlJetOptions.verifySchemaVersion(SqlJetOptions.java:269)
at 
org.tmatesoft.sqljet.core.internal.table.SqlJetOptions.changeSchemaVersion(SqlJetOptions.java:282)
at 
org.tmatesoft.sqljet.core.internal.schema.SqlJetSchema.createTableSafe(SqlJetSchema.java:527)
at 
org.tmatesoft.sqljet.core.internal.schema.SqlJetSchema.createTable(SqlJetSchema.java:476)
at org.tmatesoft.sqljet.core.table.SqlJetDb$5.run(SqlJetDb.java:270)
at org.tmatesoft.sqljet.core.table.SqlJetDb$3.run(SqlJetDb.java:240)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine$12.runSynchronized(SqlJetEngine.java:533)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.runSynchronized(SqlJetEngine.java:217)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.runEngineTransaction(SqlJetEngine.java:529)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.runTransaction(SqlJetDb.java:238)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.runWriteTransaction(SqlJetDb.java:211)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.createTable(SqlJetDb.java:268)
at 
org.tmatesoft.svn.core.internal.wc17.db.statement.SVNWCDbCreateSchema$1.run(SVNWCDbCreateSchema.java:237)
at org.tmatesoft.sqljet.core.table.SqlJetDb$3.run(SqlJetDb.java:240)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine$12.runSynchronized(SqlJetEngine.java:538)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.runSynchronized(SqlJetEngine.java:217)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.runEngineTransaction(SqlJetEngine.java:529)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.runTransaction(SqlJetDb.java:238)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.runWriteTransaction(SqlJetDb.java:211)
at 
org.tmatesoft.svn.core.internal.wc17.db.statement.SVNWCDbCreateSchema.exec(SVNWCDbCreateSchema.java:221)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetStatement.done(SVNSqlJetStatement.java:420)
at 
org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb$BumpRevisionPostUpdate.bumpMovedAway(SVNWCDb.java:5185)
at 
org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb$BumpRevisionPostUpdate.transaction(SVNWCDb.java:5178)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.runTransaction(SVNSqlJetDb.java:256)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.runTransaction(SVNSqlJetDb.java:250)
at 
org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.opBumpRevisionPostUpdate(SVNWCDb.java:5130)
at 
org.tmatesoft.svn.core.internal.wc17.SVNUpdateEditor17.closeEdit(SVNUpdateEditor17.java:1728)
at 
org.tmatesoft.svn.core.internal.wc.SVNCancellableEditor.closeEdit(SVNCancellableEditor.java:148)
at 
org.tmatesoft.svn.core.internal.io.dav.handlers.DAVEditorHandler.endElement(DAVEditorHandler.java:488)
at 
org.tmatesoft.svn.core.internal.io.dav.handlers.BasicDAVHandler.endElement(BasicDAVHandler.java:103)
at 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown 
Source)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown
 Source)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown
 Source)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown 
Source)
at 
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown 
Source)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
 Source)
at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown 
Source)
at 

[jira] [Commented] (ZOOKEEPER-2087) Few UX improvements in ZooInspector

[Hudson (JIRA)]

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

Hudson commented on ZOOKEEPER-2087:
---

SUCCESS: Integrated in ZooKeeper-trunk #2842 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/2842/])
ZOOKEEPER-2087 Few UX improvements in ZooInspector (Adam Dudczak via phunt) 
(phunt: 
[http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN=rev=1734346])
* trunk/src/contrib/zooinspector/ivy.xml
* 
trunk/src/contrib/zooinspector/src/java/org/apache/zookeeper/inspector/gui/ZooInspectorPanel.java
* 
trunk/src/contrib/zooinspector/src/java/org/apache/zookeeper/inspector/gui/ZooInspectorTreeViewer.java
* 
trunk/src/contrib/zooinspector/src/java/org/apache/zookeeper/inspector/gui/actions
* 
trunk/src/contrib/zooinspector/src/java/org/apache/zookeeper/inspector/gui/actions/AddNodeAction.java
* 
trunk/src/contrib/zooinspector/src/java/org/apache/zookeeper/inspector/gui/actions/DeleteNodeAction.java
* 
trunk/src/contrib/zooinspector/src/java/org/apache/zookeeper/inspector/manager/NodesCache.java
* 
trunk/src/contrib/zooinspector/src/java/org/apache/zookeeper/inspector/manager/ZooInspectorManagerImpl.java


> Few UX improvements in ZooInspector
> ---
>
> Key: ZOOKEEPER-2087
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2087
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: contrib
>Affects Versions: 3.4.6
>Reporter: Adam Dudczak
>Assignee: Adam Dudczak
>Priority: Minor
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2087.patch, ZOOKEEPER-2087.patch
>
>
> A few simple changes would simplify using ZooInspector a lot.  
> - Alphabetical order of nodes on a tree view
> - Short term caching of zookeeper nodes for faster rendering of node tree
> - Add/Delete node in context menu of a node
> - Keyboard shortcuts for add/deleting a node
> - Logging information that ZooInspector failed to load nodeViewers



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

ZooKeeper-trunk-jdk8 - Build # 518 - Failure

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 384705 lines...]
[junit] 2016-03-10 05:53:05,922 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-03-10 05:53:05,923 [myid:] - INFO  [main:ClientBase@460] - 
STARTING server
[junit] 2016-03-10 05:53:05,923 [myid:] - INFO  [main:ClientBase@380] - 
CREATING server instance 127.0.0.1:11222
[junit] 2016-03-10 05:53:05,924 [myid:] - INFO  
[main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 2 selector thread(s), 32 worker threads, and 64 
kB direct buffers.
[junit] 2016-03-10 05:53:05,924 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-03-10 05:53:05,925 [myid:] - INFO  [main:ClientBase@355] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-03-10 05:53:05,925 [myid:] - INFO  [main:ZooKeeperServer@858] 
- minSessionTimeout set to 6000
[junit] 2016-03-10 05:53:05,925 [myid:] - INFO  [main:ZooKeeperServer@867] 
- maxSessionTimeout set to 6
[junit] 2016-03-10 05:53:05,925 [myid:] - INFO  [main:ZooKeeperServer@156] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test8631474545094955399.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test8631474545094955399.junit.dir/version-2
[junit] 2016-03-10 05:53:05,926 [myid:] - INFO  [ProcessThread(sid:0 
cport:11222)::PrepRequestProcessor@154] - PrepRequestProcessor exited loop!
[junit] 2016-03-10 05:53:05,931 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test8631474545094955399.junit.dir/version-2/snapshot.b
[junit] 2016-03-10 05:53:05,937 [myid:] - INFO  [main:FileTxnSnapLog@298] - 
Snapshotting: 0xb to 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test8631474545094955399.junit.dir/version-2/snapshot.b
[junit] 2016-03-10 05:53:05,943 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-03-10 05:53:05,944 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:50522
[junit] 2016-03-10 05:53:05,949 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:50522
[junit] 2016-03-10 05:53:05,949 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-03-10 05:53:05,951 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:50522 (no session established for client)
[junit] 2016-03-10 05:53:05,951 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-03-10 05:53:05,954 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-03-10 05:53:05,954 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-03-10 05:53:05,954 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-03-10 05:53:05,954 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-03-10 05:53:05,956 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 62179
[junit] 2016-03-10 05:53:05,956 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-03-10 05:53:05,956 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-03-10 05:53:05,957 [myid:] - INFO  [main:ClientBase@537] - 
tearDown starting
[junit] 2016-03-10 05:53:05,967 [myid:] - INFO  [main:ZooKeeper@1110] - 
Session: 0x1016884112f closed
[junit] 2016-03-10 05:53:05,967 [myid:] - INFO  [main:ClientBase@507] - 
STOPPING server
[junit] 2016-03-10 05:53:05,968 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-03-10 05:53:05,968 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-03-10 05:53:05,968 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2016-03-10 05:53:05,969 [myid:] - INFO  

Failed: ZOOKEEPER-2133 PreCommit Build #3097

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 390859 lines...]
 [exec] -1 tests included.  The patch doesn't appear to include any new 
or modified tests.
 [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/3097//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3097//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3097//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] 5cea2d89a85f8f6d51de658f26a3aba9bc429391 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:1646:
 exec returned: 1

Total time: 18 minutes 56 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-2133
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



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

[jira] [Commented] (ZOOKEEPER-2133) zkperl: Segmentation fault if getting a node with null value

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-2133:
--

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

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

This message is automatically generated.

> zkperl: Segmentation fault if getting a node with null value
> 
>
> Key: ZOOKEEPER-2133
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2133
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: contrib-bindings
>Affects Versions: 3.4.6, 3.5.0
>Reporter: Botond Hejj
>Assignee: Botond Hejj
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2133.patch
>
>
> If Node content is null:
> [zk: (CONNECTED) 0] get /apps
> null
> cZxid = 0x1000d
> than
> my $data = $zk->{zkh}->get('/apps');
> causing a core dump with Segmentation fault



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

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

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/1886/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 572 lines...]
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:18)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
at 
org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
at 
org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387)
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:158)
... 14 more
Caused by: org.tmatesoft.sqljet.core.SqlJetException: SCHEMA: error code is 
SCHEMA
at 
org.tmatesoft.sqljet.core.internal.table.SqlJetOptions.verifySchemaVersion(SqlJetOptions.java:269)
at 
org.tmatesoft.sqljet.core.internal.table.SqlJetOptions.changeSchemaVersion(SqlJetOptions.java:282)
at 
org.tmatesoft.sqljet.core.internal.schema.SqlJetSchema.createTableSafe(SqlJetSchema.java:527)
at 
org.tmatesoft.sqljet.core.internal.schema.SqlJetSchema.createTable(SqlJetSchema.java:476)
at org.tmatesoft.sqljet.core.table.SqlJetDb$5.run(SqlJetDb.java:270)
at org.tmatesoft.sqljet.core.table.SqlJetDb$3.run(SqlJetDb.java:240)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine$12.runSynchronized(SqlJetEngine.java:533)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.runSynchronized(SqlJetEngine.java:217)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.runEngineTransaction(SqlJetEngine.java:529)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.runTransaction(SqlJetDb.java:238)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.runWriteTransaction(SqlJetDb.java:211)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.createTable(SqlJetDb.java:268)
at 
org.tmatesoft.svn.core.internal.wc17.db.statement.SVNWCDbCreateSchema$1.run(SVNWCDbCreateSchema.java:237)
at org.tmatesoft.sqljet.core.table.SqlJetDb$3.run(SqlJetDb.java:240)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine$12.runSynchronized(SqlJetEngine.java:538)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.runSynchronized(SqlJetEngine.java:217)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.runEngineTransaction(SqlJetEngine.java:529)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.runTransaction(SqlJetDb.java:238)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.runWriteTransaction(SqlJetDb.java:211)
at 
org.tmatesoft.svn.core.internal.wc17.db.statement.SVNWCDbCreateSchema.exec(SVNWCDbCreateSchema.java:221)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetStatement.done(SVNSqlJetStatement.java:420)
at 
org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb$BumpRevisionPostUpdate.bumpMovedAway(SVNWCDb.java:5185)
at 
org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb$BumpRevisionPostUpdate.transaction(SVNWCDb.java:5178)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.runTransaction(SVNSqlJetDb.java:256)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.runTransaction(SVNSqlJetDb.java:250)
at 
org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.opBumpRevisionPostUpdate(SVNWCDb.java:5130)
at 
org.tmatesoft.svn.core.internal.wc17.SVNUpdateEditor17.closeEdit(SVNUpdateEditor17.java:1728)
at 
org.tmatesoft.svn.core.internal.wc.SVNCancellableEditor.closeEdit(SVNCancellableEditor.java:148)
at 
org.tmatesoft.svn.core.internal.io.dav.handlers.DAVEditorHandler.endElement(DAVEditorHandler.java:488)
at 
org.tmatesoft.svn.core.internal.io.dav.handlers.BasicDAVHandler.endElement(BasicDAVHandler.java:103)
at 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown 
Source)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown
 Source)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown
 Source)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown 
Source)
at 
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown 
Source)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
 Source)
at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown 
Source)
at 

ZooKeeper-trunk-WinVS2008 - Build # 1885 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/1885/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 580 lines...]
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:18)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
at 
org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
at 
org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387)
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:158)
... 14 more
Caused by: org.tmatesoft.sqljet.core.SqlJetException: SCHEMA: error code is 
SCHEMA
at 
org.tmatesoft.sqljet.core.internal.table.SqlJetOptions.verifySchemaVersion(SqlJetOptions.java:269)
at 
org.tmatesoft.sqljet.core.internal.table.SqlJetOptions.changeSchemaVersion(SqlJetOptions.java:282)
at 
org.tmatesoft.sqljet.core.internal.schema.SqlJetSchema.createTableSafe(SqlJetSchema.java:527)
at 
org.tmatesoft.sqljet.core.internal.schema.SqlJetSchema.createTable(SqlJetSchema.java:476)
at org.tmatesoft.sqljet.core.table.SqlJetDb$5.run(SqlJetDb.java:270)
at org.tmatesoft.sqljet.core.table.SqlJetDb$3.run(SqlJetDb.java:240)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine$12.runSynchronized(SqlJetEngine.java:533)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.runSynchronized(SqlJetEngine.java:217)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.runEngineTransaction(SqlJetEngine.java:529)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.runTransaction(SqlJetDb.java:238)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.runWriteTransaction(SqlJetDb.java:211)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.createTable(SqlJetDb.java:268)
at 
org.tmatesoft.svn.core.internal.wc17.db.statement.SVNWCDbCreateSchema$1.run(SVNWCDbCreateSchema.java:237)
at org.tmatesoft.sqljet.core.table.SqlJetDb$3.run(SqlJetDb.java:240)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine$12.runSynchronized(SqlJetEngine.java:538)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.runSynchronized(SqlJetEngine.java:217)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.runEngineTransaction(SqlJetEngine.java:529)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.runTransaction(SqlJetDb.java:238)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.runWriteTransaction(SqlJetDb.java:211)
at 
org.tmatesoft.svn.core.internal.wc17.db.statement.SVNWCDbCreateSchema.exec(SVNWCDbCreateSchema.java:221)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetStatement.done(SVNSqlJetStatement.java:420)
at 
org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb$BumpRevisionPostUpdate.bumpMovedAway(SVNWCDb.java:5185)
at 
org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb$BumpRevisionPostUpdate.transaction(SVNWCDb.java:5178)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.runTransaction(SVNSqlJetDb.java:256)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.runTransaction(SVNSqlJetDb.java:250)
at 
org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.opBumpRevisionPostUpdate(SVNWCDb.java:5130)
at 
org.tmatesoft.svn.core.internal.wc17.SVNUpdateEditor17.closeEdit(SVNUpdateEditor17.java:1728)
at 
org.tmatesoft.svn.core.internal.wc.SVNCancellableEditor.closeEdit(SVNCancellableEditor.java:148)
at 
org.tmatesoft.svn.core.internal.io.dav.handlers.DAVEditorHandler.endElement(DAVEditorHandler.java:488)
at 
org.tmatesoft.svn.core.internal.io.dav.handlers.BasicDAVHandler.endElement(BasicDAVHandler.java:103)
at 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown 
Source)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown
 Source)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown
 Source)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown 
Source)
at 
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown 
Source)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
 Source)
at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown 
Source)
at 

ZooKeeper_branch35_jdk7 - Build # 437 - Failure

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 378445 lines...]
 [exec]  : elapsed 6336 : OK
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/../../build/test/test-cppunit/conf/1.conf
 [exec] TestReconfigServer::testRemoveConnectedFollowerStarting zookeeper 
... STARTED
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/../../build/test/test-cppunit/conf/2.conf
 [exec] Starting zookeeper ... STARTED
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/../../build/test/test-cppunit/conf/0.conf
 [exec] Starting zookeeper ... STARTED
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/../../build/test/test-cppunit/conf/1.conf
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/../../build/test/test-cppunit/conf/2.conf
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/../../build/test/test-cppunit/conf/0.conf
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/../../build/test/test-cppunit/conf/1.conf
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/../../build/test/test-cppunit/conf/0.conf
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/../../build/test/test-cppunit/conf/1.conf
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/../../build/test/test-cppunit/conf/2.conf
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/../../build/test/test-cppunit/conf/0.conf
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/../../build/test/test-cppunit/conf/1.conf
 [exec] Stopping zookeeper ... STOPPED
 [exec] Stopping zookeeper ... STOPPED
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/../../build/test/test-cppunit/conf/2.conf
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/../../build/test/test-cppunit/conf/0.conf
 [exec] Stopping zookeeper ... STOPPED
 [exec]  : elapsed 6026 : OK
 [exec] TestReconfigServer::testRemoveFollowerStarting zookeeper ... FAILED 
TO START
 [exec] FAIL: zktest-mt
 [exec] ==
 [exec] 1 of 2 tests failed
 [exec] Please report to u...@zookeeper.apache.org
 [exec] ==
 [exec] make[1]: Leaving directory 
`/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build/test/test-cppunit'
 [exec] zktest-mt: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/tests/ZooKeeperQuorumServer.cc:61:
 void ZooKeeperQuorumServer::start(): Assertion `system(command.c_str()) == 0' 
failed.
 [exec] /bin/bash: line 5:  6055 Aborted 
ZKROOT=/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/../..
 CLASSPATH=$CLASSPATH:$CLOVER_HOME/lib/clover.jar ${dir}$tst
 [exec] make[1]: *** [check-TESTS] Error 1
 [exec] make: *** [check-am] Error 2

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build.xml:1361:
 The following error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build.xml:1321:
 The following error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build.xml:1331:
 exec returned: 2

Total time: 14 minutes 32 seconds
Build step 'Invoke Ant' marked build as failure
Archiving artifacts
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any

[jira] [Updated] (ZOOKEEPER-2133) zkperl: Segmentation fault if getting a node with null value

[Patrick Hunt (JIRA)]

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

Patrick Hunt updated ZOOKEEPER-2133:

Fix Version/s: 3.4.9

> zkperl: Segmentation fault if getting a node with null value
> 
>
> Key: ZOOKEEPER-2133
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2133
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: contrib-bindings
>Affects Versions: 3.4.6, 3.5.0
>Reporter: Botond Hejj
>Assignee: Botond Hejj
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2133.patch
>
>
> If Node content is null:
> [zk: (CONNECTED) 0] get /apps
> null
> cZxid = 0x1000d
> than
> my $data = $zk->{zkh}->get('/apps');
> causing a core dump with Segmentation fault



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

Re: github.com zookeeper pull requests in "limbo"

[Camille Fournier]

I'll start responding to some of these with a link to the HTC page to help
get it done.

C


On Wed, Mar 9, 2016 at 7:38 PM, Patrick Hunt  wrote:

> Hi folks. If you look on github.com you'll see a number of pull
> request (41 atm) that are effectively in limbo given we don't accept
> pull requests that way:
> https://github.com/apache/zookeeper/pulls
>
> rather through our Jira process
> https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute
>
> someday we might move to git, but for the time being it seems like we
> should do something about this.
>
> I was thinking about contacting Apache infra and asking them if they
> can turn off accepting pull requests at github.com, just wanted to
> check with dev@ to see if this makes sense or do folks want to do
> something else? If I don't hear back anything negative in the next few
> days I'll ping infra about shutting down acceptance of pull requests
> (may not be possible but I'll check). I'm not talking about removing
> the mirror to be clear, just shutting down accepting pull requests on
> the mirror.
>
> Patrick
>
> ps. regardless we probably need to get back to everyone and ask them
> to follow the HTC page I don't seem to be able to close out the
> PRs, just comment on them, so that's going to be a possible issue as
> well arg.
>

[jira] [Updated] (ZOOKEEPER-2386) Cannot achieve quorum when middle server (in a q of 3) is unreacable

[Enis Soztutar (JIRA)]

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

Enis Soztutar updated ZOOKEEPER-2386:
-
Attachment: zklogs.tar.gz

Attaching relevant logs from two servers that are alive. As you can see, we 
keep cycling the leader election + timeout loop forever. zk2 is always the 
leader, and from that servers perspective each cycle of leader election takes 
15 secs, while zk0 reports it around 30 sec. 

Again, (I think) the issue is that the vote that the candidate does not send 
the votes in parallel, but serially. So zk2 as a candidate cannot cast a self 
vote until the request to zk1 timesouts which takes more than 5 seconds. By 
that time, the follower zk0 already gives up on the leader, and starts a new 
round. So there is actually a leader elected every ~30 seconds, but the quorum 
cannot operate still. 

zk0: 
{code}
2016-01-27 23:30:15,293 [myid:1] - INFO  
[QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2182:Follower@63] - FOLLOWING - LEADER 
ELECTION TOOK - 31008
2016-01-27 23:30:50,417 [myid:1] - INFO  
[QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2182:Follower@63] - FOLLOWING - LEADER 
ELECTION TOOK - 31112
2016-01-27 23:31:25,326 [myid:1] - INFO  
[QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2182:Follower@63] - FOLLOWING - LEADER 
ELECTION TOOK - 30898
2016-01-27 23:32:00,340 [myid:1] - INFO  
[QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2182:Follower@63] - FOLLOWING - LEADER 
ELECTION TOOK - 30997
2016-01-27 23:32:35,365 [myid:1] - INFO  
[QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2182:Follower@63] - FOLLOWING - LEADER 
ELECTION TOOK - 31014
2016-01-27 23:33:10,391 [myid:1] - INFO  
[QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2182:Follower@63] - FOLLOWING - LEADER 
ELECTION TOOK - 31014
2016-01-27 23:33:45,485 [myid:1] - INFO  
[QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2182:Follower@63] - FOLLOWING - LEADER 
ELECTION TOOK - 31082
{code}

zk2:
{code}
2016-01-27 23:30:20,080 [myid:3] - INFO  
[QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2182:Leader@358] - LEADING - LEADER 
ELECTION TOOK - 14816
2016-01-27 23:30:55,407 [myid:3] - INFO  
[QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2182:Leader@358] - LEADING - LEADER 
ELECTION TOOK - 15324
2016-01-27 23:31:30,314 [myid:3] - INFO  
[QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2182:Leader@358] - LEADING - LEADER 
ELECTION TOOK - 14904
2016-01-27 23:32:05,327 [myid:3] - INFO  
[QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2182:Leader@358] - LEADING - LEADER 
ELECTION TOOK - 15010
2016-01-27 23:32:40,353 [myid:3] - INFO  
[QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2182:Leader@358] - LEADING - LEADER 
ELECTION TOOK - 15023
2016-01-27 23:33:15,179 [myid:3] - INFO  
[QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2182:Leader@358] - LEADING - LEADER 
ELECTION TOOK - 14823
2016-01-27 23:33:50,476 [myid:3] - INFO  
[QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2182:Leader@358] - LEADING - LEADER 
ELECTION TOOK - 15294
2016-01-27 23:34:25,234 [myid:3] - INFO  
[QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2182:Leader@358] - LEADING - LEADER 
ELECTION TOOK - 14756
20
{code}


> Cannot achieve quorum when middle server (in a q of 3) is unreacable
> 
>
> Key: ZOOKEEPER-2386
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2386
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Enis Soztutar
> Attachments: zklogs.tar.gz
>
>
> Recently, we've observed a curious case where a quorum was not reached for 
> days in a cluster of 3 nodes (zk0, zk1, zk2) and the middle node zk1 is 
> unreachable from network. 
> The leader election happens, and both zk0 and zk2 starts the vote. Then each 
> server sends notifications to every other server including itself. The 
> problem is that, zk1 vm is unavailable, so when we are trying to open up a 
> socket to connect to that server with socket timeout of 5 seconds, it delays 
> the notification processing of the vote sent from zk2 to zk2 (itself). The 
> vote eventually comes after 5 sec, but by that time, the follower (zk0) 
> already converted to the follower state. On the follower state, the follower 
> try to connect to leader 5 times with 1 second timeout (5 sec in total). 
> Since the leader does not start its peer port for 5 seconds after the 
> follower starts, the follower always times out connecting to the leader. This 
> cycle is repeating for hours / days even after restarting the servers several 
> times. 
> I believe this is related to the default timeouts (5 sec socket timeout) and 
> follower to leader connection timeout (5 tries with 1 second timeout). Only 
> after setting the {{zookeeper.cnxTimeout}} to 1 second, the quorum was 
> operating. 
> More logs coming shortly. 
> zoo.cfg: 
> {code}
> server.3=zk2-hostname:2889:3889
> server.2=zk1-hostname:2889:3889
> server.1=zk0-hostname:2889:3889
> {code}



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

Failed: ZOOKEEPER-2087 PreCommit Build #3096

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 389904 lines...]
 [exec] -1 tests included.  The patch doesn't appear to include any new 
or modified tests.
 [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/3096//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3096//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3096//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] cdb8b204ea74b1a2a1e81124ac98af94c4a47276 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:1646:
 exec returned: 1

Total time: 22 minutes 24 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-2087
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



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

[jira] [Commented] (ZOOKEEPER-2087) Few UX improvements in ZooInspector

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-2087:
--

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

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

This message is automatically generated.

> Few UX improvements in ZooInspector
> ---
>
> Key: ZOOKEEPER-2087
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2087
> Project: ZooKeeper
>  Issue Type: Improvement
>Affects Versions: 3.4.6
>Reporter: Adam Dudczak
>Assignee: Adam Dudczak
>Priority: Minor
> Attachments: ZOOKEEPER-2087.patch, ZOOKEEPER-2087.patch
>
>
> A few simple changes would simplify using ZooInspector a lot.  
> - Alphabetical order of nodes on a tree view
> - Short term caching of zookeeper nodes for faster rendering of node tree
> - Add/Delete node in context menu of a node
> - Keyboard shortcuts for add/deleting a node
> - Logging information that ZooInspector failed to load nodeViewers



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

[jira] [Updated] (ZOOKEEPER-2087) Few UX improvements in ZooInspector

[Patrick Hunt (JIRA)]

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

Patrick Hunt updated ZOOKEEPER-2087:

Attachment: ZOOKEEPER-2087.patch

Updated the patch to apply cleanly. Also fixed the license headers for the new 
files.

> Few UX improvements in ZooInspector
> ---
>
> Key: ZOOKEEPER-2087
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2087
> Project: ZooKeeper
>  Issue Type: Improvement
>Affects Versions: 3.4.6
>Reporter: Adam Dudczak
>Assignee: Adam Dudczak
>Priority: Minor
> Attachments: ZOOKEEPER-2087.patch, ZOOKEEPER-2087.patch
>
>
> A few simple changes would simplify using ZooInspector a lot.  
> - Alphabetical order of nodes on a tree view
> - Short term caching of zookeeper nodes for faster rendering of node tree
> - Add/Delete node in context menu of a node
> - Keyboard shortcuts for add/deleting a node
> - Logging information that ZooInspector failed to load nodeViewers



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

[jira] [Comment Edited] (ZOOKEEPER-2141) ACL cache in DataTree never removes entries

[Patrick Hunt (JIRA)]

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

Patrick Hunt edited comment on ZOOKEEPER-2141 at 3/10/16 12:49 AM:
---

qabot identified a couple issues:

1) missing license headers in the new files
2) findbugs noticed some locking issues.


was (Author: phunt):
qa identified a couple issues:

1) missing license headers in the new files
2) findbugs noticed some locking issues.

> ACL cache in DataTree never removes entries
> ---
>
> Key: ZOOKEEPER-2141
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2141
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Karol Dudzinski
>Assignee: Karol Dudzinski
> Attachments: ZOOKEEPER-2141.patch, ZOOKEEPER-2141.patch
>
>
> The problem and potential solutions are discussed in 
> http://mail-archives.apache.org/mod_mbox/zookeeper-user/201502.mbox/browser
> I will attach a proposed patch in due course.



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

[jira] [Commented] (ZOOKEEPER-2044) CancelledKeyException in zookeeper 3.4.5

[Patrick Hunt (JIRA)]

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

Patrick Hunt commented on ZOOKEEPER-2044:
-

I get bugged about this issue quite a bit, but it's really just cosmetic. Are 
you sure the risk outweighs the reward wrt 3.4, vs fixing in 3.5/trunk only?

> CancelledKeyException in zookeeper 3.4.5
> 
>
> Key: ZOOKEEPER-2044
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2044
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.6
> Environment: Red Hat Enterprise Linux Server release 6.2
>Reporter: shamjith antholi
>Assignee: Flavio Junqueira
>Priority: Minor
> Fix For: 3.4.9
>
> Attachments: ZOOKEEPER-2044.patch, ZOOKEEPER-2044.patch
>
>
> I am getting cancelled key exception in zookeeper (version 3.4.5). Please see 
> the log below. When this error is thrown, the connected solr shard is going 
> down by giving the error "Failed to index metadata in 
> Solr,StackTrace=SolrError: HTTP status 503.Reason: 
> {"responseHeader":{"status":503,"QTime":204},"error":{"msg":"ClusterState 
> says we are the leader, but locally we don't think so","code":503"  and 
> ultimately the current activity is going down. Could you please give a 
> solution for this ?
> Zookeper log 
> --
> 2014-09-16 02:58:47,799 [myid:1] - INFO  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@832] - Client 
> attempting to renew session 0x24868e7ca980003 at /172.22.0.5:58587
> 2014-09-16 02:58:47,800 [myid:1] - INFO  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:Learner@107] - Revalidating 
> client: 0x24868e7ca980003
> 2014-09-16 02:58:47,802 [myid:1] - INFO  
> [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:ZooKeeperServer@588] - Invalid 
> session 0x24868e7ca980003 for client /172.22.0.5:58587, probably expired
> 2014-09-16 02:58:47,803 [myid:1] - INFO  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed 
> socket connection for client /172.22.0.5:58587 which had sessionid 
> 0x24868e7ca980003
> 2014-09-16 02:58:47,810 [myid:1] - ERROR 
> [CommitProcessor:1:NIOServerCnxn@180] - Unexpected Exception:
> java.nio.channels.CancelledKeyException
> at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:55)
> at sun.nio.ch.SelectionKeyImpl.interestOps(SelectionKeyImpl.java:59)
> at 
> org.apache.zookeeper.server.NIOServerCnxn.sendBuffer(NIOServerCnxn.java:153)
> at 
> org.apache.zookeeper.server.NIOServerCnxn.sendResponse(NIOServerCnxn.java:1076)
> at 
> org.apache.zookeeper.server.NIOServerCnxn.process(NIOServerCnxn.java:1113)
> at org.apache.zookeeper.server.DataTree.setWatches(DataTree.java:1327)
> at 
> org.apache.zookeeper.server.ZKDatabase.setWatches(ZKDatabase.java:384)
> at 
> org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:304)
> at 
> org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:74)
>  



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

[jira] [Commented] (ZOOKEEPER-2195) fsync.warningthresholdms in zoo.cfg not working

[Dmitry Ryabkov (JIRA)]

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

Dmitry Ryabkov commented on ZOOKEEPER-2195:
---

Sure. I'll look into this.

> fsync.warningthresholdms in zoo.cfg not working
> ---
>
> Key: ZOOKEEPER-2195
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2195
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: quorum
>Affects Versions: 3.4.6, 3.5.0
>Reporter: David Fan
>Assignee: Biju Nair
>Priority: Trivial
> Attachments: ZOOKEEPER-2195-DOC.patch, ZOOKEEPER-2195.patch
>
>
> Config fsync.warningthresholdms in zoo.cfg does not work.
> I find QuorumPeerConfig.parseProperties give fsync.warningthresholdms a 
> prefix like "zookeeper.fsync.warningthresholdms".  But in class FileTxnLog 
> where fsync.warningthresholdms is used, code is 
> :Long.getLong("fsync.warningthresholdms", 1000),without prefix "zookeeper.", 
> therefore can not get fsync.warningthresholdms's value.
> I wonder the speed of fsync, need this config to see whether the speed is 
> good enough.



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

[jira] [Commented] (ZOOKEEPER-2384) Support atomic increment / decrement of znode value

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira commented on ZOOKEEPER-2384:
-

What I suggested isn't particularly hard to do, but it can be inefficient in 
the presence of contention. If there are many clients trying to do that, then 
they can keep stepping on each other and causing the conditional write to fail.

> Support atomic increment / decrement of znode value
> ---
>
> Key: ZOOKEEPER-2384
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2384
> Project: ZooKeeper
>  Issue Type: Improvement
>Reporter: Ted Yu
>
> Use case is to store reference count (integer type) in znode.
> It is desirable to provide support for atomic increment / decrement of the 
> znode value.
> Suggestion from Flavio:
> you can read the znode, keep the version of the znode, update the value, 
> write back conditionally. The condition for the setData operation to succeed 
> is that the version is the same that it read
> While the above is feasible, developer has to implement retry logic 
> him/herself. It is not easy to combine increment / decrement with other 
> operations using multi.



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

Failed: ZOOKEEPER-2385 PreCommit Build #3095

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 382091 lines...]
 [exec] -1 tests included.  The patch doesn't appear to include any new 
or modified tests.
 [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/3095//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3095//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3095//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] b32f7ca9786ef4c8e0d8a607e44cd21a41ab8ffe 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:1646:
 exec returned: 1

Total time: 17 minutes 13 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-2385
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



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

[jira] [Commented] (ZOOKEEPER-2385) Zookeeper trunk build is failing on windows

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-2385:
--

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12792329/ZOOKEEPER-2385-01.patch
  against trunk revision 1733679.

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

This message is automatically generated.

> Zookeeper trunk build is failing on windows
> ---
>
> Key: ZOOKEEPER-2385
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2385
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: build
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Blocker
> Fix For: 3.5.2
>
> Attachments: ZOOKEEPER-2385-01.patch
>
>
> command {{ant tar}} fails with following error
> {code}
> D:\gitHome\zookeeperTrunk\build.xml:722: The following error occurred while 
> executing this line:
> D:\gitHome\zookeeperTrunk\src\contrib\build.xml:47: The following error 
> occurred while executing this line:
> D:\gitHome\zookeeperTrunk\src\contrib\build-contrib.xml:207: Unable to delete 
> file D:\gitHome\zookeeperTrunk\src\java\lib\ivy-2.4.0.jar
> {code}
> This is happening only on windows.



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

[jira] [Updated] (ZOOKEEPER-2385) Zookeeper trunk build is failing on windows

[Chris Nauroth (JIRA)]

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

Chris Nauroth updated ZOOKEEPER-2385:
-
 Priority: Blocker  (was: Major)
Fix Version/s: 3.5.2

> Zookeeper trunk build is failing on windows
> ---
>
> Key: ZOOKEEPER-2385
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2385
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: build
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Blocker
> Fix For: 3.5.2
>
> Attachments: ZOOKEEPER-2385-01.patch
>
>
> command {{ant tar}} fails with following error
> {code}
> D:\gitHome\zookeeperTrunk\build.xml:722: The following error occurred while 
> executing this line:
> D:\gitHome\zookeeperTrunk\src\contrib\build.xml:47: The following error 
> occurred while executing this line:
> D:\gitHome\zookeeperTrunk\src\contrib\build-contrib.xml:207: Unable to delete 
> file D:\gitHome\zookeeperTrunk\src\java\lib\ivy-2.4.0.jar
> {code}
> This is happening only on windows.



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

[jira] [Updated] (ZOOKEEPER-2385) Zookeeper trunk build is failing on windows

[Arshad Mohammad (JIRA)]

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

Arshad Mohammad updated ZOOKEEPER-2385:
---
Attachment: ZOOKEEPER-2385-01.patch

changed ivy version in build-contrib.xml to 2.4.0

> Zookeeper trunk build is failing on windows
> ---
>
> Key: ZOOKEEPER-2385
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2385
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: build
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
> Attachments: ZOOKEEPER-2385-01.patch
>
>
> command {{ant tar}} fails with following error
> {code}
> D:\gitHome\zookeeperTrunk\build.xml:722: The following error occurred while 
> executing this line:
> D:\gitHome\zookeeperTrunk\src\contrib\build.xml:47: The following error 
> occurred while executing this line:
> D:\gitHome\zookeeperTrunk\src\contrib\build-contrib.xml:207: Unable to delete 
> file D:\gitHome\zookeeperTrunk\src\java\lib\ivy-2.4.0.jar
> {code}
> This is happening only on windows.



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

[jira] [Commented] (ZOOKEEPER-2385) Zookeeper trunk build is failing on windows

[Arshad Mohammad (JIRA)]

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

Arshad Mohammad commented on ZOOKEEPER-2385:


This is happening because ivy version in {{build.xml}} and 
{{src\contrib\build-contrib.xml}} are different.
Ivy jar downloaded at {{src\java\lib}} is being deleted while it is in use. It 
is like a build race condition.

> Zookeeper trunk build is failing on windows
> ---
>
> Key: ZOOKEEPER-2385
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2385
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: build
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>
> command {{ant tar}} fails with following error
> {code}
> D:\gitHome\zookeeperTrunk\build.xml:722: The following error occurred while 
> executing this line:
> D:\gitHome\zookeeperTrunk\src\contrib\build.xml:47: The following error 
> occurred while executing this line:
> D:\gitHome\zookeeperTrunk\src\contrib\build-contrib.xml:207: Unable to delete 
> file D:\gitHome\zookeeperTrunk\src\java\lib\ivy-2.4.0.jar
> {code}
> This is happening only on windows.



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

[jira] [Created] (ZOOKEEPER-2385) Zookeeper trunk build is failing on windows

[Arshad Mohammad (JIRA)]

Arshad Mohammad created ZOOKEEPER-2385:
--

 Summary: Zookeeper trunk build is failing on windows
 Key: ZOOKEEPER-2385
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2385
 Project: ZooKeeper
  Issue Type: Bug
  Components: build
Reporter: Arshad Mohammad
Assignee: Arshad Mohammad


command {{ant tar}} fails with following error
{code}
D:\gitHome\zookeeperTrunk\build.xml:722: The following error occurred while 
executing this line:
D:\gitHome\zookeeperTrunk\src\contrib\build.xml:47: The following error 
occurred while executing this line:
D:\gitHome\zookeeperTrunk\src\contrib\build-contrib.xml:207: Unable to delete 
file D:\gitHome\zookeeperTrunk\src\java\lib\ivy-2.4.0.jar
{code}

This is happening only on windows.



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

[jira] [Commented] (ZOOKEEPER-2247) Zookeeper service becomes unavailable when leader fails to write transaction log

[ASF GitHub Bot (JIRA)]

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

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

Github user arshadmohammad closed the pull request at:

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


> Zookeeper service becomes unavailable when leader fails to write transaction 
> log
> 
>
> Key: ZOOKEEPER-2247
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2247
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Arshad Mohammad
>Assignee: Rakesh R
>Priority: Critical
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2247-01.patch, ZOOKEEPER-2247-02.patch, 
> ZOOKEEPER-2247-03.patch, ZOOKEEPER-2247-04.patch, ZOOKEEPER-2247-05.patch, 
> ZOOKEEPER-2247-06.patch, ZOOKEEPER-2247-07.patch, ZOOKEEPER-2247-09.patch, 
> ZOOKEEPER-2247-10.patch, ZOOKEEPER-2247-11.patch, ZOOKEEPER-2247-12.patch, 
> ZOOKEEPER-2247-13.patch, ZOOKEEPER-2247-14.patch, ZOOKEEPER-2247-15.patch, 
> ZOOKEEPER-2247-b3.5.patch, ZOOKEEPER-2247-br-3.4.patch
>
>
> Zookeeper service becomes unavailable when leader fails to write transaction 
> log. Bellow are the exceptions
> {code}
> 2015-08-14 15:41:18,556 [myid:100] - ERROR 
> [SyncThread:100:ZooKeeperCriticalThread@48] - Severe unrecoverable error, 
> from thread : SyncThread:100
> java.io.IOException: Input/output error
>   at sun.nio.ch.FileDispatcherImpl.force0(Native Method)
>   at sun.nio.ch.FileDispatcherImpl.force(FileDispatcherImpl.java:76)
>   at sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:376)
>   at 
> org.apache.zookeeper.server.persistence.FileTxnLog.commit(FileTxnLog.java:331)
>   at 
> org.apache.zookeeper.server.persistence.FileTxnSnapLog.commit(FileTxnSnapLog.java:380)
>   at org.apache.zookeeper.server.ZKDatabase.commit(ZKDatabase.java:563)
>   at 
> org.apache.zookeeper.server.SyncRequestProcessor.flush(SyncRequestProcessor.java:178)
>   at 
> org.apache.zookeeper.server.SyncRequestProcessor.run(SyncRequestProcessor.java:113)
> 2015-08-14 15:41:18,559 [myid:100] - INFO  
> [SyncThread:100:ZooKeeperServer$ZooKeeperServerListenerImpl@500] - Thread 
> SyncThread:100 exits, error code 1
> 2015-08-14 15:41:18,559 [myid:100] - INFO  
> [SyncThread:100:ZooKeeperServer@523] - shutting down
> 2015-08-14 15:41:18,560 [myid:100] - INFO  
> [SyncThread:100:SessionTrackerImpl@232] - Shutting down
> 2015-08-14 15:41:18,560 [myid:100] - INFO  
> [SyncThread:100:LeaderRequestProcessor@77] - Shutting down
> 2015-08-14 15:41:18,560 [myid:100] - INFO  
> [SyncThread:100:PrepRequestProcessor@1035] - Shutting down
> 2015-08-14 15:41:18,560 [myid:100] - INFO  
> [SyncThread:100:ProposalRequestProcessor@88] - Shutting down
> 2015-08-14 15:41:18,561 [myid:100] - INFO  
> [SyncThread:100:CommitProcessor@356] - Shutting down
> 2015-08-14 15:41:18,561 [myid:100] - INFO  
> [CommitProcessor:100:CommitProcessor@191] - CommitProcessor exited loop!
> 2015-08-14 15:41:18,562 [myid:100] - INFO  
> [SyncThread:100:Leader$ToBeAppliedRequestProcessor@915] - Shutting down
> 2015-08-14 15:41:18,562 [myid:100] - INFO  
> [SyncThread:100:FinalRequestProcessor@646] - shutdown of request processor 
> complete
> 2015-08-14 15:41:18,562 [myid:100] - INFO  
> [SyncThread:100:SyncRequestProcessor@191] - Shutting down
> 2015-08-14 15:41:18,563 [myid:100] - INFO  [ProcessThread(sid:100 
> cport:-1)::PrepRequestProcessor@159] - PrepRequestProcessor exited loop!
> {code}
> After this exception Leader server still remains leader. After this non 
> recoverable exception the leader should go down and let other followers 
> become leader.



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

[GitHub] zookeeper pull request: ZOOKEEPER-2247 Zookeeper service becomes u...

[arshadmohammad]

Github user arshadmohammad closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (ZOOKEEPER-2384) Support atomic increment / decrement of znode value

[Ted Yu (JIRA)]

Ted Yu created ZOOKEEPER-2384:
-

 Summary: Support atomic increment / decrement of znode value
 Key: ZOOKEEPER-2384
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2384
 Project: ZooKeeper
  Issue Type: Improvement
Reporter: Ted Yu


Use case is to store reference count (integer type) in znode.

It is desirable to provide support for atomic increment / decrement of the 
znode value.

Suggestion from Flavio:

you can read the znode, keep the version of the znode, update the value, write 
back conditionally. The condition for the setData operation to succeed is that 
the version is the same that it read

While the above is feasible, developer has to implement retry logic 
him/herself. It is not easy to combine increment / decrement with other 
operations using multi.



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

Failed: ZOOKEEPER-2141 PreCommit Build #3094

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 377394 lines...]
 [exec] 
 [exec] +1 tests included.  The patch appears to include 3 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 appears to introduce 3 new Findbugs 
(version 2.0.3) warnings.
 [exec] 
 [exec] -1 release audit.  The applied patch generated 2 release audit 
warnings (more than the trunk's current 0 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/3094//testReport/
 [exec] Release audit warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3094//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3094//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3094//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] 7cd3da8f7eecd8537522b51b24b416405345603f 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:1646:
 exec returned: 2

Total time: 13 minutes 42 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-2141
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



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

[jira] [Commented] (ZOOKEEPER-2141) ACL cache in DataTree never removes entries

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-2141:
--

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

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

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

+1 javadoc.  The javadoc tool 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 appears to introduce 3 new Findbugs (version 2.0.3) 
warnings.

-1 release audit.  The applied patch generated 2 release audit warnings 
(more than the trunk's current 0 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/3094//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3094//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3094//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3094//console

This message is automatically generated.

> ACL cache in DataTree never removes entries
> ---
>
> Key: ZOOKEEPER-2141
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2141
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Karol Dudzinski
>Assignee: Karol Dudzinski
> Attachments: ZOOKEEPER-2141.patch, ZOOKEEPER-2141.patch
>
>
> The problem and potential solutions are discussed in 
> http://mail-archives.apache.org/mod_mbox/zookeeper-user/201502.mbox/browser
> I will attach a proposed patch in due course.



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

[jira] [Commented] (ZOOKEEPER-2266) Integrate JaCoCo Coverage Library

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-2266:
--

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12792196/ZOOKEEPER-2266-v4.patch
  against trunk revision 1733679.

+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 failed core unit tests.

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

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

This message is automatically generated.

> Integrate JaCoCo Coverage Library
> -
>
> Key: ZOOKEEPER-2266
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2266
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: tests
>Reporter: Akihiro Suda
>Assignee: Akihiro Suda
>Priority: Minor
> Attachments: ZOOKEEPER-2266-v1.patch, ZOOKEEPER-2266-v2.patch, 
> ZOOKEEPER-2266-v3.patch, ZOOKEEPER-2266-v4.patch, jacoco-report-example.zip
>
>
> I would like to propose integration of 
> [JaCoCo|http://www.eclemma.org/jacoco/] coverage library with ZooKeeper.
> h4. Purposes
>  - To find poorly covered methods, and improve JUnit testcases to cover them
>  - To estimate causes of flaky testcases (e.g. ZOOKEEPER-2080, 
> ZOOKEEPER-2252, ZOOKEEPER-1868) by comparing reports from succeeded 
> experiments and failed ones (I'm recently interested in how we can 
> systematically realize this.)
> h4. Advantages of JaCoCo
>  - Support recent JDKs (including JDK 8)
>  - Low overhead
>  - Released under EPL
>  -- Note: cobertura has been removed from the code base because it is 
> released under GPL ( ZOOKEEPER-75, 
> http://www.apache.org/legal/resolved.html#category-x )
> h4. Usage
> {panel}
> $ ant test #(plus optionally, -Dtestcase=.. -Dtest.method=..)
> $ ant jacoco-report
> $ x-www-browser build/test/jacoco/reports/index.html &
> {panel}
> Example: jacoco-report-example.zip
> h4. Possible Future Work
> - Integrate to Jenkins buildbot so that we can check coverage after each of 
> builds



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

Failed: ZOOKEEPER-2266 PreCommit Build #3093

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 366960 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 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/3093//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3093//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3093//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] 8bce609b5f05b458f16fcb76b2dc6750ef656770 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:1646:
 exec returned: 2

Total time: 45 minutes 38 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Compressed 542.59 KB of artifacts by 41.3% relative to #3091
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-2266
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentObserverIsParticipantInNewConfig

Error Message:
waiting for server 2 being up

Stack Trace:
junit.framework.AssertionFailedError: waiting for server 2 being up
at 
org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentObserverIsParticipantInNewConfig(ReconfigRecoveryTest.java:529)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

[jira] [Commented] (ZOOKEEPER-2380) Deadlock while shutting down the zookeeper

[Rakesh R (JIRA)]

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

Rakesh R commented on ZOOKEEPER-2380:
-

Thank you [~arshad.mohammad] for the updates. Since this is a critical issue, 
its good to back with unit tests. I know it is not that simple, but could you 
check any chance to write unit tests by stubbing {{MockSyncRequestProcessor 
extends SyncRequestProcessor}} or welcome some other approach.

> Deadlock while shutting down the zookeeper
> --
>
> Key: ZOOKEEPER-2380
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2380
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2380-01.patch, ZOOKEEPER-2380-02.patch
>
>
> Zookeeper enters into deadlock while shutting down itself, thus making 
> zookeeper service unavailable as deadlocked server is a leader. Here is the 
> thread dump:
> {code}
> "QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled)" #25 prio=5 
> os_prio=0 tid=0x7fbc502a6800 nid=0x834 in Object.wait() 
> [0x7fbc4d9a8000]  java.lang.Thread.State: WAITING (on object monitor) 
>  at java.lang.Object.wait(Native Method)  at 
> java.lang.Thread.join(Thread.java:1245)  - locked <
> 0xfeb78000> (a org.apache.zookeeper.server.SyncRequestProcessor)  
> at java.lang.Thread.join(Thread.java:1319)  at 
> org.apache.zookeeper.server.SyncRequestProcessor.shutdown(SyncRequestProcessor.java:196)
>   at 
> org.apache.zookeeper.server.quorum.ProposalRequestProcessor.shutdown(ProposalRequestProcessor.java:90)
>   at 
> org.apache.zookeeper.server.PrepRequestProcessor.shutdown(PrepRequestProcessor.java:1016)
>   at 
> org.apache.zookeeper.server.quorum.LeaderRequestProcessor.shutdown(LeaderRequestProcessor.java:78)
>   at 
> org.apache.zookeeper.server.ZooKeeperServer.shutdown(ZooKeeperServer.java:561)
>   - locked <
> 0xfeb61e20> (a 
> org.apache.zookeeper.server.quorum.LeaderZooKeeperServer)  at 
> org.apache.zookeeper.server.quorum.QuorumZooKeeperServer.shutdown(QuorumZooKeeperServer.java:169)
>   - locked <
> 0xfeb61e20> (a 
> org.apache.zookeeper.server.quorum.LeaderZooKeeperServer)  at 
> org.apache.zookeeper.server.quorum.LeaderZooKeeperServer.shutdown(LeaderZooKeeperServer.java:102)
>   - locked <
> 0xfeb61e20> (a 
> org.apache.zookeeper.server.quorum.LeaderZooKeeperServer)  at 
> org.apache.zookeeper.server.quorum.Leader.shutdown(Leader.java:637)  at 
> org.apache.zookeeper.server.quorum.Leader.lead(Leader.java:590)  - locked 
> <
> 0xfeb781a0> (a org.apache.zookeeper.server.quorum.Leader)  at 
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:1108)
> "SyncThread:1" #46 prio=5 os_prio=0 tid=0x7fbc5848f000 nid=0x867 waiting 
> for monitor entry [0x7fbc4ca9]  java.lang.Thread.State: BLOCKED 
> (on object monitor)  at 
> org.apache.zookeeper.server.quorum.Leader.processAck(Leader.java:784)  - 
> waiting to lock <0xfeb781a0> (a 
> org.apache.zookeeper.server.quorum.Leader)  at 
> org.apache.zookeeper.server.quorum.AckRequestProcessor.processRequest(AckRequestProcessor.java:46)
>   at 
> org.apache.zookeeper.server.SyncRequestProcessor.flush(SyncRequestProcessor.java:183)
>   at 
> org.apache.zookeeper.server.SyncRequestProcessor.run(SyncRequestProcessor.java:113)
> {code}
> Leader.lead() calls shutdown() from the synchronized block, it acquired lock 
> on Leader.java instance
> {code}
> while (true) {
> synchronized (this) {
> long start = Time.currentElapsedTime();
>   .
> {code}
> In the shutdown flow SyncThread is trying to acquire lock on the same 
> Leader.java instance. 
> Leader thread acquired lock and waiting for SyncThread shutdown. SyncThread 
> waiting for the lock to complete its shutdown.  This is how ZooKeeper entered 
> into deadlock



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

[jira] [Commented] (ZOOKEEPER-2380) Deadlock while shutting down the zookeeper

[Rakesh R (JIRA)]

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

Rakesh R commented on ZOOKEEPER-2380:
-

I'm just adding a point to avoid confusions, this issue has no relation with 
the ZOOKEEPER-2347. The call sequence or the execution path is completely 
different for both these issues.

> Deadlock while shutting down the zookeeper
> --
>
> Key: ZOOKEEPER-2380
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2380
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2380-01.patch, ZOOKEEPER-2380-02.patch
>
>
> Zookeeper enters into deadlock while shutting down itself, thus making 
> zookeeper service unavailable as deadlocked server is a leader. Here is the 
> thread dump:
> {code}
> "QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled)" #25 prio=5 
> os_prio=0 tid=0x7fbc502a6800 nid=0x834 in Object.wait() 
> [0x7fbc4d9a8000]  java.lang.Thread.State: WAITING (on object monitor) 
>  at java.lang.Object.wait(Native Method)  at 
> java.lang.Thread.join(Thread.java:1245)  - locked <
> 0xfeb78000> (a org.apache.zookeeper.server.SyncRequestProcessor)  
> at java.lang.Thread.join(Thread.java:1319)  at 
> org.apache.zookeeper.server.SyncRequestProcessor.shutdown(SyncRequestProcessor.java:196)
>   at 
> org.apache.zookeeper.server.quorum.ProposalRequestProcessor.shutdown(ProposalRequestProcessor.java:90)
>   at 
> org.apache.zookeeper.server.PrepRequestProcessor.shutdown(PrepRequestProcessor.java:1016)
>   at 
> org.apache.zookeeper.server.quorum.LeaderRequestProcessor.shutdown(LeaderRequestProcessor.java:78)
>   at 
> org.apache.zookeeper.server.ZooKeeperServer.shutdown(ZooKeeperServer.java:561)
>   - locked <
> 0xfeb61e20> (a 
> org.apache.zookeeper.server.quorum.LeaderZooKeeperServer)  at 
> org.apache.zookeeper.server.quorum.QuorumZooKeeperServer.shutdown(QuorumZooKeeperServer.java:169)
>   - locked <
> 0xfeb61e20> (a 
> org.apache.zookeeper.server.quorum.LeaderZooKeeperServer)  at 
> org.apache.zookeeper.server.quorum.LeaderZooKeeperServer.shutdown(LeaderZooKeeperServer.java:102)
>   - locked <
> 0xfeb61e20> (a 
> org.apache.zookeeper.server.quorum.LeaderZooKeeperServer)  at 
> org.apache.zookeeper.server.quorum.Leader.shutdown(Leader.java:637)  at 
> org.apache.zookeeper.server.quorum.Leader.lead(Leader.java:590)  - locked 
> <
> 0xfeb781a0> (a org.apache.zookeeper.server.quorum.Leader)  at 
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:1108)
> "SyncThread:1" #46 prio=5 os_prio=0 tid=0x7fbc5848f000 nid=0x867 waiting 
> for monitor entry [0x7fbc4ca9]  java.lang.Thread.State: BLOCKED 
> (on object monitor)  at 
> org.apache.zookeeper.server.quorum.Leader.processAck(Leader.java:784)  - 
> waiting to lock <0xfeb781a0> (a 
> org.apache.zookeeper.server.quorum.Leader)  at 
> org.apache.zookeeper.server.quorum.AckRequestProcessor.processRequest(AckRequestProcessor.java:46)
>   at 
> org.apache.zookeeper.server.SyncRequestProcessor.flush(SyncRequestProcessor.java:183)
>   at 
> org.apache.zookeeper.server.SyncRequestProcessor.run(SyncRequestProcessor.java:113)
> {code}
> Leader.lead() calls shutdown() from the synchronized block, it acquired lock 
> on Leader.java instance
> {code}
> while (true) {
> synchronized (this) {
> long start = Time.currentElapsedTime();
>   .
> {code}
> In the shutdown flow SyncThread is trying to acquire lock on the same 
> Leader.java instance. 
> Leader thread acquired lock and waiting for SyncThread shutdown. SyncThread 
> waiting for the lock to complete its shutdown.  This is how ZooKeeper entered 
> into deadlock



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

[GitHub] zookeeper pull request: Update zookeeper.h

[itayB]

GitHub user itayB opened a pull request:

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

Update zookeeper.h

Typo fix (Comments)

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

$ git pull https://github.com/itayB/zookeeper trunk

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

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

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

This closes #56


commit 7091ad9db2d2a046eaa83cd9acdf1f2d81a40999
Author: Itay 
Date:   2016-03-09T10:21:00Z

Update zookeeper.h

Typo fix




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (ZOOKEEPER-2141) ACL cache in DataTree never removes entries

[Adam Milne-Smith (JIRA)]

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

Adam Milne-Smith updated ZOOKEEPER-2141:

Attachment: ZOOKEEPER-2141.patch

Attaching trunk patch

> ACL cache in DataTree never removes entries
> ---
>
> Key: ZOOKEEPER-2141
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2141
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Karol Dudzinski
>Assignee: Karol Dudzinski
> Attachments: ZOOKEEPER-2141.patch, ZOOKEEPER-2141.patch
>
>
> The problem and potential solutions are discussed in 
> http://mail-archives.apache.org/mod_mbox/zookeeper-user/201502.mbox/browser
> I will attach a proposed patch in due course.



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