[jira] [Commented] (ZOOKEEPER-2317) Non-OSGi compatible version

[Sachin (JIRA)]

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

Sachin commented on ZOOKEEPER-2317:
---

Did some change in build.xml and repackaged it from alpha to 3.5.1.1
We are testing it . Let me know how i can attached build.xml in this issue.

> Non-OSGi compatible version
> ---
>
> Key: ZOOKEEPER-2317
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2317
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: build
>Affects Versions: 3.5.1
> Environment: Karaf OSGi container
>Reporter: Markus Tippmann
>Priority: Blocker
> Fix For: 3.5.3
>
>
> Bundle cannot be deployed to OSGi container.
> Manifest version is not OSGi compatible.
> Instead of using 3.5.1-alpha, manifest needs to contain 3.5.1.alpha



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

Re: PreCommitBuild - Adding comment to Jira

[Rakesh Radhakrishnan]

Thanks Michael for reporting the infra issue. Lets us watch the progress.

Rakesh

On Tue, Jul 26, 2016 at 12:25 AM, Michael Han  wrote:

> Filed https://issues.apache.org/jira/browse/INFRA-12327.
>
> On Mon, Jul 25, 2016 at 11:15 AM, Patrick Hunt  wrote:
>
> > I'd recommend you start by opening an INFRA jira against Jenkins. The
> INFRA
> > folks are usually pretty quick to address.
> >
> > Patrick
> >
> > On Mon, Jul 25, 2016 at 10:26 AM, Flavio Junqueira 
> wrote:
> >
> > > I've only logged on to the jenkins console, I've never tried to access
> > the
> > > machine itself.
> > >
> > > -Flavio
> > >
> > > > On 25 Jul 2016, at 17:57, Michael Han  wrote:
> > > >
> > > > Actually the issue might not be transient, just noticed that although
> > > > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3284/
> > succeeds,
> > > the
> > > > log still said permission denied on invoking test-patch.sh. Not sure
> > why
> > > > this build is green given other pre-commit build failed with same
> cause
> > > > (for example
> > > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3283/).
> > > >
> > > > Does anyone have access to the build bot so we can investigate and
> fix
> > > > this, or Apache Infra team can take care of this?
> > > >
> > > > On Mon, Jul 25, 2016 at 9:49 AM, Michael Han 
> > wrote:
> > > >
> > > >> The issue might be transient, as this pre-commit build works this
> > > morning:
> > > >> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3284/
> > > >>
> > > >> As a side note there are a couple of other failures while triage the
> > > build
> > > >> today, looks like these are infrastructure issues:
> > > >>
> > > >> https://builds.apache.org/job/ZooKeeper-trunk-solaris/1240/
> > > >> BUILD FAILED
> > > >> /zonestorage/hudson_solaris/home/hudson/hudson-slave/
> > > >> workspace/ZooKeeper-trunk-solaris/trunk/build.xml:324: Execute
> failed:
> > > >> java.io.IOException: Cannot run program "sh": error=12, Not enough
> > space
> > > >>
> > > >> https://builds.apache.org/job/ZooKeeper-trunk/3005/
> > > >> mv: cannot stat 'build/*.tar.gz': No such file or directory
> > > >> mv: cannot stat 'build/*.jar': No such file or directory
> > > >> mv: cannot stat 'build/test/findbugs': No such file or directory
> > > >> mv: cannot stat 'build/docs/api': No such file or directory
> > > >>
> > > >> On Mon, Jul 25, 2016 at 7:55 AM, Rakesh Radhakrishnan <
> > > rake...@apache.org>
> > > >> wrote:
> > > >>
> > > >>> Anybody has done changes to the build machine or test
> infrastructure?
> > > Is
> > > >>> this something simple issue, which can be resolved by giving
> > > permission to
> > > >>> those directories?
> > > >>>
> > > >>> +Rakesh
> > > >>>
> > > >>> On Sun, Jul 24, 2016 at 9:02 PM, Flavio Junqueira 
> > > wrote:
> > > >>>
> > >  The console output says this:
> > > 
> > >  [exec]
> > > 
> > > >>>
> > >
> >
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
> > >  line 558: /home/jenkins/tools/jiracli/latest/jira: Permission
> denied
> > >  [exec]
> > > 
> > > >>>
> > >
> >
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
> > >  line 559: /home/jenkins/tools/jiracli/latest/jira: Permission
> denied
> > > 
> > >  I'm not sure whether this is transient or anyone has changed the
> > > config.
> > > 
> > >  -Flavio
> > > 
> > > > On 24 Jul 2016, at 16:12, Rakesh Radhakrishnan <
> rake...@apache.org
> > >
> > >  wrote:
> > > >
> > > > Hi,
> > > >
> > > > It looks like "Precommit build" is triggered but failed to add
> > > >>> comments
> > >  to
> > > > Jira. Appreciate your help. Thanks!
> > > >
> > > > References:-
> > > > ZOOKEEPER-2479 ->
> > > > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3283/
> > > > ZOOKEEPER-2172 ->
> > > > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3282/
> > > >
> > > >
> > > ==
> > > >
> > > >[exec] Adding comment to Jira.
> > > >[exec]
> > > 
> > ==
> > > >[exec]
> > > 
> > ==
> > > >[exec]
> > > >[exec]
> > > >[exec]
> > > >[exec]
> > > >[exec]
> > > 
> > ==
> > > >[exec]
> > > 
> > ==
> > > >[exec] Finished build.
> > > >[exec]
> > > 
> > ==
> > > >
> > > >
> > > > Thanks,
> > > 

ZooKeeper-trunk - Build # 3006 - Still Failing

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1497 lines...]
 [exec] 
 [exec] init-proxy:
 [exec] 
 [exec] fetch-skins-descriptors:
 [exec] 
 [exec] fetch-skin:
 [exec] 
 [exec] unpack-skins:
 [exec] 
 [exec] init-skins:
 [exec] 
 [exec] fetch-plugins-descriptors:
 [exec] Copying 1 file to 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/src/docs/build/tmp
 [exec] Copying 1 file to 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/src/docs/build/tmp
 [exec] Fetching plugins descriptor: 
http://forrest.apache.org/plugins/plugins.xml
 [exec] Getting: http://forrest.apache.org/plugins/plugins.xml
 [exec] To: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/src/docs/build/tmp/plugins-1.xml
 [exec] local file date : Tue Nov 18 13:39:59 UTC 2014
 [exec] Not modified - so not downloaded
 [exec] Fetching plugins descriptor: 
http://forrest.apache.org/plugins/whiteboard-plugins.xml
 [exec] Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml
 [exec] To: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/src/docs/build/tmp/plugins-2.xml
 [exec] local file date : Tue Nov 18 13:39:59 UTC 2014
 [exec] Not modified - so not downloaded
 [exec] Plugin list loaded from 
http://forrest.apache.org/plugins/plugins.xml.
 [exec] Plugin list loaded from 
http://forrest.apache.org/plugins/whiteboard-plugins.xml.
 [exec] 
 [exec] init-plugins:
 [exec] 
 [exec] BUILD FAILED
 [exec] /home/jenkins/tools/forrest/latest/main/targets/plugins.xml:374: 
Directory /home/jenkins/tools/forrest/latest/build/plugins creation was not 
successful for an unknown reason
 [exec] 
 [exec] Total time: 1 second

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build.xml:468: exec 
returned: 1

Total time: 2 seconds
mv: cannot stat 'build/*.tar.gz': No such file or directory
mv: cannot stat 'build/*.jar': No such file or directory
mv: cannot stat 'build/test/findbugs': No such file or directory
mv: cannot stat 'build/docs/api': No such file or directory
Build Failed
Build step 'Execute shell' marked build as failure
[FINDBUGS] Skipping publisher since build result is FAILURE
[WARNINGS] Skipping publisher since build result is FAILURE
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording fingerprints
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
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Publishing Javadoc
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
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



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

[jira] [Commented] (ZOOKEEPER-2080) ReconfigRecoveryTest fails intermittently

[Michael Han (JIRA)]

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

Michael Han commented on ZOOKEEPER-2080:


[~shralex] Thanks for all the feedback so far:). I am trying to find a 
different solution today (my previous patch does not fix root cause, it is a 
workaround only.). I've tried another solution by [returning 
here|https://github.com/apache/zookeeper/blob/3c37184e83a3e68b73544cebccf9388eea26f523/src/java/main/org/apache/zookeeper/server/quorum/QuorumCnxManager.java#L475]
 before locking on QuorumPeer if the 'shutdown' flag is set to true, and it 
does not always work (failed my pressure test). I'll try finding another 
solution.

> ReconfigRecoveryTest fails intermittently
> -
>
> Key: ZOOKEEPER-2080
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2080
> Project: ZooKeeper
>  Issue Type: Sub-task
>Reporter: Ted Yu
>Assignee: Michael Han
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2080.patch, 
> jacoco-ZOOKEEPER-2080.unzip-grows-to-70MB.7z, repro-20150816.log, 
> threaddump.log
>
>
> I got the following test failure on MacBook with trunk code:
> {code}
> Testcase: testCurrentObserverIsParticipantInNewConfig took 93.628 sec
>   FAILED
> waiting for server 2 being up
> 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:52)
> {code}



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

[jira] [Commented] (ZOOKEEPER-2080) ReconfigRecoveryTest fails intermittently

[Michael Han (JIRA)]

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

Michael Han commented on ZOOKEEPER-2080:


ZOOKEEPER-2488 to track this.

> ReconfigRecoveryTest fails intermittently
> -
>
> Key: ZOOKEEPER-2080
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2080
> Project: ZooKeeper
>  Issue Type: Sub-task
>Reporter: Ted Yu
>Assignee: Michael Han
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2080.patch, 
> jacoco-ZOOKEEPER-2080.unzip-grows-to-70MB.7z, repro-20150816.log, 
> threaddump.log
>
>
> I got the following test failure on MacBook with trunk code:
> {code}
> Testcase: testCurrentObserverIsParticipantInNewConfig took 93.628 sec
>   FAILED
> waiting for server 2 being up
> 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:52)
> {code}



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

[jira] [Created] (ZOOKEEPER-2488) Unsynchronized access to shuttingDownLE in QuorumPeer

[Michael Han (JIRA)]

Michael Han created ZOOKEEPER-2488:
--

 Summary: Unsynchronized access to shuttingDownLE in QuorumPeer
 Key: ZOOKEEPER-2488
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2488
 Project: ZooKeeper
  Issue Type: Bug
  Components: server
Affects Versions: 3.5.2
Reporter: Michael Han
 Fix For: 3.5.3, 3.6.0


Access to shuttingDownLE in QuorumPeer is not synchronized here:

https://github.com/apache/zookeeper/blob/3c37184e83a3e68b73544cebccf9388eea26f523/src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java#L1066
https://github.com/apache/zookeeper/blob/3c37184e83a3e68b73544cebccf9388eea26f523/src/java/main/org/

The access should be synchronized as the same variable might be accessed 
in QuormPeer::restartLeaderElection, which is synchronized.



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

ZooKeeper_branch34_jdk8 - Build # 642 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_jdk8/642/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 216688 lines...]
[junit] 2016-07-25 23:06:02,566 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-07-25 23:06:02,566 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-07-25 23:06:02,566 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2016-07-25 23:06:02,566 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-07-25 23:06:02,567 [myid:] - INFO  [main:ZooKeeperServer@469] 
- shutting down
[junit] 2016-07-25 23:06:02,567 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-07-25 23:06:02,567 [myid:] - INFO  
[main:PrepRequestProcessor@765] - Shutting down
[junit] 2016-07-25 23:06:02,567 [myid:] - INFO  
[main:SyncRequestProcessor@209] - Shutting down
[junit] 2016-07-25 23:06:02,567 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-07-25 23:06:02,567 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited!
[junit] 2016-07-25 23:06:02,568 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2016-07-25 23:06:02,568 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-07-25 23:06:02,569 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-07-25 23:06:02,570 [myid:] - INFO  [main:ClientBase@443] - 
STARTING server
[junit] 2016-07-25 23:06:02,570 [myid:] - INFO  [main:ClientBase@364] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-07-25 23:06:02,571 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-07-25 23:06:02,571 [myid:] - INFO  [main:ClientBase@339] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-07-25 23:06:02,571 [myid:] - INFO  [main:ZooKeeperServer@170] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/branch-3.4/build/test/tmp/test4468626419027260476.junit.dir/version-2
 snapdir 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/branch-3.4/build/test/tmp/test4468626419027260476.junit.dir/version-2
[junit] 2016-07-25 23:06:02,575 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-07-25 23:06:02,576 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:33401
[junit] 2016-07-25 23:06:02,576 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:33401
[junit] 2016-07-25 23:06:02,577 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-07-25 23:06:02,577 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:33401 (no session established for client)
[junit] 2016-07-25 23:06:02,578 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-07-25 23:06:02,581 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-07-25 23:06:02,581 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-07-25 23:06:02,581 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-07-25 23:06:02,582 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-07-25 23:06:02,582 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 5207
[junit] 2016-07-25 23:06:02,582 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-07-25 23:06:02,583 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-07-25 23:06:02,583 [myid:] - INFO  [main:ClientBase@520] - 
tearDown starting
[junit] 2016-07-25 23:06:02,651 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x156244ed87f closed
[junit] 2016-07-25 23:06:02,651 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2016-07-25 23:06:02,651 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x156244ed87f
[junit] 2016-07-25 23:06:02,651 [myid:] - INFO  

[jira] [Commented] (ZOOKEEPER-2469) infinite loop in ZK re-login

[Sergey Shelukhin (JIRA)]

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

Sergey Shelukhin commented on ZOOKEEPER-2469:
-

ping for a binding +1/commit? ;)

> infinite loop in ZK re-login
> 
>
> Key: ZOOKEEPER-2469
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2469
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: ZOOKEEPER-2469.01.patch, ZOOKEEPER-2469.02.patch, 
> ZOOKEEPER-2469.03.patch, ZOOKEEPER-2469.patch
>
>
> {noformat}
> int retry = 1;
> while (retry >= 0) {
> try {
> reLogin();
> break;
> } catch (LoginException le) {
> if (retry > 0) {
> --retry;
> // sleep for 10 seconds.
> try {
> Thread.sleep(10 * 1000);
> } catch (InterruptedException e) {
> LOG.error("Interrupted during login 
> retry after LoginException:", le);
> throw le;
> }
> } else {
> LOG.error("Could not refresh TGT for 
> principal: " + principal + ".", le);
> }
> }
> }
> {noformat}
> will retry forever. Should return like the one above



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

[jira] [Commented] (ZOOKEEPER-2080) ReconfigRecoveryTest fails intermittently

[Michael Han (JIRA)]

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

Michael Han commented on ZOOKEEPER-2080:


bq. Which isn't synchronized now, but probably should be.
Yeah, this looks like a bug to me since all other accesses to the 
'shuttingDownLE' flag is synchronized except these ones:
https://github.com/apache/zookeeper/blob/3c37184e83a3e68b73544cebccf9388eea26f523/src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java#L1066
https://github.com/apache/zookeeper/blob/3c37184e83a3e68b73544cebccf9388eea26f523/src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java#L1083



> ReconfigRecoveryTest fails intermittently
> -
>
> Key: ZOOKEEPER-2080
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2080
> Project: ZooKeeper
>  Issue Type: Sub-task
>Reporter: Ted Yu
>Assignee: Michael Han
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2080.patch, 
> jacoco-ZOOKEEPER-2080.unzip-grows-to-70MB.7z, repro-20150816.log, 
> threaddump.log
>
>
> I got the following test failure on MacBook with trunk code:
> {code}
> Testcase: testCurrentObserverIsParticipantInNewConfig took 93.628 sec
>   FAILED
> waiting for server 2 being up
> 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:52)
> {code}



--
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

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira commented on ZOOKEEPER-2247:
-

Is this PR updated, [~rakeshr]:

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

> 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.3, 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-16.patch, ZOOKEEPER-2247-17.patch, ZOOKEEPER-2247-18.patch, 
> ZOOKEEPER-2247-19.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)

Re: PreCommitBuild - Adding comment to Jira

[Michael Han]

Filed https://issues.apache.org/jira/browse/INFRA-12327.

On Mon, Jul 25, 2016 at 11:15 AM, Patrick Hunt  wrote:

> I'd recommend you start by opening an INFRA jira against Jenkins. The INFRA
> folks are usually pretty quick to address.
>
> Patrick
>
> On Mon, Jul 25, 2016 at 10:26 AM, Flavio Junqueira  wrote:
>
> > I've only logged on to the jenkins console, I've never tried to access
> the
> > machine itself.
> >
> > -Flavio
> >
> > > On 25 Jul 2016, at 17:57, Michael Han  wrote:
> > >
> > > Actually the issue might not be transient, just noticed that although
> > > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3284/
> succeeds,
> > the
> > > log still said permission denied on invoking test-patch.sh. Not sure
> why
> > > this build is green given other pre-commit build failed with same cause
> > > (for example
> > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3283/).
> > >
> > > Does anyone have access to the build bot so we can investigate and fix
> > > this, or Apache Infra team can take care of this?
> > >
> > > On Mon, Jul 25, 2016 at 9:49 AM, Michael Han 
> wrote:
> > >
> > >> The issue might be transient, as this pre-commit build works this
> > morning:
> > >> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3284/
> > >>
> > >> As a side note there are a couple of other failures while triage the
> > build
> > >> today, looks like these are infrastructure issues:
> > >>
> > >> https://builds.apache.org/job/ZooKeeper-trunk-solaris/1240/
> > >> BUILD FAILED
> > >> /zonestorage/hudson_solaris/home/hudson/hudson-slave/
> > >> workspace/ZooKeeper-trunk-solaris/trunk/build.xml:324: Execute failed:
> > >> java.io.IOException: Cannot run program "sh": error=12, Not enough
> space
> > >>
> > >> https://builds.apache.org/job/ZooKeeper-trunk/3005/
> > >> mv: cannot stat 'build/*.tar.gz': No such file or directory
> > >> mv: cannot stat 'build/*.jar': No such file or directory
> > >> mv: cannot stat 'build/test/findbugs': No such file or directory
> > >> mv: cannot stat 'build/docs/api': No such file or directory
> > >>
> > >> On Mon, Jul 25, 2016 at 7:55 AM, Rakesh Radhakrishnan <
> > rake...@apache.org>
> > >> wrote:
> > >>
> > >>> Anybody has done changes to the build machine or test infrastructure?
> > Is
> > >>> this something simple issue, which can be resolved by giving
> > permission to
> > >>> those directories?
> > >>>
> > >>> +Rakesh
> > >>>
> > >>> On Sun, Jul 24, 2016 at 9:02 PM, Flavio Junqueira 
> > wrote:
> > >>>
> >  The console output says this:
> > 
> >  [exec]
> > 
> > >>>
> >
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
> >  line 558: /home/jenkins/tools/jiracli/latest/jira: Permission denied
> >  [exec]
> > 
> > >>>
> >
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
> >  line 559: /home/jenkins/tools/jiracli/latest/jira: Permission denied
> > 
> >  I'm not sure whether this is transient or anyone has changed the
> > config.
> > 
> >  -Flavio
> > 
> > > On 24 Jul 2016, at 16:12, Rakesh Radhakrishnan  >
> >  wrote:
> > >
> > > Hi,
> > >
> > > It looks like "Precommit build" is triggered but failed to add
> > >>> comments
> >  to
> > > Jira. Appreciate your help. Thanks!
> > >
> > > References:-
> > > ZOOKEEPER-2479 ->
> > > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3283/
> > > ZOOKEEPER-2172 ->
> > > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3282/
> > >
> > >
> > ==
> > >
> > >[exec] Adding comment to Jira.
> > >[exec]
> > 
> ==
> > >[exec]
> > 
> ==
> > >[exec]
> > >[exec]
> > >[exec]
> > >[exec]
> > >[exec]
> > 
> ==
> > >[exec]
> > 
> ==
> > >[exec] Finished build.
> > >[exec]
> > 
> ==
> > >
> > >
> > > Thanks,
> > > Rakesh
> > 
> > 
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> Cheers
> > >> Michael.
> > >>
> > >
> > >
> > >
> > > --
> > > Cheers
> > > Michael.
> >
> >
>



-- 
Cheers
Michael.

[jira] [Commented] (ZOOKEEPER-2317) Non-OSGi compatible version

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira commented on ZOOKEEPER-2317:
-

[~sachin_garg] given that there is no one assigned, I'd think that there is no 
one working on it. If you're willing to provide a patch, it'd greatly help us. 
would you be ok if I assign it to you?

> Non-OSGi compatible version
> ---
>
> Key: ZOOKEEPER-2317
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2317
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: build
>Affects Versions: 3.5.1
> Environment: Karaf OSGi container
>Reporter: Markus Tippmann
>Priority: Blocker
> Fix For: 3.5.3
>
>
> Bundle cannot be deployed to OSGi container.
> Manifest version is not OSGi compatible.
> Instead of using 3.5.1-alpha, manifest needs to contain 3.5.1.alpha



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

Re: PreCommitBuild - Adding comment to Jira

[Patrick Hunt]

I'd recommend you start by opening an INFRA jira against Jenkins. The INFRA
folks are usually pretty quick to address.

Patrick

On Mon, Jul 25, 2016 at 10:26 AM, Flavio Junqueira  wrote:

> I've only logged on to the jenkins console, I've never tried to access the
> machine itself.
>
> -Flavio
>
> > On 25 Jul 2016, at 17:57, Michael Han  wrote:
> >
> > Actually the issue might not be transient, just noticed that although
> > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3284/ succeeds,
> the
> > log still said permission denied on invoking test-patch.sh. Not sure why
> > this build is green given other pre-commit build failed with same cause
> > (for example
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3283/).
> >
> > Does anyone have access to the build bot so we can investigate and fix
> > this, or Apache Infra team can take care of this?
> >
> > On Mon, Jul 25, 2016 at 9:49 AM, Michael Han  wrote:
> >
> >> The issue might be transient, as this pre-commit build works this
> morning:
> >> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3284/
> >>
> >> As a side note there are a couple of other failures while triage the
> build
> >> today, looks like these are infrastructure issues:
> >>
> >> https://builds.apache.org/job/ZooKeeper-trunk-solaris/1240/
> >> BUILD FAILED
> >> /zonestorage/hudson_solaris/home/hudson/hudson-slave/
> >> workspace/ZooKeeper-trunk-solaris/trunk/build.xml:324: Execute failed:
> >> java.io.IOException: Cannot run program "sh": error=12, Not enough space
> >>
> >> https://builds.apache.org/job/ZooKeeper-trunk/3005/
> >> mv: cannot stat 'build/*.tar.gz': No such file or directory
> >> mv: cannot stat 'build/*.jar': No such file or directory
> >> mv: cannot stat 'build/test/findbugs': No such file or directory
> >> mv: cannot stat 'build/docs/api': No such file or directory
> >>
> >> On Mon, Jul 25, 2016 at 7:55 AM, Rakesh Radhakrishnan <
> rake...@apache.org>
> >> wrote:
> >>
> >>> Anybody has done changes to the build machine or test infrastructure?
> Is
> >>> this something simple issue, which can be resolved by giving
> permission to
> >>> those directories?
> >>>
> >>> +Rakesh
> >>>
> >>> On Sun, Jul 24, 2016 at 9:02 PM, Flavio Junqueira 
> wrote:
> >>>
>  The console output says this:
> 
>  [exec]
> 
> >>>
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
>  line 558: /home/jenkins/tools/jiracli/latest/jira: Permission denied
>  [exec]
> 
> >>>
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
>  line 559: /home/jenkins/tools/jiracli/latest/jira: Permission denied
> 
>  I'm not sure whether this is transient or anyone has changed the
> config.
> 
>  -Flavio
> 
> > On 24 Jul 2016, at 16:12, Rakesh Radhakrishnan 
>  wrote:
> >
> > Hi,
> >
> > It looks like "Precommit build" is triggered but failed to add
> >>> comments
>  to
> > Jira. Appreciate your help. Thanks!
> >
> > References:-
> > ZOOKEEPER-2479 ->
> > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3283/
> > ZOOKEEPER-2172 ->
> > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3282/
> >
> >
> ==
> >
> >[exec] Adding comment to Jira.
> >[exec]
>  ==
> >[exec]
>  ==
> >[exec]
> >[exec]
> >[exec]
> >[exec]
> >[exec]
>  ==
> >[exec]
>  ==
> >[exec] Finished build.
> >[exec]
>  ==
> >
> >
> > Thanks,
> > Rakesh
> 
> 
> >>>
> >>
> >>
> >>
> >> --
> >> Cheers
> >> Michael.
> >>
> >
> >
> >
> > --
> > Cheers
> > Michael.
>
>

ZooKeeper_branch35_solaris - Build # 182 - Still Failing

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 426043 lines...]
[junit] 2016-07-25 17:18:05,387 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-07-25 17:18:05,388 [myid:] - INFO  [main:ClientBase@466] - 
STARTING server
[junit] 2016-07-25 17:18:05,388 [myid:] - INFO  [main:ClientBase@386] - 
CREATING server instance 127.0.0.1:11222
[junit] 2016-07-25 17:18:05,388 [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-07-25 17:18:05,389 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-07-25 17:18:05,390 [myid:] - INFO  [main:ClientBase@361] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-07-25 17:18:05,390 [myid:] - INFO  [main:ZooKeeperServer@858] 
- minSessionTimeout set to 6000
[junit] 2016-07-25 17:18:05,390 [myid:] - INFO  [main:ZooKeeperServer@867] 
- maxSessionTimeout set to 6
[junit] 2016-07-25 17:18:05,390 [myid:] - INFO  [main:ZooKeeperServer@156] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test737585715296229082.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test737585715296229082.junit.dir/version-2
[junit] 2016-07-25 17:18:05,391 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test737585715296229082.junit.dir/version-2/snapshot.b
[junit] 2016-07-25 17:18:05,393 [myid:] - INFO  [main:FileTxnSnapLog@298] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test737585715296229082.junit.dir/version-2/snapshot.b
[junit] 2016-07-25 17:18:05,394 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-07-25 17:18:05,395 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:62759
[junit] 2016-07-25 17:18:05,396 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:62759
[junit] 2016-07-25 17:18:05,396 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-07-25 17:18:05,396 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:62759 (no session established for client)
[junit] 2016-07-25 17:18:05,396 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-07-25 17:18:05,398 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-07-25 17:18:05,398 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-07-25 17:18:05,398 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-07-25 17:18:05,398 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-07-25 17:18:05,398 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17738
[junit] 2016-07-25 17:18:05,399 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-07-25 17:18:05,399 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-07-25 17:18:05,399 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-07-25 17:18:06,042 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x122a00c675f
[junit] 2016-07-25 17:18:06,042 [myid:] - INFO  [main:ZooKeeper@1313] - 
Session: 0x122a00c675f closed
[junit] 2016-07-25 17:18:06,042 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-07-25 17:18:06,042 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2016-07-25 17:18:06,043 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-07-25 17:18:06,043 [myid:] - INFO  

Re: PreCommitBuild - Adding comment to Jira

[Flavio Junqueira]

I've only logged on to the jenkins console, I've never tried to access the 
machine itself. 

-Flavio

> On 25 Jul 2016, at 17:57, Michael Han  wrote:
> 
> Actually the issue might not be transient, just noticed that although
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3284/ succeeds, the
> log still said permission denied on invoking test-patch.sh. Not sure why
> this build is green given other pre-commit build failed with same cause
> (for example https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3283/).
> 
> Does anyone have access to the build bot so we can investigate and fix
> this, or Apache Infra team can take care of this?
> 
> On Mon, Jul 25, 2016 at 9:49 AM, Michael Han  wrote:
> 
>> The issue might be transient, as this pre-commit build works this morning:
>> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3284/
>> 
>> As a side note there are a couple of other failures while triage the build
>> today, looks like these are infrastructure issues:
>> 
>> https://builds.apache.org/job/ZooKeeper-trunk-solaris/1240/
>> BUILD FAILED
>> /zonestorage/hudson_solaris/home/hudson/hudson-slave/
>> workspace/ZooKeeper-trunk-solaris/trunk/build.xml:324: Execute failed:
>> java.io.IOException: Cannot run program "sh": error=12, Not enough space
>> 
>> https://builds.apache.org/job/ZooKeeper-trunk/3005/
>> mv: cannot stat 'build/*.tar.gz': No such file or directory
>> mv: cannot stat 'build/*.jar': No such file or directory
>> mv: cannot stat 'build/test/findbugs': No such file or directory
>> mv: cannot stat 'build/docs/api': No such file or directory
>> 
>> On Mon, Jul 25, 2016 at 7:55 AM, Rakesh Radhakrishnan 
>> wrote:
>> 
>>> Anybody has done changes to the build machine or test infrastructure?  Is
>>> this something simple issue, which can be resolved by giving permission to
>>> those directories?
>>> 
>>> +Rakesh
>>> 
>>> On Sun, Jul 24, 2016 at 9:02 PM, Flavio Junqueira  wrote:
>>> 
 The console output says this:
 
 [exec]
 
>>> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
 line 558: /home/jenkins/tools/jiracli/latest/jira: Permission denied
 [exec]
 
>>> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
 line 559: /home/jenkins/tools/jiracli/latest/jira: Permission denied
 
 I'm not sure whether this is transient or anyone has changed the config.
 
 -Flavio
 
> On 24 Jul 2016, at 16:12, Rakesh Radhakrishnan 
 wrote:
> 
> Hi,
> 
> It looks like "Precommit build" is triggered but failed to add
>>> comments
 to
> Jira. Appreciate your help. Thanks!
> 
> References:-
> ZOOKEEPER-2479 ->
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3283/
> ZOOKEEPER-2172 ->
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3282/
> 
> ==
> 
>[exec] Adding comment to Jira.
>[exec]
 ==
>[exec]
 ==
>[exec]
>[exec]
>[exec]
>[exec]
>[exec]
 ==
>[exec]
 ==
>[exec] Finished build.
>[exec]
 ==
> 
> 
> Thanks,
> Rakesh
 
 
>>> 
>> 
>> 
>> 
>> --
>> Cheers
>> Michael.
>> 
> 
> 
> 
> -- 
> Cheers
> Michael.

[jira] [Updated] (ZOOKEEPER-2487) Test failed because of 'Forked Java VM exited abnormally.'

[Michael Han (JIRA)]

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

Michael Han updated ZOOKEEPER-2487:
---
Fix Version/s: 3.5.3

> Test failed because of 'Forked Java VM exited abnormally.'
> --
>
> Key: ZOOKEEPER-2487
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2487
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.5.2
>Reporter: Michael Han
> Fix For: 3.5.3
>
>
> Sometimes tests fail with error message like this:
> Error Message:
> Forked Java VM exited abnormally. Please note the time in the report does not 
> reflect the time until the VM exit.
> Stack Trace:
> junit.framework.AssertionFailedError: Forked Java VM exited abnormally. 
> Please note the time in the report does not reflect the time until the VM 
> exit.
> Examples:
> https://builds.apache.org/job/ZooKeeper-trunk-solaris/1239/
> https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1147/
> https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1129/
> The failure happen on all platforms (jdk7/8/solaris).



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

[jira] [Updated] (ZOOKEEPER-2487) Test failed because of 'Forked Java VM exited abnormally.'

[Michael Han (JIRA)]

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

Michael Han updated ZOOKEEPER-2487:
---
Affects Version/s: (was: 3.5.3)
   3.5.2

> Test failed because of 'Forked Java VM exited abnormally.'
> --
>
> Key: ZOOKEEPER-2487
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2487
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.5.2
>Reporter: Michael Han
> Fix For: 3.5.3
>
>
> Sometimes tests fail with error message like this:
> Error Message:
> Forked Java VM exited abnormally. Please note the time in the report does not 
> reflect the time until the VM exit.
> Stack Trace:
> junit.framework.AssertionFailedError: Forked Java VM exited abnormally. 
> Please note the time in the report does not reflect the time until the VM 
> exit.
> Examples:
> https://builds.apache.org/job/ZooKeeper-trunk-solaris/1239/
> https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1147/
> https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1129/
> The failure happen on all platforms (jdk7/8/solaris).



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

[jira] [Created] (ZOOKEEPER-2487) Test failed because of 'Forked Java VM exited abnormally.'

[Michael Han (JIRA)]

Michael Han created ZOOKEEPER-2487:
--

 Summary: Test failed because of 'Forked Java VM exited abnormally.'
 Key: ZOOKEEPER-2487
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2487
 Project: ZooKeeper
  Issue Type: Bug
  Components: tests
Affects Versions: 3.5.3
Reporter: Michael Han


Sometimes tests fail with error message like this:

Error Message:
Forked Java VM exited abnormally. Please note the time in the report does not 
reflect the time until the VM exit.

Stack Trace:
junit.framework.AssertionFailedError: Forked Java VM exited abnormally. Please 
note the time in the report does not reflect the time until the VM exit.

Examples:
https://builds.apache.org/job/ZooKeeper-trunk-solaris/1239/
https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1147/
https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1129/

The failure happen on all platforms (jdk7/8/solaris).



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

Re: PreCommitBuild - Adding comment to Jira

[Michael Han]

Actually the issue might not be transient, just noticed that although
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3284/ succeeds, the
log still said permission denied on invoking test-patch.sh. Not sure why
this build is green given other pre-commit build failed with same cause
(for example https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3283/).

Does anyone have access to the build bot so we can investigate and fix
this, or Apache Infra team can take care of this?

On Mon, Jul 25, 2016 at 9:49 AM, Michael Han  wrote:

> The issue might be transient, as this pre-commit build works this morning:
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3284/
>
> As a side note there are a couple of other failures while triage the build
> today, looks like these are infrastructure issues:
>
> https://builds.apache.org/job/ZooKeeper-trunk-solaris/1240/
> BUILD FAILED
> /zonestorage/hudson_solaris/home/hudson/hudson-slave/
> workspace/ZooKeeper-trunk-solaris/trunk/build.xml:324: Execute failed:
> java.io.IOException: Cannot run program "sh": error=12, Not enough space
>
> https://builds.apache.org/job/ZooKeeper-trunk/3005/
> mv: cannot stat 'build/*.tar.gz': No such file or directory
> mv: cannot stat 'build/*.jar': No such file or directory
> mv: cannot stat 'build/test/findbugs': No such file or directory
> mv: cannot stat 'build/docs/api': No such file or directory
>
> On Mon, Jul 25, 2016 at 7:55 AM, Rakesh Radhakrishnan 
> wrote:
>
>> Anybody has done changes to the build machine or test infrastructure?  Is
>> this something simple issue, which can be resolved by giving permission to
>> those directories?
>>
>> +Rakesh
>>
>> On Sun, Jul 24, 2016 at 9:02 PM, Flavio Junqueira  wrote:
>>
>> > The console output says this:
>> >
>> > [exec]
>> >
>> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
>> > line 558: /home/jenkins/tools/jiracli/latest/jira: Permission denied
>> >  [exec]
>> >
>> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
>> > line 559: /home/jenkins/tools/jiracli/latest/jira: Permission denied
>> >
>> > I'm not sure whether this is transient or anyone has changed the config.
>> >
>> > -Flavio
>> >
>> > > On 24 Jul 2016, at 16:12, Rakesh Radhakrishnan 
>> > wrote:
>> > >
>> > > Hi,
>> > >
>> > > It looks like "Precommit build" is triggered but failed to add
>> comments
>> > to
>> > > Jira. Appreciate your help. Thanks!
>> > >
>> > > References:-
>> > > ZOOKEEPER-2479 ->
>> > > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3283/
>> > > ZOOKEEPER-2172 ->
>> > > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3282/
>> > >
>> > > ==
>> > >
>> > > [exec] Adding comment to Jira.
>> > > [exec]
>> > ==
>> > > [exec]
>> > ==
>> > > [exec]
>> > > [exec]
>> > > [exec]
>> > > [exec]
>> > > [exec]
>> > ==
>> > > [exec]
>> > ==
>> > > [exec] Finished build.
>> > > [exec]
>> > ==
>> > >
>> > >
>> > > Thanks,
>> > > Rakesh
>> >
>> >
>>
>
>
>
> --
> Cheers
> Michael.
>



-- 
Cheers
Michael.

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

[Michael Han (JIRA)]

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

Michael Han commented on ZOOKEEPER-2247:


This is a known flaky tests and is tracked by ZOOKEEPER-2483.

> 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.3, 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-16.patch, ZOOKEEPER-2247-17.patch, ZOOKEEPER-2247-18.patch, 
> ZOOKEEPER-2247-19.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)

Re: PreCommitBuild - Adding comment to Jira

[Michael Han]

The issue might be transient, as this pre-commit build works this morning:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3284/

As a side note there are a couple of other failures while triage the build
today, looks like these are infrastructure issues:

https://builds.apache.org/job/ZooKeeper-trunk-solaris/1240/
BUILD FAILED
/zonestorage/hudson_solaris/home/hudson/hudson-slave/
workspace/ZooKeeper-trunk-solaris/trunk/build.xml:324: Execute failed:
java.io.IOException: Cannot run program "sh": error=12, Not enough space

https://builds.apache.org/job/ZooKeeper-trunk/3005/
mv: cannot stat 'build/*.tar.gz': No such file or directory
mv: cannot stat 'build/*.jar': No such file or directory
mv: cannot stat 'build/test/findbugs': No such file or directory
mv: cannot stat 'build/docs/api': No such file or directory

On Mon, Jul 25, 2016 at 7:55 AM, Rakesh Radhakrishnan 
wrote:

> Anybody has done changes to the build machine or test infrastructure?  Is
> this something simple issue, which can be resolved by giving permission to
> those directories?
>
> +Rakesh
>
> On Sun, Jul 24, 2016 at 9:02 PM, Flavio Junqueira  wrote:
>
> > The console output says this:
> >
> > [exec]
> >
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
> > line 558: /home/jenkins/tools/jiracli/latest/jira: Permission denied
> >  [exec]
> >
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
> > line 559: /home/jenkins/tools/jiracli/latest/jira: Permission denied
> >
> > I'm not sure whether this is transient or anyone has changed the config.
> >
> > -Flavio
> >
> > > On 24 Jul 2016, at 16:12, Rakesh Radhakrishnan 
> > wrote:
> > >
> > > Hi,
> > >
> > > It looks like "Precommit build" is triggered but failed to add comments
> > to
> > > Jira. Appreciate your help. Thanks!
> > >
> > > References:-
> > > ZOOKEEPER-2479 ->
> > > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3283/
> > > ZOOKEEPER-2172 ->
> > > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3282/
> > >
> > > ==
> > >
> > > [exec] Adding comment to Jira.
> > > [exec]
> > ==
> > > [exec]
> > ==
> > > [exec]
> > > [exec]
> > > [exec]
> > > [exec]
> > > [exec]
> > ==
> > > [exec]
> > ==
> > > [exec] Finished build.
> > > [exec]
> > ==
> > >
> > >
> > > Thanks,
> > > Rakesh
> >
> >
>



-- 
Cheers
Michael.

ZooKeeper_branch34_openjdk7 - Build # 1148 - Still Failing

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 219760 lines...]
[junit] 2016-07-25 15:20:21,732 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-07-25 15:20:21,732 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-07-25 15:20:21,733 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2016-07-25 15:20:21,733 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-07-25 15:20:21,733 [myid:] - INFO  [main:ZooKeeperServer@469] 
- shutting down
[junit] 2016-07-25 15:20:21,734 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-07-25 15:20:21,734 [myid:] - INFO  
[main:PrepRequestProcessor@765] - Shutting down
[junit] 2016-07-25 15:20:21,734 [myid:] - INFO  
[main:SyncRequestProcessor@209] - Shutting down
[junit] 2016-07-25 15:20:21,734 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-07-25 15:20:21,734 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited!
[junit] 2016-07-25 15:20:21,738 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2016-07-25 15:20:21,739 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-07-25 15:20:21,740 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-07-25 15:20:21,741 [myid:] - INFO  [main:ClientBase@443] - 
STARTING server
[junit] 2016-07-25 15:20:21,742 [myid:] - INFO  [main:ClientBase@364] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-07-25 15:20:21,742 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-07-25 15:20:21,743 [myid:] - INFO  [main:ClientBase@339] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-07-25 15:20:21,743 [myid:] - INFO  [main:ZooKeeperServer@170] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/branch-3.4/build/test/tmp/test2907099642742584113.junit.dir/version-2
 snapdir 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/branch-3.4/build/test/tmp/test2907099642742584113.junit.dir/version-2
[junit] 2016-07-25 15:20:21,747 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-07-25 15:20:21,747 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:51304
[junit] 2016-07-25 15:20:21,748 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:51304
[junit] 2016-07-25 15:20:21,748 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-07-25 15:20:21,749 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:51304 (no session established for client)
[junit] 2016-07-25 15:20:21,749 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-07-25 15:20:21,751 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-07-25 15:20:21,751 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-07-25 15:20:21,751 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-07-25 15:20:21,751 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-07-25 15:20:21,752 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 26415
[junit] 2016-07-25 15:20:21,752 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-07-25 15:20:21,752 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-07-25 15:20:21,752 [myid:] - INFO  [main:ClientBase@520] - 
tearDown starting
[junit] 2016-07-25 15:20:21,822 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15622a480a3 closed
[junit] 2016-07-25 15:20:21,822 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2016-07-25 15:20:21,823 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-07-25 15:20:21,824 [myid:] 

Re: PreCommitBuild - Adding comment to Jira

[Rakesh Radhakrishnan]

Anybody has done changes to the build machine or test infrastructure?  Is
this something simple issue, which can be resolved by giving permission to
those directories?

+Rakesh

On Sun, Jul 24, 2016 at 9:02 PM, Flavio Junqueira  wrote:

> The console output says this:
>
> [exec]
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
> line 558: /home/jenkins/tools/jiracli/latest/jira: Permission denied
>  [exec]
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
> line 559: /home/jenkins/tools/jiracli/latest/jira: Permission denied
>
> I'm not sure whether this is transient or anyone has changed the config.
>
> -Flavio
>
> > On 24 Jul 2016, at 16:12, Rakesh Radhakrishnan 
> wrote:
> >
> > Hi,
> >
> > It looks like "Precommit build" is triggered but failed to add comments
> to
> > Jira. Appreciate your help. Thanks!
> >
> > References:-
> > ZOOKEEPER-2479 ->
> > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3283/
> > ZOOKEEPER-2172 ->
> > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3282/
> >
> > ==
> >
> > [exec] Adding comment to Jira.
> > [exec]
> ==
> > [exec]
> ==
> > [exec]
> > [exec]
> > [exec]
> > [exec]
> > [exec]
> ==
> > [exec]
> ==
> > [exec] Finished build.
> > [exec]
> ==
> >
> >
> > Thanks,
> > Rakesh
>
>

[jira] [Commented] (ZOOKEEPER-2383) Startup race in ZooKeeperServer

[Rakesh R (JIRA)]

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

Rakesh R commented on ZOOKEEPER-2383:
-

fyi: The patch got a green 
[build_3284|https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3284/] , 
unfortunately there is a {{Permission denied}} issue in the build and due to 
that its not commenting to the jira. Anyone has idea about this problem?

{code}
[exec] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
 line 558: /home/jenkins/tools/jiracli/latest/jira: Permission denied
 [exec] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
 line 559: /home/jenkins/tools/jiracli/latest/jira: Permission denied
{code}

> Startup race in ZooKeeperServer
> ---
>
> Key: ZOOKEEPER-2383
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2383
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: jmx, server
>Affects Versions: 3.4.8
>Reporter: Steve Rowe
>Assignee: Rakesh R
>Priority: Blocker
> Fix For: 3.4.9, 3.5.3, 3.6.0
>
> Attachments: TestZkStandaloneJMXRegistrationRaceConcurrent.java, 
> ZOOKEEPER-2383.patch, release-3.4.8-extra-logging.patch, 
> zk-3.4.8-MBeanRegistry.log, zk-3.4.8-NPE.log
>
>
> In attempting to upgrade Solr's ZooKeeper dependency from 3.4.6 to 3.4.8 
> (SOLR-8724) I ran into test failures where attempts to create a node in a 
> newly started standalone ZooKeeperServer were failing because of an assertion 
> in MBeanRegistry.
> ZooKeeperServer.startup() first sets up its request processor chain then 
> registers itself in JMX, but if a connection comes in before the server's JMX 
> registration happens, registration of the connection will fail because it 
> trips the assertion that (effectively) its parent (the server) has already 
> registered itself.
> {code:java|title=ZooKeeperServer.java}
> public synchronized void startup() {
> if (sessionTracker == null) {
> createSessionTracker();
> }
> startSessionTracker();
> setupRequestProcessors();
> registerJMX();
> state = State.RUNNING;
> notifyAll();
> }
> {code}
> {code:java|title=MBeanRegistry.java}
> public void register(ZKMBeanInfo bean, ZKMBeanInfo parent)
> throws JMException
> {
> assert bean != null;
> String path = null;
> if (parent != null) {
> path = mapBean2Path.get(parent);
> assert path != null;
> }
> {code}
> This problem appears to be new with ZK 3.4.8 - AFAIK Solr never had this 
> issue with ZK 3.4.6. 



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

Success: ZOOKEEPER-2383 PreCommit Build #3284

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 442394 lines...]
 [exec]   
http://issues.apache.org/jira/secure/attachment/12819926/ZOOKEEPER-2383.patch
 [exec]   against trunk revision 1750739.
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [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 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/3284//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3284//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3284//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
 line 558: /home/jenkins/tools/jiracli/latest/jira: Permission denied
 [exec] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
 line 559: /home/jenkins/tools/jiracli/latest/jira: Permission denied

BUILD SUCCESSFUL
Total time: 20 minutes 50 seconds
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-2383
Email was triggered for: Success
Sending email for trigger: Success
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-2383) Startup race in ZooKeeperServer

[Rakesh R (JIRA)]

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

Rakesh R commented on ZOOKEEPER-2383:
-

Attached initial patch where I've used {{zkServer.isRunning()}} status to check 
whether the server is up and running. Appreciate your help in reviews. Thanks!

> Startup race in ZooKeeperServer
> ---
>
> Key: ZOOKEEPER-2383
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2383
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: jmx, server
>Affects Versions: 3.4.8
>Reporter: Steve Rowe
>Assignee: Rakesh R
>Priority: Blocker
> Fix For: 3.4.9
>
> Attachments: TestZkStandaloneJMXRegistrationRaceConcurrent.java, 
> ZOOKEEPER-2383.patch, release-3.4.8-extra-logging.patch, 
> zk-3.4.8-MBeanRegistry.log, zk-3.4.8-NPE.log
>
>
> In attempting to upgrade Solr's ZooKeeper dependency from 3.4.6 to 3.4.8 
> (SOLR-8724) I ran into test failures where attempts to create a node in a 
> newly started standalone ZooKeeperServer were failing because of an assertion 
> in MBeanRegistry.
> ZooKeeperServer.startup() first sets up its request processor chain then 
> registers itself in JMX, but if a connection comes in before the server's JMX 
> registration happens, registration of the connection will fail because it 
> trips the assertion that (effectively) its parent (the server) has already 
> registered itself.
> {code:java|title=ZooKeeperServer.java}
> public synchronized void startup() {
> if (sessionTracker == null) {
> createSessionTracker();
> }
> startSessionTracker();
> setupRequestProcessors();
> registerJMX();
> state = State.RUNNING;
> notifyAll();
> }
> {code}
> {code:java|title=MBeanRegistry.java}
> public void register(ZKMBeanInfo bean, ZKMBeanInfo parent)
> throws JMException
> {
> assert bean != null;
> String path = null;
> if (parent != null) {
> path = mapBean2Path.get(parent);
> assert path != null;
> }
> {code}
> This problem appears to be new with ZK 3.4.8 - AFAIK Solr never had this 
> issue with ZK 3.4.6. 



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

[jira] [Updated] (ZOOKEEPER-2383) Startup race in ZooKeeperServer

[Rakesh R (JIRA)]

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

Rakesh R updated ZOOKEEPER-2383:

Attachment: ZOOKEEPER-2383.patch

> Startup race in ZooKeeperServer
> ---
>
> Key: ZOOKEEPER-2383
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2383
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: jmx, server
>Affects Versions: 3.4.8
>Reporter: Steve Rowe
>Assignee: Rakesh R
>Priority: Blocker
> Fix For: 3.4.9
>
> Attachments: TestZkStandaloneJMXRegistrationRaceConcurrent.java, 
> ZOOKEEPER-2383.patch, release-3.4.8-extra-logging.patch, 
> zk-3.4.8-MBeanRegistry.log, zk-3.4.8-NPE.log
>
>
> In attempting to upgrade Solr's ZooKeeper dependency from 3.4.6 to 3.4.8 
> (SOLR-8724) I ran into test failures where attempts to create a node in a 
> newly started standalone ZooKeeperServer were failing because of an assertion 
> in MBeanRegistry.
> ZooKeeperServer.startup() first sets up its request processor chain then 
> registers itself in JMX, but if a connection comes in before the server's JMX 
> registration happens, registration of the connection will fail because it 
> trips the assertion that (effectively) its parent (the server) has already 
> registered itself.
> {code:java|title=ZooKeeperServer.java}
> public synchronized void startup() {
> if (sessionTracker == null) {
> createSessionTracker();
> }
> startSessionTracker();
> setupRequestProcessors();
> registerJMX();
> state = State.RUNNING;
> notifyAll();
> }
> {code}
> {code:java|title=MBeanRegistry.java}
> public void register(ZKMBeanInfo bean, ZKMBeanInfo parent)
> throws JMException
> {
> assert bean != null;
> String path = null;
> if (parent != null) {
> path = mapBean2Path.get(parent);
> assert path != null;
> }
> {code}
> This problem appears to be new with ZK 3.4.8 - AFAIK Solr never had this 
> issue with ZK 3.4.6. 



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

ZooKeeper_branch35_jdk8 - Build # 164 - Failure

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 434354 lines...]
[junit] 2016-07-25 12:15:24,470 [myid:127.0.0.1:24814] - WARN  
[main-SendThread(127.0.0.1:24814):ClientCnxn$SendThread@1235] - Session 
0x3017b2da395 for server 127.0.0.1/127.0.0.1:24814, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2016-07-25 12:15:25,281 [myid:127.0.0.1:24811] - INFO  
[main-SendThread(127.0.0.1:24811):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:24811. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-07-25 12:15:25,281 [myid:127.0.0.1:24811] - WARN  
[main-SendThread(127.0.0.1:24811):ClientCnxn$SendThread@1235] - Session 
0x2017b2da32c for server 127.0.0.1/127.0.0.1:24811, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2016-07-25 12:15:25,436 [myid:] - INFO  [ProcessThread(sid:0 
cport:24931)::PrepRequestProcessor@647] - Processed session termination for 
sessionid: 0x1017b3087e8
[junit] 2016-07-25 12:15:25,444 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port24931,name1=Connections,name2=127.0.0.1,name3=0x1017b3087e8]
[junit] 2016-07-25 12:15:25,444 [myid:] - INFO  [main:ZooKeeper@1313] - 
Session: 0x1017b3087e8 closed
[junit] 2016-07-25 12:15:25,444 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1017b3087e8
[junit] 2016-07-25 12:15:25,444 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 139113
[junit] 2016-07-25 12:15:25,444 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 1642
[junit] 2016-07-25 12:15:25,444 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2016-07-25 12:15:25,444 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-07-25 12:15:25,444 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-07-25 12:15:25,444 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:24931
[junit] 2016-07-25 12:15:25,450 [myid:] - INFO  [main:ZooKeeperServer@498] 
- shutting down
[junit] 2016-07-25 12:15:25,450 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2016-07-25 12:15:25,450 [myid:] - INFO  
[main:PrepRequestProcessor@965] - Shutting down
[junit] 2016-07-25 12:15:25,450 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2016-07-25 12:15:25,450 [myid:] - INFO  [ProcessThread(sid:0 
cport:24931)::PrepRequestProcessor@154] - PrepRequestProcessor exited loop!
[junit] 2016-07-25 12:15:25,451 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2016-07-25 12:15:25,451 [myid:] - INFO  
[main:FinalRequestProcessor@479] - shutdown of request processor complete
[junit] 2016-07-25 12:15:25,451 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port24931,name1=InMemoryDataTree]
[junit] 2016-07-25 12:15:25,451 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port24931]
[junit] 2016-07-25 12:15:25,451 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 24931
[junit] 2016-07-25 12:15:25,452 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-07-25 12:15:25,457 [myid:] - INFO  [main:ClientBase@568] - 
fdcount after test is: 4833 at start it was 4829
[junit] 2016-07-25 12:15:25,457 [myid:] - INFO  [main:ClientBase@570] - 
sleeping for 20 secs
[junit] 2016-07-25 12:15:25,457 [myid:] - INFO  [main:ZKTestCase$1@65] - 
SUCCEEDED testWatcherAutoResetWithLocal
[junit] 2016-07-25 

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

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 383214 lines...]
[junit] at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
[junit] at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
[junit] at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
[junit] at 
junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:38)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:532)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1179)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:1030)
[junit] 2016-07-25 12:00:21,458 [myid:] - INFO  [main:ZKTestCase$1@60] - 
FINISHED testAsyncGetACL
[junit] 2016-07-25 12:00:21,460 [myid:] - INFO  [main:PortAssignment@85] - 
Assigned port 27391 from range 27379 - 30071.
[junit] 2016-07-25 12:00:21,460 [myid:] - INFO  [main:ZKTestCase$1@55] - 
STARTING testAsyncCreate2Failure_NoNode
[junit] 2016-07-25 12:00:21,461 [myid:] - INFO  [main:ClientBase@448] - 
Initial fdcount is: 59
[junit] 2016-07-25 12:02:21,581 [myid:] - INFO  [main:ZKTestCase$1@70] - 
FAILED testAsyncCreate2Failure_NoNode
[junit] org.junit.internal.runners.model.MultipleFailureException: There 
were 2 errors:
[junit]   java.rmi.ConnectIOException(error during JRMP connection 
establishment; nested exception is: 
[junit] java.net.SocketTimeoutException: Read timed out)
[junit]   java.lang.NullPointerException(null)
[junit] at 
org.junit.runners.model.MultipleFailureException.assertEmpty(MultipleFailureException.java:67)
[junit] at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:39)
[junit] at org.junit.rules.TestWatchman$1.evaluate(TestWatchman.java:53)
[junit] at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
[junit] at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
[junit] at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
[junit] at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
[junit] at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
[junit] at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
[junit] at 
org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
[junit] at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
[junit] at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
[junit] at org.junit.runners.Suite.runChild(Suite.java:128)
[junit] at org.junit.runners.Suite.runChild(Suite.java:27)
[junit] at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
[junit] at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
[junit] at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
[junit] at 
org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
[junit] at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
[junit] at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
[junit] at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
[junit] at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
[junit] at 
junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:38)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:532)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1179)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:1030)
[junit] 2016-07-25 12:02:21,582 [myid:] - INFO  [main:ZKTestCase$1@60] - 
FINISHED testAsyncCreate2Failure_NoNode
[junit] 2016-07-25 12:02:21,583 [myid:] - INFO  [main:PortAssignment@85] - 
Assigned port 27392 from range 27379 - 30071.
[junit] 2016-07-25 12:02:21,584 [myid:] - INFO  [main:ZKTestCase$1@55] - 
STARTING testAsyncCreateFailure_NoNode
[junit] 2016-07-25 12:02:21,584 [myid:] - INFO  [main:ClientBase@448] - 
Initial fdcount is: 61
[junit] Running org.apache.zookeeper.test.NettyNettySuiteTest in thread 7
[junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 
sec, Thread: 7, Class: org.apache.zookeeper.test.NettyNettySuiteTest
[junit] Test org.apache.zookeeper.test.NettyNettySuiteTest FAILED (timeout)

BUILD FAILED

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

[Rakesh R (JIRA)]

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

Rakesh R commented on ZOOKEEPER-2247:
-

ping [~fpj], [~rgs], would be great to see your feedback on pushing this in. 
I've tried fixing all your comments in the latest patch. Kindly review it 
again. Thanks!

> 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.3, 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-16.patch, ZOOKEEPER-2247-17.patch, ZOOKEEPER-2247-18.patch, 
> ZOOKEEPER-2247-19.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)

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

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 192 lines...]
 [java] at 
org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:495)
 [java] at org.apache.tools.ant.taskdefs.Java.fork(Java.java:791)
 [java] ... 19 more
 [java] Caused by: java.io.IOException: error=12, Not enough space
 [java] at java.lang.UNIXProcess.forkAndExec(Native Method)
 [java] at java.lang.UNIXProcess.(UNIXProcess.java:136)
 [java] at java.lang.ProcessImpl.start(ProcessImpl.java:130)
 [java] at java.lang.ProcessBuilder.start(ProcessBuilder.java:1028)
 [java] ... 24 more
 [java] Java Result: -1
[touch] Creating 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/src/java/generated/.generated

ver-gen:
[javac] Compiling 1 source file to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/classes

svn-revision:
[mkdir] Created dir: 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/.revision

BUILD FAILED
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build.xml:324:
 Execute failed: java.io.IOException: Cannot run program "sh": error=12, Not 
enough space
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1047)
at java.lang.Runtime.exec(Runtime.java:617)
at 
org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.exec(Execute.java:862)
at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:481)
at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:495)
at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:631)
at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:672)
at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:498)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.Main.runBuild(Main.java:809)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Caused by: java.io.IOException: error=12, Not enough space
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:136)
at java.lang.ProcessImpl.start(ProcessImpl.java:130)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1028)
... 23 more

Total time: 41 seconds
Build step 'Invoke Ant' marked build as failure
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



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

[jira] [Commented] (ZOOKEEPER-2383) Startup race in ZooKeeperServer

[Rakesh R (JIRA)]

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

Rakesh R commented on ZOOKEEPER-2383:
-

[~ozawa], thanks for the interest. I was busy with other things and will give 
priority to this issue. I will update patch soon. I'm planning to include this 
in 3.4.9 release and please see the [3.4.9 release 
discussion|http://goo.gl/SJJhbx]

> Startup race in ZooKeeperServer
> ---
>
> Key: ZOOKEEPER-2383
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2383
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: jmx, server
>Affects Versions: 3.4.8
>Reporter: Steve Rowe
>Assignee: Rakesh R
>Priority: Blocker
> Fix For: 3.4.9
>
> Attachments: TestZkStandaloneJMXRegistrationRaceConcurrent.java, 
> release-3.4.8-extra-logging.patch, zk-3.4.8-MBeanRegistry.log, 
> zk-3.4.8-NPE.log
>
>
> In attempting to upgrade Solr's ZooKeeper dependency from 3.4.6 to 3.4.8 
> (SOLR-8724) I ran into test failures where attempts to create a node in a 
> newly started standalone ZooKeeperServer were failing because of an assertion 
> in MBeanRegistry.
> ZooKeeperServer.startup() first sets up its request processor chain then 
> registers itself in JMX, but if a connection comes in before the server's JMX 
> registration happens, registration of the connection will fail because it 
> trips the assertion that (effectively) its parent (the server) has already 
> registered itself.
> {code:java|title=ZooKeeperServer.java}
> public synchronized void startup() {
> if (sessionTracker == null) {
> createSessionTracker();
> }
> startSessionTracker();
> setupRequestProcessors();
> registerJMX();
> state = State.RUNNING;
> notifyAll();
> }
> {code}
> {code:java|title=MBeanRegistry.java}
> public void register(ZKMBeanInfo bean, ZKMBeanInfo parent)
> throws JMException
> {
> assert bean != null;
> String path = null;
> if (parent != null) {
> path = mapBean2Path.get(parent);
> assert path != null;
> }
> {code}
> This problem appears to be new with ZK 3.4.8 - AFAIK Solr never had this 
> issue with ZK 3.4.6. 



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

[jira] [Commented] (ZOOKEEPER-2383) Startup race in ZooKeeperServer

[Tsuyoshi Ozawa (JIRA)]

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

Tsuyoshi Ozawa commented on ZOOKEEPER-2383:
---

[~rakeshr] hi Rakesh, how is the progress of this issue?

> Startup race in ZooKeeperServer
> ---
>
> Key: ZOOKEEPER-2383
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2383
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: jmx, server
>Affects Versions: 3.4.8
>Reporter: Steve Rowe
>Assignee: Rakesh R
>Priority: Blocker
> Fix For: 3.4.9
>
> Attachments: TestZkStandaloneJMXRegistrationRaceConcurrent.java, 
> release-3.4.8-extra-logging.patch, zk-3.4.8-MBeanRegistry.log, 
> zk-3.4.8-NPE.log
>
>
> In attempting to upgrade Solr's ZooKeeper dependency from 3.4.6 to 3.4.8 
> (SOLR-8724) I ran into test failures where attempts to create a node in a 
> newly started standalone ZooKeeperServer were failing because of an assertion 
> in MBeanRegistry.
> ZooKeeperServer.startup() first sets up its request processor chain then 
> registers itself in JMX, but if a connection comes in before the server's JMX 
> registration happens, registration of the connection will fail because it 
> trips the assertion that (effectively) its parent (the server) has already 
> registered itself.
> {code:java|title=ZooKeeperServer.java}
> public synchronized void startup() {
> if (sessionTracker == null) {
> createSessionTracker();
> }
> startSessionTracker();
> setupRequestProcessors();
> registerJMX();
> state = State.RUNNING;
> notifyAll();
> }
> {code}
> {code:java|title=MBeanRegistry.java}
> public void register(ZKMBeanInfo bean, ZKMBeanInfo parent)
> throws JMException
> {
> assert bean != null;
> String path = null;
> if (parent != null) {
> path = mapBean2Path.get(parent);
> assert path != null;
> }
> {code}
> This problem appears to be new with ZK 3.4.8 - AFAIK Solr never had this 
> issue with ZK 3.4.6. 



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

[jira] [Commented] (ZOOKEEPER-2317) Non-OSGi compatible version

[Sachin (JIRA)]

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

Sachin commented on ZOOKEEPER-2317:
---

Hi All,

Is there any work in progress for this issue.

We are also facing such issue in our code.




> Non-OSGi compatible version
> ---
>
> Key: ZOOKEEPER-2317
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2317
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: build
>Affects Versions: 3.5.1
> Environment: Karaf OSGi container
>Reporter: Markus Tippmann
>Priority: Blocker
> Fix For: 3.5.3
>
>
> Bundle cannot be deployed to OSGi container.
> Manifest version is not OSGi compatible.
> Instead of using 3.5.1-alpha, manifest needs to contain 3.5.1.alpha



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