Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-321 [Umbrella] Generic application history service
  3. YARN-304

RM Tracking Links for purged applications needs a long-term solution

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Won't Fix
    • 0.23.5, 3.0.0-alpha1
    • None
    • None
    • None

    Description

      This JIRA is intended to track a proper long-term fix for the issue described in YARN-285.

      The following is from the original description:

      As applications complete, the RM tracks their IDs in a completed list. This list is routinely truncated to limit the total number of application remembered by the RM.

      When a user clicks the History for a job, either the browser is redirected to the application's tracking link obtained from the stored application instance. But when the application has been purged from the RM, an error is displayed.

      In very busy clusters the rate at which applications complete can cause applications to be purged from the RM's internal list within hours, which breaks the proxy URLs users have saved for their jobs.

      We would like the RM to provide valid tracking links persist so that users are not frustrated by broken links.

      Attachments

        1. YARN-304-1.patch
          6 kB
          Mayank Bansal

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mayank_bansal Mayank Bansal
            dagit Derek Dagit
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment