Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-386 [Umbrella] YARN API Changes
  3. YARN-444

Move special container exit codes from YarnConfiguration to API

    XMLWordPrintableJSON

Details

    • Reviewed

    Description

      YarnConfiguration currently contains the special container exit codes INVALID_CONTAINER_EXIT_STATUS = -1000, ABORTED_CONTAINER_EXIT_STATUS = -100, and DISKS_FAILED = -101.

      These are not really not really related to configuration, and YarnConfiguration should not become a place to put miscellaneous constants.

      Per discussion on YARN-417, appmaster writers need to be able to provide special handling for them, so it might make sense to move these to their own user-facing class.

      Attachments

        1. YARN-444-2.patch
          17 kB
          Sandy Ryza
        2. YARN-444-2.patch
          17 kB
          Sandy Ryza
        3. YARN-444-2.patch
          17 kB
          Sandy Ryza
        4. YARN-444-1.patch
          16 kB
          Sandy Ryza
        5. YARN-444.patch
          13 kB
          Sandy Ryza

        Issue Links

          relates to

          Sub-task - The sub-task of the issue YARN-417 Create AMRMClient wrapper that provides asynchronous callbacks

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MAPREDUCE-5151 Update MR App after YARN-444

          • Major - Major loss of function.
          • Closed

          Activity

            People

              sandyr Sandy Ryza
              sandyr Sandy Ryza
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: