Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-2836

RM behaviour on token renewal failures is broken

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • resourcemanager
    • None

    Description

      Found this while reviewing YARN-2834.

      We now completely ignore token renewal failures. For things like Timeline tokens which are automatically obtained whether the app needs it or not (we should fix this to be user driven), we can ignore failures. But for HDFS Tokens etc, ignoring failures is bad because it (1) wastes resources as AMs will continue and eventually fail (2) app doesn't know what happened it fails eventually.

      Attachments

        Issue Links

          is related to

          Sub-task - The sub-task of the issue YARN-342 RM doesn't retry token renewals

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. YARN-3021 YARN's delegation-token handling disallows certain trust setups to operate properly over DistCp

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. YARN-2834 Resource manager crashed with Null Pointer Exception

          • Blocker - Blocks development and/or testing work, production could not run
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated: