You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Attila Sasvari (JIRA)" <ji...@apache.org> on 2017/10/31 10:02:00 UTC

[jira] [Created] (OOZIE-3103) Improve log message regarding max concurrency for coordinators

Attila Sasvari created OOZIE-3103:
-------------------------------------

             Summary: Improve log message regarding max concurrency for coordinators
                 Key: OOZIE-3103
                 URL: https://issues.apache.org/jira/browse/OOZIE-3103
             Project: Oozie
          Issue Type: Improvement
            Reporter: Attila Sasvari
            Priority: Trivial


Currently, when maximum concurrency is reached for coordinators, the log message is as follows:
{code}
2017-09-25 06:00:00,069 WARN org.apache.oozie.command.coord.CoordActionReadyXCommand: SERVER[hpmaster5.lrd.cat.com] USER[testclu0] GROUP[-] TOKEN[] APP[test->dev->xyzabc] JOB[0000065-191474932323346-oozie-oozi-C] ACTION[] No actions to start for jobId=0000065-191474932323346-oozie-oozi-C as max concurrency reached!
{code}

It's confusing as-is and sounds like something is wrong, even though it's perfectly fine. 

We should make it an INFO message and say something more specific and less scary sounding (no exclamation ). Maybe something like "Not starting any additional actions because max concurrency \[<X>] for \[<coordinator>] has been reached"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)