[jira] [Commented] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[ https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905786#comment-15905786 ] Eugene Chekanskiy commented on AMBARI-20323: addendum patch in 0bd7b86..290218f branch-2.5 -> branch-2.5 0471b0c..b69ac43 trunk -> trunk > Commands timed-out on ambari host without any error logs > > > Key: AMBARI-20323 > URL: https://issues.apache.org/jira/browse/AMBARI-20323 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20323.2.patch, AMBARI-20323.3.patch, > AMBARI-20323.4.patch, AMBARI-20323.5.patch, AMBARI-20323.addendum.patch, > AMBARI-20323.patch > > > Ambari-agent stop execution commands. It is happend because of threads > blocking due to broken multiprocessing.Queue after killing > StatusCommandsExecutor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[ https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903450#comment-15903450 ] Hudson commented on AMBARI-20323: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6989 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6989/]) AMBARI-20323. Commands timed-out on ambari host without any error logs (echekanskiy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=da0b7ad8f8974dfdeaf0e99d86339c7562cdd9f2]) * (edit) ambari-agent/src/main/python/ambari_agent/Controller.py * (edit) ambari-agent/src/main/python/ambari_agent/StatusCommandsExecutor.py * (edit) ambari-agent/src/main/python/ambari_agent/main.py * (edit) ambari-agent/src/test/python/ambari_agent/TestActionQueue.py * (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py * (edit) ambari-agent/src/test/python/ambari_agent/TestController.py * (edit) ambari-agent/src/test/python/ambari_agent/TestMain.py > Commands timed-out on ambari host without any error logs > > > Key: AMBARI-20323 > URL: https://issues.apache.org/jira/browse/AMBARI-20323 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20323.2.patch, AMBARI-20323.3.patch, > AMBARI-20323.4.patch, AMBARI-20323.5.patch, AMBARI-20323.patch > > > Ambari-agent stop execution commands. It is happend because of threads > blocking due to broken multiprocessing.Queue after killing > StatusCommandsExecutor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[ https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903441#comment-15903441 ] Hudson commented on AMBARI-20323: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1223 (See [https://builds.apache.org/job/Ambari-branch-2.5/1223/]) AMBARI-20323. Commands timed-out on ambari host without any error logs (echekanskiy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=17ef555940758b73cd09ddcc9fc8a3461604c085]) * (edit) ambari-agent/src/main/python/ambari_agent/StatusCommandsExecutor.py * (edit) ambari-agent/src/test/python/ambari_agent/TestMain.py * (edit) ambari-agent/src/main/python/ambari_agent/Controller.py * (edit) ambari-agent/src/test/python/ambari_agent/TestController.py * (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py * (edit) ambari-agent/src/test/python/ambari_agent/TestActionQueue.py * (edit) ambari-agent/src/main/python/ambari_agent/main.py > Commands timed-out on ambari host without any error logs > > > Key: AMBARI-20323 > URL: https://issues.apache.org/jira/browse/AMBARI-20323 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20323.2.patch, AMBARI-20323.3.patch, > AMBARI-20323.4.patch, AMBARI-20323.5.patch, AMBARI-20323.patch > > > Ambari-agent stop execution commands. It is happend because of threads > blocking due to broken multiprocessing.Queue after killing > StatusCommandsExecutor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[ https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903210#comment-15903210 ] Hadoop QA commented on AMBARI-20323: {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12857003/AMBARI-20323.5.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 3 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in ambari-agent. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/10943//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/10943//console This message is automatically generated. > Commands timed-out on ambari host without any error logs > > > Key: AMBARI-20323 > URL: https://issues.apache.org/jira/browse/AMBARI-20323 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20323.2.patch, AMBARI-20323.3.patch, > AMBARI-20323.4.patch, AMBARI-20323.5.patch, AMBARI-20323.patch > > > Ambari-agent stop execution commands. It is happend because of threads > blocking due to broken multiprocessing.Queue after killing > StatusCommandsExecutor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[ https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899860#comment-15899860 ] Hadoop QA commented on AMBARI-20323: {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12856625/AMBARI-20323.4.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 3 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in ambari-agent. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/10914//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/10914//console This message is automatically generated. > Commands timed-out on ambari host without any error logs > > > Key: AMBARI-20323 > URL: https://issues.apache.org/jira/browse/AMBARI-20323 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20323.2.patch, AMBARI-20323.3.patch, > AMBARI-20323.4.patch, AMBARI-20323.patch > > > Ambari-agent stop execution commands. It is happend because of threads > blocking due to broken multiprocessing.Queue after killing > StatusCommandsExecutor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[ https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899656#comment-15899656 ] Hadoop QA commented on AMBARI-20323: {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12856623/AMBARI-20323.3.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 3 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in ambari-agent. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/10909//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/10909//console This message is automatically generated. > Commands timed-out on ambari host without any error logs > > > Key: AMBARI-20323 > URL: https://issues.apache.org/jira/browse/AMBARI-20323 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20323.2.patch, AMBARI-20323.3.patch, > AMBARI-20323.4.patch, AMBARI-20323.patch > > > Ambari-agent stop execution commands. It is happend because of threads > blocking due to broken multiprocessing.Queue after killing > StatusCommandsExecutor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)