[
https://issues.apache.org/jira/browse/OOZIE-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309319#comment-16309319
]
Julia Kinga Marton commented on OOZIE-3085:
-------------------------------------------
Conclusions after a short discussion with [~asasvari]:
- the actionID is always filled and it follows the following pattern:
jobId@ActionName, but is duplicated, so I will delete it from the log message.
The log entry produced by XLog looks like:
{noformat}2017-12-28 20:01:22,282 INFO ForkActionExecutor:520 -
SERVER[kmarton-mbp] USER[martonjuliakinga] GROUP[-] TOKEN[] APP[Fork_workflow]
JOB[0000004-171228181538280-oozie-mart-W]
ACTION[0000004-171228181538280-oozie-mart-W@fs-paralel] Starting action
[0000004-171228181538280-oozie-mart-W@fs-paralel]{noformat}
- in some cases the external status is the same with the status. However there
are some cases where it differs, but the status is defined based on the
external status, so I think that the external status has more information
content. There is no need for adding the status as well.
- it will be useful to add a log entry when killing an action (where is
supported of course)
- I will think on modifying the actual description to be a little bit more
precise
If I missed something, or some of you have some additional ideas, feel free to
point it out.
> Improve logging in ActionExecutors
> ----------------------------------
>
> Key: OOZIE-3085
> URL: https://issues.apache.org/jira/browse/OOZIE-3085
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: 4.3.0
> Reporter: Peter Cseh
> Assignee: Julia Kinga Marton
> Labels: newbie
> Fix For: 5.0.0
>
> Attachments: OOZIE-3085-001.patch, OOZIE-3085-002.patch,
> OOZIE-3085-003.patch
>
>
> Decision, ForkJoin, Email and FS ActionExecutors are producing no or very
> little logs on info level. This makes it hard to gather usage information and
> help with troubleshooting in the case of any issues. Please improve logging
> in these classes.
> Several subtasks can be separated out from this one
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
