[jira] [Updated] (ZOOKEEPER-2307) ZooKeeper not starting because acceptedEpoch is less than the currentEpoch

2015-11-05 Thread Arshad Mohammad (JIRA) 

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

Arshad Mohammad updated ZOOKEEPER-2307:
---
Attachment: ZOOKEEPER-2307-02.patch

Submitting the fix.

> ZooKeeper not starting because acceptedEpoch is less than the currentEpoch
> --
>
> Key: ZOOKEEPER-2307
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2307
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Critical
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2307-01.patch, ZOOKEEPER-2307-02.patch
>
>
> This issue occurred in one of our test environment where disk was being 
> changed to read only very frequently.
> The the scenario is as follows:
> # Configure three node ZooKeeper cluster, lets say nodes are A, B and C
> # Start A and B. Both A and B start successfully, quorum is running.
> # Start C, because of IO error C fails to update acceptedEpoch file. But C 
> also starts successfully, joins the quorum as follower
> # Stop C
> # Start C, bellow exception with message "The accepted epoch, 0 is less than 
> the current epoch, 1" is thrown
> {code}
> 2015-10-29 16:52:32,942 [myid:3] - ERROR [main:QuorumPeer@784] - Unable to 
> load database on disk
> java.io.IOException: The accepted epoch, 0 is less than the current epoch, 1
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeer.loadDataBase(QuorumPeer.java:781)
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeer.start(QuorumPeer.java:720)
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeerMain.runFromConfig(QuorumPeerMain.java:202)
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:139)
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:88)
> 2015-10-29 16:52:32,946 [myid:3] - ERROR [main:QuorumPeerMain@111] - 
> Unexpected exception, exiting abnormally
> java.lang.RuntimeException: Unable to run quorum server 
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeer.loadDataBase(QuorumPeer.java:785)
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeer.start(QuorumPeer.java:720)
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeerMain.runFromConfig(QuorumPeerMain.java:202)
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:139)
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:88)
> Caused by: java.io.IOException: The accepted epoch, 0 is less than the 
> current epoch, 1
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeer.loadDataBase(QuorumPeer.java:781)
> {code}



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

Failed: ZOOKEEPER-2307 PreCommit Build #2943

2015-11-05 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2307
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2943/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 520190 lines...]
 [exec] +1 tests included.  The patch appears to include 5 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 generated 1 release audit 
warnings (more than the trunk's current 0 warnings).
 [exec] 
 [exec] -1 core tests.  The patch failed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2943//testReport/
 [exec] Release audit warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2943//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2943//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2943//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Comment added.
 [exec] de71b5bbee7237a1b36030c9401c568e09da5a08 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

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

Total time: 12 minutes 11 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Compressed 557.13 KB of artifacts by 51.7% relative to #2942
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-2307
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



###
## FAILED TESTS (if any) 
##
2 tests failed.
FAILED:  org.apache.zookeeper.server.quorum.Zab1_0Test.testTxnTimeout

Error Message:
expected:<1> but was:<0>

Stack Trace:
junit.framework.AssertionFailedError: expected:<1> but was:<0>
at 
org.apache.zookeeper.server.quorum.Zab1_0Test$7.converseWithLeader(Zab1_0Test.java:955)
at 
org.apache.zookeeper.server.quorum.Zab1_0Test.testLeaderConversation(Zab1_0Test.java:393)
at 
org.apache.zookeeper.server.quorum.Zab1_0Test.testTxnTimeout(Zab1_0Test.java:923)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)


FAILED:  org.apache.zookeeper.server.quorum.Zab1_0Test.testNormalRun

Error Message:
expected:<1> but was:<0>

Stack Trace:
junit.framework.AssertionFailedError: expected:<1> but was:<0>
at 
org.apache.zookeeper.server.quorum.Zab1_0Test$6.converseWithLeader(Zab1_0Test.java:910)
at 
org.apache.zookeeper.server.quorum.Zab1_0Test.testLeaderConversation(Zab1_0Test.java:393)
at 
org.apache.zookeeper.server.quorum.Zab1_0Test.testNormalRun(Zab1_0Test.java:877)
at

[jira] [Commented] (ZOOKEEPER-2307) ZooKeeper not starting because acceptedEpoch is less than the currentEpoch

2015-11-05 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on ZOOKEEPER-2307:
--

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12770769/ZOOKEEPER-2307-02.patch
  against trunk revision 1712218.

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

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

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

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

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

-1 release audit.  The applied patch generated 1 release audit warnings 
(more than the trunk's current 0 warnings).

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

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

Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2943//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2943//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2943//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2943//console

This message is automatically generated.

> ZooKeeper not starting because acceptedEpoch is less than the currentEpoch
> --
>
> Key: ZOOKEEPER-2307
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2307
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Critical
> Fix For: 3.5.2
>
> Attachments: ZOOKEEPER-2307-01.patch, ZOOKEEPER-2307-02.patch
>
>
> This issue occurred in one of our test environment where disk was being 
> changed to read only very frequently.
> The the scenario is as follows:
> # Configure three node ZooKeeper cluster, lets say nodes are A, B and C
> # Start A and B. Both A and B start successfully, quorum is running.
> # Start C, because of IO error C fails to update acceptedEpoch file. But C 
> also starts successfully, joins the quorum as follower
> # Stop C
> # Start C, bellow exception with message "The accepted epoch, 0 is less than 
> the current epoch, 1" is thrown
> {code}
> 2015-10-29 16:52:32,942 [myid:3] - ERROR [main:QuorumPeer@784] - Unable to 
> load database on disk
> java.io.IOException: The accepted epoch, 0 is less than the current epoch, 1
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeer.loadDataBase(QuorumPeer.java:781)
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeer.start(QuorumPeer.java:720)
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeerMain.runFromConfig(QuorumPeerMain.java:202)
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:139)
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:88)
> 2015-10-29 16:52:32,946 [myid:3] - ERROR [main:QuorumPeerMain@111] - 
> Unexpected exception, exiting abnormally
> java.lang.RuntimeException: Unable to run quorum server 
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeer.loadDataBase(QuorumPeer.java:785)
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeer.start(QuorumPeer.java:720)
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeerMain.runFromConfig(QuorumPeerMain.java:202)
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:139)
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:88)
> Caused by: java.io.IOException: The accepted epoch, 0 is less than the 
> current epoch, 1
>   at 
> org.apache.zookeeper.server.quorum.QuorumPeer.loadDataBase(QuorumPeer.java:781)
> {code}



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

[jira] [Created] (ZOOKEEPER-2314) Improve SASL documentation

2015-11-05 Thread Flavio Junqueira (JIRA) 
Flavio Junqueira created ZOOKEEPER-2314:
---

 Summary: Improve SASL documentation
 Key: ZOOKEEPER-2314
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2314
 Project: ZooKeeper
  Issue Type: Improvement
  Components: documentation
Affects Versions: 3.5.1, 3.4.6
Reporter: Flavio Junqueira
Assignee: Flavio Junqueira
Priority: Blocker
 Fix For: 3.4.8, 3.5.2, 3.6.0


Points that occur to me right now:

# The login object in ZooKeeperSaslClient is static, which means that if you 
try to create another client for tests, the login object will be the first one 
you've set for all runs. I've experienced this with 3.4.6.
# There are a number of properties spread across the code that do not appear in 
the docs. For example, zookeeper.allowSaslFailedClients isn't documented afaict.



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

[jira] [Commented] (ZOOKEEPER-2315) Change client connect zk service timeout log level from Info to Warn level

2015-11-05 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on ZOOKEEPER-2315:
--

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

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

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

-1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2944//console

This message is automatically generated.

> Change client connect zk service timeout log level from Info to Warn level
> --
>
> Key: ZOOKEEPER-2315
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2315
> Project: ZooKeeper
>  Issue Type: Wish
>  Components: java client
>Affects Versions: 3.4.6
>Reporter: Lin Yiqun
>Priority: Minor
> Attachments: ZOOKEEPER-2315.001.patch
>
>
> Recently my the resourmanager  of my hadoop cluster is fail suddenly,so I 
> look into the rsourcemanager log.But the log is not helpful for me to direct 
> find the reson until I found the zk timeout info log record.
> {code}
> 2015-11-06 06:34:11,257 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: 
> Assigned container container_1446016482901_292094_01_000140 of capacity 
>  on host mofa2089:41361, which has 30 containers, 
>  used and  available after 
> allocation
> 2015-11-06 06:34:11,266 INFO org.apache.zookeeper.ClientCnxn: Unable to 
> reconnect to ZooKeeper service, session 0x24f4fd5118e5c6e has expired, 
> closing socket connection
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl: 
> container_1446016482901_292094_01_000105 Container Transitioned from RUNNING 
> to COMPLETED
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSAppAttempt: 
> Completed container: container_1446016482901_292094_01_000105 in state: 
> COMPLETED event:FINISHED
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dongwei  
> OPERATION=AM Released Container TARGET=SchedulerApp RESULT=SUCCESS  
> APPID=application_1446016482901_292094  
> CONTAINERID=container_1446016482901_292094_01_000105
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: 
> Released container container_1446016482901_292094_01_000105 of capacity 
>  on host mofa010079:50991, which currently has 29 
> containers,  used and  
> available, release resources=true
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler: 
> Application attempt appattempt_1446016482901_292094_01 released container 
> container_1446016482901_292094_01_000105 on node: host: mofa010079:50991 
> #containers=29 available= used= vCores:29> with event: FINISHED
> 2015-11-06 06:34:11,272 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl: 
> container_1446016482901_292094_01_000141 Container Transitioned from NEW to 
> ALLOCATED
> 2015-11-06 06:34:11,272 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dongwei  
> OPERATION=AM Allocated ContainerTARGET=SchedulerApp 
> RESULT=SUCCESS  APPID=application_1446016482901_292094  
> CONTAINERID=container_1446016482901_292094_01_000141
> 2015-11-06 06:34:11,272 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: 
> Assigned container container_1446016482901_292094_01_000141 of capacity 
>  on host mofa010079:50991, which has 30 containers, 
>  used and  available after 
> allocation
> 2015-11-06 06:34:11,295 WARN 
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.ApplicationMasterLauncher:
>  
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.ApplicationMasterLauncher$LauncherThread
>  interrupted. Returning.
> 2015-11-06 06:34:11,296 INFO org.apache.hadoop.ipc.Server: Stopping server on 
> 8032
> 2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server Responder
> 2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server:

[jira] [Commented] (ZOOKEEPER-2315) Change client connect zk service timeout log level from Info to Warn level

2015-11-05 Thread Michi Mutsuzaki (JIRA) 

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

Michi Mutsuzaki commented on ZOOKEEPER-2315:


Thanks for the patch [~linyiqun]. Could you define string variables for these 
messages so that you can use them for both logging and exception?

> Change client connect zk service timeout log level from Info to Warn level
> --
>
> Key: ZOOKEEPER-2315
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2315
> Project: ZooKeeper
>  Issue Type: Wish
>  Components: java client
>Affects Versions: 3.4.6
>Reporter: Lin Yiqun
>Priority: Minor
> Attachments: ZOOKEEPER-2315.001.patch
>
>
> Recently my the resourmanager  of my hadoop cluster is fail suddenly,so I 
> look into the rsourcemanager log.But the log is not helpful for me to direct 
> find the reson until I found the zk timeout info log record.
> {code}
> 2015-11-06 06:34:11,257 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: 
> Assigned container container_1446016482901_292094_01_000140 of capacity 
>  on host mofa2089:41361, which has 30 containers, 
>  used and  available after 
> allocation
> 2015-11-06 06:34:11,266 INFO org.apache.zookeeper.ClientCnxn: Unable to 
> reconnect to ZooKeeper service, session 0x24f4fd5118e5c6e has expired, 
> closing socket connection
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl: 
> container_1446016482901_292094_01_000105 Container Transitioned from RUNNING 
> to COMPLETED
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSAppAttempt: 
> Completed container: container_1446016482901_292094_01_000105 in state: 
> COMPLETED event:FINISHED
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dongwei  
> OPERATION=AM Released Container TARGET=SchedulerApp RESULT=SUCCESS  
> APPID=application_1446016482901_292094  
> CONTAINERID=container_1446016482901_292094_01_000105
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: 
> Released container container_1446016482901_292094_01_000105 of capacity 
>  on host mofa010079:50991, which currently has 29 
> containers,  used and  
> available, release resources=true
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler: 
> Application attempt appattempt_1446016482901_292094_01 released container 
> container_1446016482901_292094_01_000105 on node: host: mofa010079:50991 
> #containers=29 available= used= vCores:29> with event: FINISHED
> 2015-11-06 06:34:11,272 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl: 
> container_1446016482901_292094_01_000141 Container Transitioned from NEW to 
> ALLOCATED
> 2015-11-06 06:34:11,272 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dongwei  
> OPERATION=AM Allocated ContainerTARGET=SchedulerApp 
> RESULT=SUCCESS  APPID=application_1446016482901_292094  
> CONTAINERID=container_1446016482901_292094_01_000141
> 2015-11-06 06:34:11,272 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: 
> Assigned container container_1446016482901_292094_01_000141 of capacity 
>  on host mofa010079:50991, which has 30 containers, 
>  used and  available after 
> allocation
> 2015-11-06 06:34:11,295 WARN 
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.ApplicationMasterLauncher:
>  
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.ApplicationMasterLauncher$LauncherThread
>  interrupted. Returning.
> 2015-11-06 06:34:11,296 INFO org.apache.hadoop.ipc.Server: Stopping server on 
> 8032
> 2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server Responder
> 2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server: Stopping server on 
> 8030
> 2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server listener on 8032
> 2015-11-06 06:34:11,298 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server Responder
> 2015-11-06 06:34:11,298 INFO org.apache.hadoop.ipc.Server: Stopping server on 
> 8031
> 2015-11-06 06:34:11,298 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server listener on 8030
> 2015-11-06 06:34:11,300 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server listener on 80312015-11-06 06:34:11,300 INFO 
>

[jira] [Updated] (ZOOKEEPER-2315) Change client connect zk service timeout log level from Info to Warn level

2015-11-05 Thread Michi Mutsuzaki (JIRA) 

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

Michi Mutsuzaki updated ZOOKEEPER-2315:
---
Fix Version/s: 3.6.0
   3.5.2
   3.4.7

> Change client connect zk service timeout log level from Info to Warn level
> --
>
> Key: ZOOKEEPER-2315
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2315
> Project: ZooKeeper
>  Issue Type: Wish
>  Components: java client
>Affects Versions: 3.4.6
>Reporter: Lin Yiqun
>Priority: Minor
> Fix For: 3.4.7, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2315.001.patch
>
>
> Recently my the resourmanager  of my hadoop cluster is fail suddenly,so I 
> look into the rsourcemanager log.But the log is not helpful for me to direct 
> find the reson until I found the zk timeout info log record.
> {code}
> 2015-11-06 06:34:11,257 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: 
> Assigned container container_1446016482901_292094_01_000140 of capacity 
>  on host mofa2089:41361, which has 30 containers, 
>  used and  available after 
> allocation
> 2015-11-06 06:34:11,266 INFO org.apache.zookeeper.ClientCnxn: Unable to 
> reconnect to ZooKeeper service, session 0x24f4fd5118e5c6e has expired, 
> closing socket connection
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl: 
> container_1446016482901_292094_01_000105 Container Transitioned from RUNNING 
> to COMPLETED
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSAppAttempt: 
> Completed container: container_1446016482901_292094_01_000105 in state: 
> COMPLETED event:FINISHED
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dongwei  
> OPERATION=AM Released Container TARGET=SchedulerApp RESULT=SUCCESS  
> APPID=application_1446016482901_292094  
> CONTAINERID=container_1446016482901_292094_01_000105
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: 
> Released container container_1446016482901_292094_01_000105 of capacity 
>  on host mofa010079:50991, which currently has 29 
> containers,  used and  
> available, release resources=true
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler: 
> Application attempt appattempt_1446016482901_292094_01 released container 
> container_1446016482901_292094_01_000105 on node: host: mofa010079:50991 
> #containers=29 available= used= vCores:29> with event: FINISHED
> 2015-11-06 06:34:11,272 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl: 
> container_1446016482901_292094_01_000141 Container Transitioned from NEW to 
> ALLOCATED
> 2015-11-06 06:34:11,272 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dongwei  
> OPERATION=AM Allocated ContainerTARGET=SchedulerApp 
> RESULT=SUCCESS  APPID=application_1446016482901_292094  
> CONTAINERID=container_1446016482901_292094_01_000141
> 2015-11-06 06:34:11,272 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: 
> Assigned container container_1446016482901_292094_01_000141 of capacity 
>  on host mofa010079:50991, which has 30 containers, 
>  used and  available after 
> allocation
> 2015-11-06 06:34:11,295 WARN 
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.ApplicationMasterLauncher:
>  
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.ApplicationMasterLauncher$LauncherThread
>  interrupted. Returning.
> 2015-11-06 06:34:11,296 INFO org.apache.hadoop.ipc.Server: Stopping server on 
> 8032
> 2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server Responder
> 2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server: Stopping server on 
> 8030
> 2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server listener on 8032
> 2015-11-06 06:34:11,298 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server Responder
> 2015-11-06 06:34:11,298 INFO org.apache.hadoop.ipc.Server: Stopping server on 
> 8031
> 2015-11-06 06:34:11,298 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server listener on 8030
> 2015-11-06 06:34:11,300 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server listener on 80312015-11-06 06:34:11,300 INFO 
> org.apache.hadoop.ipc.Server: Stopping IPC Server Responder
> {code}
> The

[jira] [Updated] (ZOOKEEPER-2315) Change client connect zk service timeout log level from Info to Warn level

2015-11-05 Thread Lin Yiqun (JIRA) 

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

Lin Yiqun updated ZOOKEEPER-2315:
-
Attachment: ZOOKEEPER-2315.001.patch

> Change client connect zk service timeout log level from Info to Warn level
> --
>
> Key: ZOOKEEPER-2315
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2315
> Project: ZooKeeper
>  Issue Type: Wish
>  Components: java client
>Affects Versions: 3.4.6
>Reporter: Lin Yiqun
>Priority: Minor
> Attachments: ZOOKEEPER-2315.001.patch
>
>
> Recently my the resourmanager  of my hadoop cluster is fail suddenly,so I 
> look into the rsourcemanager log.But the log is not helpful for me to direct 
> find the reson until I found the zk timeout info log record.
> {code}
> 2015-11-06 06:34:11,257 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: 
> Assigned container container_1446016482901_292094_01_000140 of capacity 
>  on host mofa2089:41361, which has 30 containers, 
>  used and  available after 
> allocation
> 2015-11-06 06:34:11,266 INFO org.apache.zookeeper.ClientCnxn: Unable to 
> reconnect to ZooKeeper service, session 0x24f4fd5118e5c6e has expired, 
> closing socket connection
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl: 
> container_1446016482901_292094_01_000105 Container Transitioned from RUNNING 
> to COMPLETED
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSAppAttempt: 
> Completed container: container_1446016482901_292094_01_000105 in state: 
> COMPLETED event:FINISHED
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dongwei  
> OPERATION=AM Released Container TARGET=SchedulerApp RESULT=SUCCESS  
> APPID=application_1446016482901_292094  
> CONTAINERID=container_1446016482901_292094_01_000105
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: 
> Released container container_1446016482901_292094_01_000105 of capacity 
>  on host mofa010079:50991, which currently has 29 
> containers,  used and  
> available, release resources=true
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler: 
> Application attempt appattempt_1446016482901_292094_01 released container 
> container_1446016482901_292094_01_000105 on node: host: mofa010079:50991 
> #containers=29 available= used= vCores:29> with event: FINISHED
> 2015-11-06 06:34:11,272 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl: 
> container_1446016482901_292094_01_000141 Container Transitioned from NEW to 
> ALLOCATED
> 2015-11-06 06:34:11,272 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dongwei  
> OPERATION=AM Allocated ContainerTARGET=SchedulerApp 
> RESULT=SUCCESS  APPID=application_1446016482901_292094  
> CONTAINERID=container_1446016482901_292094_01_000141
> 2015-11-06 06:34:11,272 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: 
> Assigned container container_1446016482901_292094_01_000141 of capacity 
>  on host mofa010079:50991, which has 30 containers, 
>  used and  available after 
> allocation
> 2015-11-06 06:34:11,295 WARN 
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.ApplicationMasterLauncher:
>  
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.ApplicationMasterLauncher$LauncherThread
>  interrupted. Returning.
> 2015-11-06 06:34:11,296 INFO org.apache.hadoop.ipc.Server: Stopping server on 
> 8032
> 2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server Responder
> 2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server: Stopping server on 
> 8030
> 2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server listener on 8032
> 2015-11-06 06:34:11,298 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server Responder
> 2015-11-06 06:34:11,298 INFO org.apache.hadoop.ipc.Server: Stopping server on 
> 8031
> 2015-11-06 06:34:11,298 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server listener on 8030
> 2015-11-06 06:34:11,300 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server listener on 80312015-11-06 06:34:11,300 INFO 
> org.apache.hadoop.ipc.Server: Stopping IPC Server Responder
> {code}
> The problem is solved,but it's too difficult to find the connect zk service 
> time out info from so

Failed: ZOOKEEPER-2315 PreCommit Build #2944

2015-11-05 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2315
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2944/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 109 lines...]
 [exec] PATCH APPLICATION FAILED
 [exec] 
 [exec] 
 [exec] 
 [exec] 
 [exec] -1 overall.  Here are the results of testing the latest attachment 
 [exec]   
http://issues.apache.org/jira/secure/attachment/12770943/ZOOKEEPER-2315.001.patch
 [exec]   against trunk revision 1712218.
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] -1 tests included.  The patch doesn't appear to include any new 
or modified tests.
 [exec] Please justify why no new tests are needed 
for this patch.
 [exec] Also please list what manual steps were 
performed to verify this patch.
 [exec] 
 [exec] -1 patch.  The patch command could not apply the patch.
 [exec] 
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2944//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Comment added.
 [exec] 93206312b71dee26a9d5a5ee3842056932925f01 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

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

Total time: 49 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
ERROR: Publisher 'Publish JUnit test result report' failed: No test report 
files were found. Configuration error?
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-2315
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



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

Re: ZOOKEEPER-1525

2015-11-05 Thread Michi Mutsuzaki 
Thank you for reminding us Tim. I'm taking a look right now.

On Thu, Nov 5, 2015 at 7:54 PM, Crowder Tim  wrote:
> Hi All-
>
> Could I bug someone for a follow-up review on:
>   https://reviews.apache.org/r/33874/
>
> Thanks!
>
> .timrc

[jira] [Commented] (ZOOKEEPER-2315) Change client connect zk service timeout log level from Info to Warn level

2015-11-05 Thread Michi Mutsuzaki (JIRA) 

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

Michi Mutsuzaki commented on ZOOKEEPER-2315:


Also, you need to use --no-prefix if you are generating the patch using git 
diff.

> Change client connect zk service timeout log level from Info to Warn level
> --
>
> Key: ZOOKEEPER-2315
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2315
> Project: ZooKeeper
>  Issue Type: Wish
>  Components: java client
>Affects Versions: 3.4.6
>Reporter: Lin Yiqun
>Priority: Minor
> Fix For: 3.4.7, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2315.001.patch
>
>
> Recently my the resourmanager  of my hadoop cluster is fail suddenly,so I 
> look into the rsourcemanager log.But the log is not helpful for me to direct 
> find the reson until I found the zk timeout info log record.
> {code}
> 2015-11-06 06:34:11,257 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: 
> Assigned container container_1446016482901_292094_01_000140 of capacity 
>  on host mofa2089:41361, which has 30 containers, 
>  used and  available after 
> allocation
> 2015-11-06 06:34:11,266 INFO org.apache.zookeeper.ClientCnxn: Unable to 
> reconnect to ZooKeeper service, session 0x24f4fd5118e5c6e has expired, 
> closing socket connection
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl: 
> container_1446016482901_292094_01_000105 Container Transitioned from RUNNING 
> to COMPLETED
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSAppAttempt: 
> Completed container: container_1446016482901_292094_01_000105 in state: 
> COMPLETED event:FINISHED
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dongwei  
> OPERATION=AM Released Container TARGET=SchedulerApp RESULT=SUCCESS  
> APPID=application_1446016482901_292094  
> CONTAINERID=container_1446016482901_292094_01_000105
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: 
> Released container container_1446016482901_292094_01_000105 of capacity 
>  on host mofa010079:50991, which currently has 29 
> containers,  used and  
> available, release resources=true
> 2015-11-06 06:34:11,271 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler: 
> Application attempt appattempt_1446016482901_292094_01 released container 
> container_1446016482901_292094_01_000105 on node: host: mofa010079:50991 
> #containers=29 available= used= vCores:29> with event: FINISHED
> 2015-11-06 06:34:11,272 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl: 
> container_1446016482901_292094_01_000141 Container Transitioned from NEW to 
> ALLOCATED
> 2015-11-06 06:34:11,272 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dongwei  
> OPERATION=AM Allocated ContainerTARGET=SchedulerApp 
> RESULT=SUCCESS  APPID=application_1446016482901_292094  
> CONTAINERID=container_1446016482901_292094_01_000141
> 2015-11-06 06:34:11,272 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: 
> Assigned container container_1446016482901_292094_01_000141 of capacity 
>  on host mofa010079:50991, which has 30 containers, 
>  used and  available after 
> allocation
> 2015-11-06 06:34:11,295 WARN 
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.ApplicationMasterLauncher:
>  
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.ApplicationMasterLauncher$LauncherThread
>  interrupted. Returning.
> 2015-11-06 06:34:11,296 INFO org.apache.hadoop.ipc.Server: Stopping server on 
> 8032
> 2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server Responder
> 2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server: Stopping server on 
> 8030
> 2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server listener on 8032
> 2015-11-06 06:34:11,298 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server Responder
> 2015-11-06 06:34:11,298 INFO org.apache.hadoop.ipc.Server: Stopping server on 
> 8031
> 2015-11-06 06:34:11,298 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server listener on 8030
> 2015-11-06 06:34:11,300 INFO org.apache.hadoop.ipc.Server: Stopping IPC 
> Server listener on 80312015-11-06 06:34:11,300 INFO 
> org.apache.hadoop.ipc.Server:

[jira] [Created] (ZOOKEEPER-2315) Change client connect zk service timeout log level from Info to Warn level

2015-11-05 Thread Lin Yiqun (JIRA) 
Lin Yiqun created ZOOKEEPER-2315:


 Summary: Change client connect zk service timeout log level from 
Info to Warn level
 Key: ZOOKEEPER-2315
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2315
 Project: ZooKeeper
  Issue Type: Wish
  Components: java client
Affects Versions: 3.4.6
Reporter: Lin Yiqun
Priority: Minor


Recently my the resourmanager  of my hadoop cluster is fail suddenly,so I look 
into the rsourcemanager log.But the log is not helpful for me to direct find 
the reson until I found the zk timeout info log record.
{code}
2015-11-06 06:34:11,257 INFO 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: Assigned 
container container_1446016482901_292094_01_000140 of capacity  on host mofa2089:41361, which has 30 containers,  used and  available after allocation
2015-11-06 06:34:11,266 INFO org.apache.zookeeper.ClientCnxn: Unable to 
reconnect to ZooKeeper service, session 0x24f4fd5118e5c6e has expired, closing 
socket connection
2015-11-06 06:34:11,271 INFO 
org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl: 
container_1446016482901_292094_01_000105 Container Transitioned from RUNNING to 
COMPLETED
2015-11-06 06:34:11,271 INFO 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSAppAttempt: 
Completed container: container_1446016482901_292094_01_000105 in state: 
COMPLETED event:FINISHED
2015-11-06 06:34:11,271 INFO 
org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dongwei  
OPERATION=AM Released Container TARGET=SchedulerApp RESULT=SUCCESS  
APPID=application_1446016482901_292094  
CONTAINERID=container_1446016482901_292094_01_000105
2015-11-06 06:34:11,271 INFO 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: Released 
container container_1446016482901_292094_01_000105 of capacity  on host mofa010079:50991, which currently has 29 containers, 
 used and  available, release 
resources=true
2015-11-06 06:34:11,271 INFO 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler: 
Application attempt appattempt_1446016482901_292094_01 released container 
container_1446016482901_292094_01_000105 on node: host: mofa010079:50991 
#containers=29 available= used= with event: FINISHED
2015-11-06 06:34:11,272 INFO 
org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl: 
container_1446016482901_292094_01_000141 Container Transitioned from NEW to 
ALLOCATED
2015-11-06 06:34:11,272 INFO 
org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=dongwei  
OPERATION=AM Allocated ContainerTARGET=SchedulerApp RESULT=SUCCESS  
APPID=application_1446016482901_292094  
CONTAINERID=container_1446016482901_292094_01_000141
2015-11-06 06:34:11,272 INFO 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: Assigned 
container container_1446016482901_292094_01_000141 of capacity  on host mofa010079:50991, which has 30 containers,  used and  available after allocation
2015-11-06 06:34:11,295 WARN 
org.apache.hadoop.yarn.server.resourcemanager.amlauncher.ApplicationMasterLauncher:
 
org.apache.hadoop.yarn.server.resourcemanager.amlauncher.ApplicationMasterLauncher$LauncherThread
 interrupted. Returning.
2015-11-06 06:34:11,296 INFO org.apache.hadoop.ipc.Server: Stopping server on 
8032
2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server: Stopping IPC Server 
Responder
2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server: Stopping server on 
8030
2015-11-06 06:34:11,297 INFO org.apache.hadoop.ipc.Server: Stopping IPC Server 
listener on 8032
2015-11-06 06:34:11,298 INFO org.apache.hadoop.ipc.Server: Stopping IPC Server 
Responder
2015-11-06 06:34:11,298 INFO org.apache.hadoop.ipc.Server: Stopping server on 
8031
2015-11-06 06:34:11,298 INFO org.apache.hadoop.ipc.Server: Stopping IPC Server 
listener on 8030
2015-11-06 06:34:11,300 INFO org.apache.hadoop.ipc.Server: Stopping IPC Server 
listener on 80312015-11-06 06:34:11,300 INFO org.apache.hadoop.ipc.Server: 
Stopping IPC Server Responder
{code}
The problem is solved,but it's too difficult to find the connect zk service 
time out info from so many info log records.And we will easily to ignore these 
records.So we should chang these zk seesion timeout log level form info level 
to warn.



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

ZOOKEEPER-1525

2015-11-05 Thread Crowder Tim 
Hi All-

Could I bug someone for a follow-up review on:
  https://reviews.apache.org/r/33874/

Thanks!

.timrc

[jira] [Commented] (ZOOKEEPER-1582) EndOfStreamException: Unable to read additional data from client

2015-11-05 Thread zhl (JIRA) 

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

zhl commented on ZOOKEEPER-1582:


I am having same issue here with hbase 1.0.0. ZooKeeper 3.4.6 ,hadoop-2.6.0

the log:
2015-11-06 05:41:16,201 INFO  [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181] 
server.NIOServerCnxn: Closed socket connection for client /192.168.100.1:57498 
which had sessionid 0x150d99328680005
2015-11-06 05:51:09,009 INFO  [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181] 
server.NIOServerCnxnFactory: Accepted socket connection from 
/192.168.100.1:57901
2015-11-06 05:51:09,011 INFO  [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181] 
server.ZooKeeperServer: Client attempting to establish new session at 
/192.168.100.1:57901
2015-11-06 05:51:09,072 INFO  [CommitProcessor:1] server.ZooKeeperServer: 
Established session 0x150d99328680006 with negotiated timeout 9 for client 
/192.168.100.1:57901
2015-11-06 05:52:32,390 WARN  [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181] 
server.NIOServerCnxn: caught end of stream exception
EndOfStreamException: Unable to read additional data from client sessionid 
0x150d99328680006, likely client has closed socket
at 
org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
at 
org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
at java.lang.Thread.run(Thread.java:744)
2015-11-06 05:52:32,393 INFO  [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181] 
server.NIOServerCnxn: Closed socket connection for client /192.168.100.1:57901 
which had sessionid 0x150d99328680006

If anyone can help it will be greatly appreciated !!

Thanks

> EndOfStreamException: Unable to read additional data from client
> 
>
> Key: ZOOKEEPER-1582
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1582
> Project: ZooKeeper
>  Issue Type: Bug
> Environment: windows 7
> jdk 7
>Reporter: zhouyanming
>Priority: Blocker
>
> 1.download zookeeper-3.4.4.tar.gz and unzip
> 2.rename conf/zoo_sample.cfg to zoo.cfg
> 3.click zkServer.cmd
> 4.click zkCli.cmd
> zkCli can not connect to zkServer,it blocked
> zkServer console print
> 2012-11-13 17:28:05,302 [myid:] - WARN  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of 
> stream exception
> EndOfStreamException: Unable to read additional data from client sessionid 
> 0x13af9131eee, likely client has closed socket
> at 
> org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:220)
> at 
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
> at java.lang.Thread.run(Thread.java:722)
> 2012-11-13 17:28:05,308 [myid:] - INFO  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed 
> socket connection for client /127.0.0.1:54810 which had sessionid 
> 0x13af9131eee 



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