Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.4.0
Description
The standby RM's webui tries to do a redirect via meta-refresh. That is fine for pages designed to be viewed by web browsers. But the API endpoints shouldn't do that. Most programmatic HTTP clients do not do meta-refresh. I'd suggest HTTP 303, or return a well-defined error message (json or xml) stating that the standby status and a link to the active RM.
The standby RM is returning this today:
$ curl -i http://bcsec-1.ent.cloudera.com:8088/ws/v1/cluster/metrics HTTP/1.1 200 OK Cache-Control: no-cache Expires: Thu, 25 Sep 2014 18:34:53 GMT Date: Thu, 25 Sep 2014 18:34:53 GMT Pragma: no-cache Expires: Thu, 25 Sep 2014 18:34:53 GMT Date: Thu, 25 Sep 2014 18:34:53 GMT Pragma: no-cache Content-Type: text/plain; charset=UTF-8 Refresh: 3; url=http://bcsec-2.ent.cloudera.com:8088/ws/v1/cluster/metrics Content-Length: 117 Server: Jetty(6.1.26) This is standby RM. Redirecting to the current active RM: http://bcsec-2.ent.cloudera.com:8088/ws/v1/cluster/metrics
Attachments
Attachments
Issue Links
- blocks
-
SLIDER-846 [RM HA] Slider Application Master url from RM UI complains "This is standby RM"
- Open
- is depended upon by
-
SLIDER-151 Implement full slider API in REST and switch client to it
- Open
-
YARN-2084 YARN to support REST APIs in AMs
- Open
- is duplicated by
-
YARN-4112 YARN HA secondary-RM/NM redirect not parseable by Ambari/curl in a Kerberoized deployment
- Open
- is related to
-
KNOX-1581 YARN v1 UI - Application - Node and logs links broken
- Closed
-
YARN-3601 Fix UT TestRMFailover.testRMWebAppRedirect
- Closed
-
YARN-3526 ApplicationMaster tracking URL is incorrectly redirected on a QJM cluster
- Closed
- relates to
-
AMBARI-12995 Ambari alerts reports "UNKNOWN" error for secondary YARN RM and NM in a kerberoized YARN HA deployment
- Open
-
YARN-3654 ContainerLogsPage web UI should not have meta-refresh
- Resolved
-
YARN-3193 When visit standby RM webui, it will redirect to the active RM webui slowly.
- Closed