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

2015-11-08 Thread Hudson (JIRA) 

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

Hudson commented on ZOOKEEPER-2315:
---

FAILURE: Integrated in ZooKeeper-trunk #2812 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/2812/])
ZOOKEEPER-2315: Change client connect zk service timeout log level from Info
to Warn level (Lin Yiqun via rgs) (rgs: 
[http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN=rev=1713312])
* trunk/CHANGES.txt
* trunk/src/java/main/org/apache/zookeeper/ClientCnxn.java


> 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: Improvement
>  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, ZOOKEEPER-2315.002.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

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

2015-11-08 Thread Lin Yiqun (JIRA) 

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

Lin Yiqun commented on ZOOKEEPER-2315:
--

Thanks [~rgs]!

> 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: Improvement
>  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, ZOOKEEPER-2315.002.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] [Commented] (ZOOKEEPER-2315) Change client connect zk service timeout log level from Info to Warn level

2015-11-06 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on ZOOKEEPER-2315:
--

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12770995/ZOOKEEPER-2315.002.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 javadoc.  The javadoc tool did not generate any warning messages.

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

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

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

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

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

Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2946//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2946//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2946//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
> Fix For: 3.4.7, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2315.001.patch, ZOOKEEPER-2315.002.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: 
>

[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] [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: