[
https://issues.apache.org/jira/browse/AMBARI-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
