[jira] [Commented] (AMBARI-15393) Add stderr output of Ambari auto-recovery commands in agent log
[ https://issues.apache.org/jira/browse/AMBARI-15393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15211181#comment-15211181 ] Hudson commented on AMBARI-15393: - ABORTED: Integrated in Ambari-trunk-Commit #4541 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4541/]) AMBARI-15393. Add stderr output of Ambari auto-recovery commands in (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=769c39cee604304ee566fe272ff3fe3df061aa78]) * ambari-agent/src/main/python/ambari_agent/ActionQueue.py > Add stderr output of Ambari auto-recovery commands in agent log > --- > > Key: AMBARI-15393 > URL: https://issues.apache.org/jira/browse/AMBARI-15393 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.1 >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15393.patch, AMBARI-15393_branch-2.2.patch > > > Users rely on Ambari auto-recovery logic to recover from component start > failures during cluster create. The idea is to improve reliability (through > retries) by sacrificing some of the latency. > In some cases we see that cluster creates fail because component start fails > and auto-recovery is unable to start those components for up to 2 hrs, most > often on headnodes for HIVE_SERVER, OOZIE_SERVER, and NAMENODE components. > The problem these kind of problems are hard to investigate later, as auto > recovery files are not sent to server side nor they are saved in ambari agent > logs, only stored on agent . > The solution is to add a new an option *logging.log_command_executes* in to > *ambari-agent.ini*. In case this is enabled agent will append stderr of all > commands (including auto_execute commands) to agent log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15393) Add stderr output of Ambari auto-recovery commands in agent log
[ https://issues.apache.org/jira/browse/AMBARI-15393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210824#comment-15210824 ] Hudson commented on AMBARI-15393: - FAILURE: Integrated in Ambari-branch-2.2 #553 (See [https://builds.apache.org/job/Ambari-branch-2.2/553/]) AMBARI-15393. Add stderr output of Ambari auto-recovery commands in (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=58a32083f3f3d3c04b7bce65d074da7be4254bbf]) * ambari-agent/src/main/python/ambari_agent/ActionQueue.py > Add stderr output of Ambari auto-recovery commands in agent log > --- > > Key: AMBARI-15393 > URL: https://issues.apache.org/jira/browse/AMBARI-15393 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.1 >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15393.patch, AMBARI-15393_branch-2.2.patch > > > Users rely on Ambari auto-recovery logic to recover from component start > failures during cluster create. The idea is to improve reliability (through > retries) by sacrificing some of the latency. > In some cases we see that cluster creates fail because component start fails > and auto-recovery is unable to start those components for up to 2 hrs, most > often on headnodes for HIVE_SERVER, OOZIE_SERVER, and NAMENODE components. > The problem these kind of problems are hard to investigate later, as auto > recovery files are not sent to server side nor they are saved in ambari agent > logs, only stored on agent . > The solution is to add a new an option *logging.log_command_executes* in to > *ambari-agent.ini*. In case this is enabled agent will append stderr of all > commands (including auto_execute commands) to agent log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15393) Add stderr output of Ambari auto-recovery commands in agent log
[ https://issues.apache.org/jira/browse/AMBARI-15393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210723#comment-15210723 ] Sandor Magyari commented on AMBARI-15393: - To enable logging of commands by agent add *logging.log_command_executes = 1* in to *ambari-agent.ini* > Add stderr output of Ambari auto-recovery commands in agent log > --- > > Key: AMBARI-15393 > URL: https://issues.apache.org/jira/browse/AMBARI-15393 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.1 >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15393.patch, AMBARI-15393_branch-2.2.patch > > > Users rely on Ambari auto-recovery logic to recover from component start > failures during cluster create. The idea is to improve reliability (through > retries) by sacrificing some of the latency. > In some cases we see that cluster creates fail because component start fails > and auto-recovery is unable to start those components for up to 2 hrs, most > often on headnodes for HIVE_SERVER, OOZIE_SERVER, and NAMENODE components. > The problem these kind of problems are hard to investigate later, as auto > recovery files are not sent to server side nor they are saved in ambari agent > logs, only stored on agent . > The solution is to add a new an option *logging.log_command_executes* in to > *ambari-agent.ini*. In case this is enabled agent will append stderr of all > commands (including auto_execute commands) to agent log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15393) Add stderr output of Ambari auto-recovery commands in agent log
[ https://issues.apache.org/jira/browse/AMBARI-15393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210707#comment-15210707 ] Sumit Mohanty commented on AMBARI-15393: [~smagyari] can you add details on what config properties can be set to enable logging command outputs to agent log. > Add stderr output of Ambari auto-recovery commands in agent log > --- > > Key: AMBARI-15393 > URL: https://issues.apache.org/jira/browse/AMBARI-15393 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.1 >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15393.patch, AMBARI-15393_branch-2.2.patch > > > Users rely on Ambari auto-recovery logic to recover from component start > failures during cluster create. The idea is to improve reliability (through > retries) by sacrificing some of the latency. > In some cases we see that cluster creates fail because component start fails > and auto-recovery is unable to start those components for up to 2 hrs, most > often on headnodes for HIVE_SERVER, OOZIE_SERVER, and NAMENODE components. > The problem these kind of problems are hard to investigate later, as auto > recovery files are not sent to server side nor they are saved in ambari agent > logs, only stored on agent . > The solution is to add a new an option log_auto_execute_errors in logging > section to ambari-agent.ini. In case this is enabled agent will append stderr > of auto recovery command to agent log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15393) Add stderr output of Ambari auto-recovery commands in agent log
[ https://issues.apache.org/jira/browse/AMBARI-15393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210666#comment-15210666 ] Sandor Magyari commented on AMBARI-15393: - Commited to trunk, branch-2.2 > Add stderr output of Ambari auto-recovery commands in agent log > --- > > Key: AMBARI-15393 > URL: https://issues.apache.org/jira/browse/AMBARI-15393 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.1 >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15393.patch, AMBARI-15393_branch-2.2.patch > > > Users rely on Ambari auto-recovery logic to recover from component start > failures during cluster create. The idea is to improve reliability (through > retries) by sacrificing some of the latency. > In some cases we see that cluster creates fail because component start fails > and auto-recovery is unable to start those components for up to 2 hrs, most > often on headnodes for HIVE_SERVER, OOZIE_SERVER, and NAMENODE components. > The problem these kind of problems are hard to investigate later, as auto > recovery files are not sent to server side nor they are saved in ambari agent > logs, only stored on agent . > The solution is to add a new an option log_auto_execute_errors in logging > section to ambari-agent.ini. In case this is enabled agent will append stderr > of auto recovery command to agent log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15393) Add stderr output of Ambari auto-recovery commands in agent log
[
https://issues.apache.org/jira/browse/AMBARI-15393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210349#comment-15210349
]
Hadoop QA commented on AMBARI-15393:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12795053/AMBARI-15393_branch-2.2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. 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.
{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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6004//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6004//console
This message is automatically generated.
> Add stderr output of Ambari auto-recovery commands in agent log
> ---
>
> Key: AMBARI-15393
> URL: https://issues.apache.org/jira/browse/AMBARI-15393
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.2.1
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15393.patch, AMBARI-15393_branch-2.2.patch
>
>
> Users rely on Ambari auto-recovery logic to recover from component start
> failures during cluster create. The idea is to improve reliability (through
> retries) by sacrificing some of the latency.
> In some cases we see that cluster creates fail because component start fails
> and auto-recovery is unable to start those components for up to 2 hrs, most
> often on headnodes for HIVE_SERVER, OOZIE_SERVER, and NAMENODE components.
> The problem these kind of problems are hard to investigate later, as auto
> recovery files are not sent to server side nor they are saved in ambari agent
> logs, only stored on agent .
> The solution is to add a new an option log_auto_execute_errors in logging
> section to ambari-agent.ini. In case this is enabled agent will append stderr
> of auto recovery command to agent log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15393) Add stderr output of Ambari auto-recovery commands in agent log
[
https://issues.apache.org/jira/browse/AMBARI-15393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15191530#comment-15191530
]
Hadoop QA commented on AMBARI-15393:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12792873/AMBARI-15393.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. 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.
{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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5833//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5833//console
This message is automatically generated.
> Add stderr output of Ambari auto-recovery commands in agent log
> ---
>
> Key: AMBARI-15393
> URL: https://issues.apache.org/jira/browse/AMBARI-15393
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.2.1
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15393.patch
>
>
> Users rely on Ambari auto-recovery logic to recover from component start
> failures during cluster create. The idea is to improve reliability (through
> retries) by sacrificing some of the latency.
> In some cases we see that cluster creates fail because component start fails
> and auto-recovery is unable to start those components for up to 2 hrs, most
> often on headnodes for HIVE_SERVER, OOZIE_SERVER, and NAMENODE components.
> The problem these kind of problems are hard to investigate later, as auto
> recovery files are not sent to server side nor they are saved in ambari agent
> logs, only stored on agent .
> The solution is to add a new an option log_auto_execute_errors in logging
> section to ambari-agent.ini. In case this is enabled agent will append stderr
> of auto recovery command to agent log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
