Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-1560

Log messages should have a way of identifying which server they came from when using HA

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: trunk
    • Fix Version/s: 4.1.0
    • Component/s: HA
    • Labels:
      None

      Description

      When using HA, the only way to know which server is processing a specific job is to go into each server's log file and look for log messages about that job; when looking at the logs from the API, there is no way to know.

      This information can be useful, so it would be good to add the server name as part of the log message. This can either be done for logs permanently or can be done when a server is aggregating/collating logs from the other servers. The former is probably more efficient than the latter. If we go with the former, I'd say that we should always do it, regardless of HA so the log formatting is consistent and in case that server is added to an HA group later.

      For example, instead of this:

      2013-09-29 16:46:20,182 WARN org.apache.oozie.command.wf.ActionStartXCommand: USER[root] GROUP[-] TOKEN[] APP[demo-wf] JOB[0000000-130925230553293-oozie-oozi-W] ACTION[0000000-130925230553293-oozie-oozi-W@streaming-node] [***0000000-130925230553293-oozie-oozi-W@streaming-node***]Action status=RUNNING
      

      we can have this:

      2013-09-29 16:46:20,182 WARN org.apache.oozie.command.wf.ActionStartXCommand: USER[root] GROUP[-] SERVER[oozieA] TOKEN[] APP[demo-wf] JOB[0000000-130925230553293-oozie-oozi-W] ACTION[0000000-130925230553293-oozie-oozi-W@streaming-node] [***0000000-130925230553293-oozie-oozi-W@streaming-node***]Action status=RUNNING
      

        Attachments

        1. OOZIE-1560.patch
          22 kB
          Robert Kanter
        2. OOZIE-1560.patch
          22 kB
          Robert Kanter
        3. OOZIE-1560.patch
          22 kB
          Robert Kanter
        4. OOZIE-1560.patch
          22 kB
          Robert Kanter

          Issue Links

            Activity

              People

              • Assignee:
                rkanter Robert Kanter
                Reporter:
                rkanter Robert Kanter
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: