[
https://issues.apache.org/jira/browse/OOZIE-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234472#comment-15234472
]
Satish Subhashrao Saley commented on OOZIE-2506:
------------------------------------------------
{{non-binding}}
It would be good to have wording of logs in similar fashion for all of the
three - bundle, coord and workflow.
For bundle and workflow, we have
{code}
log.debug("Recover a bundle action from [KILLED] status and resubmit
CoordKillXCommand :[{0}]", baction.getCoordId());
log.debug("Recover a workflow action from [{0}] status and resubmit
ActionEndXCommand :[{1}]",action.getStatus(), action.getId());
{code}
But for coord
{code}
log.debug("Recover a [KILLED] coord action and resubmit KillXCommand :[{0}]",
caction.getId());
{code}
It's nice to be consistent
{code}
log.debug("Recover a coord action from [KILLED] status and resubmit
KillXCommand :[{0}]", caction.getId());
{code}
> Add logs into RecoverService for logging information about queued commnads
> --------------------------------------------------------------------------
>
> Key: OOZIE-2506
> URL: https://issues.apache.org/jira/browse/OOZIE-2506
> Project: Oozie
> Issue Type: Bug
> Components: core
> Reporter: abhishek bafna
> Assignee: abhishek bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2506-01.patch
>
>
> Currently, RecoveryService does not logs information about workflow actions
> commands and coordinator commands. It just logs the counter for different
> commands got queued. Logging the different commands after queuing can be
> helpful in debugging a system which have a lot work load.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
