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

provide an option to auto-deploy launcher jar onto HDFS system libpath

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • trunk
    • 4.1.0
    • None
    • None

    Description

      after OOZIE-1311, 1315, when oozie.action.ship.launcher.jar is false, launcher jar is shipped from sharelib, but it requires manual process for admin people to upload jar files onto the sharelib at server-start time, before actually starting running workflow actions. This JIRA to provide an option to remove the manual process, and make oozie server (ActionService) to automatically create and upload launcher jar files onto HDFS (tmp directory under oozie.service.WorkflowAppService.system.libpath), and allow workflow actions to consume from there. every time oozie server starts, it automatically creates a new directory to upload launcher jars to, and also purges stale directories previously created (older than 7 days, configurable).
      if false (which is current default). the behavior is the same with previous, launcher jars provided from sharelib (when oozie.action.ship.launcher.jar=false) or each workflow action creates and ships launcher jar (when oozie.action.ship.launcher.jar=true)

      Attachments

        1. OOZIE-1461.patch
          65 kB
          Virag Kothari
        2. OOZIE-1461.patch
          66 kB
          Virag Kothari
        3. OOZIE-1461.patch
          66 kB
          Virag Kothari
        4. OOZIE-1461_2.patch
          66 kB
          Virag Kothari
        5. OOZIE-1461_2.patch
          66 kB
          Virag Kothari

        Issue Links

          Activity

            People

              virag Virag Kothari
              egashira Ryota Egashira
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: