Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
trunk
-
None
-
None
Description
For example,
WARN CallableQueueService:542 - USER[-] GROUP[-] queue if full, ignoring queuing for [(org.apache.oozie.command.wf.SignalXCommand@5c819194),(org.apache.oozie.command.wf.ActionEndXCommand@3e7cbafe),(org.apache.oozie.command.wf.SignalXCommand@6ed899be),(org.apache.oozie.command.wf.ActionEndXCommand@4e55c1cc),(org.apache.oozie.command.wf.ActionStartXCommand@60266041),(org.apache.oozie.command.wf.ActionStartXCommand@77797cb7),(org.apache.oozie.command.wf.ActionStartXCommand@48eb0fa8),(org.apache.oozie.command.wf.ActionStartXCommand@405103fe),(org.apache.oozie.command.wf.ActionStartXCommand@6dd39af),(org.apache.oozie.command.wf.ActionStartXCommand@25f613ae)]
is an illustration of log messages being unclear. This one prints out the reference address information for the command instead of any meaningful info such as job-id, and user whom this command pertains to.
The log messages around callable commands can be fixed in a few other places too.
Attachments
Attachments
Issue Links
- links to