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

When visit standby RM webui, it will redirect to the active RM webui slowly.

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: webapp
    • Labels:
      None

      Description

      when visit the standby RM web ui, it will redirect to the active RM web ui. but this redirect is very slow which give client bad experience. I have try to visit standby namenode, it directly show the web to client quickly. So, can we improve this experience with YARN like HDFS.

        Issue Links

          Activity

          Hide
          rohithsharma Rohith Sharma K S added a comment -

          Redirecting to Active RM is behaviour in RM HA feature RM HA Web UI Doc.
          This is mainly because standBy RM does not starts any activeServices for serving requests, so for the user connecting to standbyRM does not get any information about the applications or metrics. And the user need not worry for always identifying activeRM web page on every switch. But in case of NameNode HA, it is different behaviour i.e all the datanodes reports to standby NameNode also, so that you can see some of the statistics like blockreport etc.

          but this redirect is very slow

          This can be reduced by configuring some of the retry parameters. Refer RM HA Conf Doc

          Show
          rohithsharma Rohith Sharma K S added a comment - Redirecting to Active RM is behaviour in RM HA feature RM HA Web UI Doc . This is mainly because standBy RM does not starts any activeServices for serving requests, so for the user connecting to standbyRM does not get any information about the applications or metrics. And the user need not worry for always identifying activeRM web page on every switch. But in case of NameNode HA, it is different behaviour i.e all the datanodes reports to standby NameNode also, so that you can see some of the statistics like blockreport etc. but this redirect is very slow This can be reduced by configuring some of the retry parameters. Refer RM HA Conf Doc
          Hide
          cheersyang Weiwei Yang added a comment -

          The redirect seems to happen in 3 seconds, if that what you means by slow.

          Show
          cheersyang Weiwei Yang added a comment - The redirect seems to happen in 3 seconds, if that what you means by slow.
          Hide
          cwelch Craig Welch added a comment -

          I believe the redirect intentionally takes a moment to allow the user to see that they did not hit the active rm, which is useful to them. In any case, it does not take very long, and the length of time can be adjusted if desired. I think this can be resolved, Japs_123 if you strongly feel otherwise, pls feel free to reopen & explain.

          Show
          cwelch Craig Welch added a comment - I believe the redirect intentionally takes a moment to allow the user to see that they did not hit the active rm, which is useful to them. In any case, it does not take very long, and the length of time can be adjusted if desired. I think this can be resolved, Japs_123 if you strongly feel otherwise, pls feel free to reopen & explain.
          Hide
          stevel@apache.org Steve Loughran added a comment -

          This was fixed in YARN-2605 by switching from some meta-refresh thing to simply returning 302/307 & letting the browser handle it. Closing as fixed

          Show
          stevel@apache.org Steve Loughran added a comment - This was fixed in YARN-2605 by switching from some meta-refresh thing to simply returning 302/307 & letting the browser handle it. Closing as fixed

            People

            • Assignee:
              stevel@apache.org Steve Loughran
              Reporter:
              Japol Japs_123
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development