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

Clarify the behavior of timeline service config properties

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.7.1
    • 2.8.0, 2.7.3, 3.0.0-alpha1
    • None
    • None
    • Reviewed

    Description

      Configurations "yarn.timeline-service.enabled" and "yarn.timeline-service.client.best-effort" are not captured better. Currently if the client doesn't want the tokens to be generated for the timeline service they can set "yarn.timeline-service.enabled" to false and/or "yarn.timeline-service.client.best-effort" to true so that even if the ATS is down jobs can continue to get submitted. This functionality is not properly documented, so as part of this jira we try to document and clarify these configurations.

      Attachments

        1. YARN-4183.v1.002.patch
          5 kB
          Naganarasimha G R
        2. YARN-4183.v1.001.patch
          5 kB
          Naganarasimha G R
        3. YARN-4183.1.patch
          3 kB
          Mit Desai

        Issue Links

          depends upon

          New Feature - A new feature of the product, which has yet to be developed. YARN-3623 We should have a config to indicate the Timeline Service version

          • Major - Major loss of function.
          • Resolved
          relates to

          Sub-task - The sub-task of the issue YARN-4356 ensure the timeline service v.2 is disabled cleanly and has no impact when it's turned off

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

          Activity

            People

              Naganarasimha Naganarasimha G R
              mitdesai Mit Desai
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: