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

Increase stability of Oozie actions when log4j.properties is missing or not readable

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.3.0
    • Fix Version/s: 5.0.0b1
    • Component/s: action
    • Labels:
      None

      Description

      In several Oozie actions we face the problem that if log4j.properties is not readable by current thread, or not present on the classpath, while taking an URL.openStream() call afterwards, an IOException is thrown and the action won't run.

      Such actions are:

      Extend LauncherMain.run() by a convenience method that loads Hadoop's log4j.properties in beforehand. In case URL.openStream() would throw IOException we resort to a call to a new file hadoop-default-log4j.properties on the classpath (packaged along w/ LauncherMain.class) that has the same contents as the log4j.properties that is not accessible / readable / present.

        Attachments

        1. OOZIE-2844.003.patch
          37 kB
          Andras Piros
        2. OOZIE-2844.002.patch
          37 kB
          Andras Piros
        3. OOZIE-2844.001.patch
          36 kB
          Andras Piros

          Issue Links

            Activity

              People

              • Assignee:
                andras.piros Andras Piros
                Reporter:
                andras.piros Andras Piros
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: