Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-3648 ContainerExecutor interface methods are too brittle
  3. YARN-3685

NodeManager unnecessarily knows about classpath-jars due to Windows limitations

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • nodemanager
    • None

    Description

      Found this while looking at cleaning up ContainerExecutor via YARN-3648, making it a sub-task.

      YARN should not know about classpaths. Our original design modeled around this. But when we added windows suppport, due to classpath issues, we ended up breaking this abstraction via YARN-316. We should clean this up.

      Attachments

        Issue Links

          is broken by

          Bug - A problem which impairs or prevents the functions of the product. YARN-316 YARN container launch may exceed maximum Windows command line length due to long classpath

          • Major - Major loss of function.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. YARN-3626 On Windows localized resources are not moved to the front of the classpath when they should be

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              vinodkv Vinod Kumar Vavilapalli
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: