[jira] [Commented] (AMBARI-16630) Extend logging for ActionQueue's retry logic

2016-05-18 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15288680#comment-15288680
 ] 

Hudson commented on AMBARI-16630:
-

FAILURE: Integrated in Ambari-trunk-Commit #4864 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4864/])
AMBARI-16630. Extend logging for ActionQueue's retry logic. (Daniel (stoader: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=40fe30bfe7d58ce56e128d8c09be6cb947eff92f])
* ambari-agent/src/main/python/ambari_agent/ActionQueue.py
* ambari-agent/src/test/python/ambari_agent/TestActionQueue.py
AMBARI-16630. Extend logging for ActionQueue's retry logic (part2). (stoader: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7d516272c6a035e0bd970cb592061ea08a40a942])
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java


> Extend logging for ActionQueue's retry logic
> 
>
> Key: AMBARI-16630
> URL: https://issues.apache.org/jira/browse/AMBARI-16630
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-agent
>Reporter: Daniel Gergely
>Assignee: Daniel Gergely
> Fix For: 2.4.0, 2.2-next
>
> Attachments: AMBARI-16630.patch, AMBARI-16630_2.2-next.patch, 
> AMBARI-16630_addendum.patch
>
>
> At info level, commands should be tracked if they are retried on failure or 
> not, and if not, what is the reason for that.



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

[jira] [Commented] (AMBARI-16630) Extend logging for ActionQueue's retry logic

2016-05-18 Thread Daniel Gergely (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15288532#comment-15288532
 ] 

Daniel Gergely commented on AMBARI-16630:
-

Ok, good idea! Thanks

> Extend logging for ActionQueue's retry logic
> 
>
> Key: AMBARI-16630
> URL: https://issues.apache.org/jira/browse/AMBARI-16630
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-agent
>Reporter: Daniel Gergely
>Assignee: Daniel Gergely
> Fix For: 2.4.0, 2.2-next
>
> Attachments: AMBARI-16630.patch, AMBARI-16630_2.2-next.patch, 
> AMBARI-16630_addendum.patch
>
>
> At info level, commands should be tracked if they are retried on failure or 
> not, and if not, what is the reason for that.



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

[jira] [Commented] (AMBARI-16630) Extend logging for ActionQueue's retry logic

2016-05-17 Thread Sumit Mohanty (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15288081#comment-15288081
 ] 

Sumit Mohanty commented on AMBARI-16630:


[~dgergely] can you take a look and see if we can also make one change to the 
server to log the config properties - see 
[attachment|https://issues.apache.org/jira/secure/attachment/12804570/AMBARI-16630_addendum.patch]

> Extend logging for ActionQueue's retry logic
> 
>
> Key: AMBARI-16630
> URL: https://issues.apache.org/jira/browse/AMBARI-16630
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-agent
>Reporter: Daniel Gergely
>Assignee: Daniel Gergely
> Fix For: 2.4.0, 2.2-next
>
> Attachments: AMBARI-16630.patch, AMBARI-16630_2.2-next.patch, 
> AMBARI-16630_addendum.patch
>
>
> At info level, commands should be tracked if they are retried on failure or 
> not, and if not, what is the reason for that.



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

[jira] [Commented] (AMBARI-16630) Extend logging for ActionQueue's retry logic

2016-05-14 Thread Sumit Mohanty (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15283658#comment-15283658
 ] 

Sumit Mohanty commented on AMBARI-16630:


[~dgergely] can we add taskId as there are parallel execution so logs may 
intersperse. Rest of the changes look good.

e.g.

{code}
logger.info("Command execution metadata - taskId = {taskId}, retry enabled = 
{retryAble}, max retry duration (sec) = {retryDuration}".
  format(taskId=taskId, retryAble=retryAble, 
retryDuration=retryDuration))
{code}

> Extend logging for ActionQueue's retry logic
> 
>
> Key: AMBARI-16630
> URL: https://issues.apache.org/jira/browse/AMBARI-16630
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-agent
>Reporter: Daniel Gergely
>Assignee: Daniel Gergely
> Fix For: 2.4.0, 2.2-next
>
> Attachments: AMBARI-16630.patch, AMBARI-16630_2.2-next.patch
>
>
> At info level, commands should be tracked if they are retried on failure or 
> not, and if not, what is the reason for that.



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