hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuan Gong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1157) ResourceManager UI has invalid tracking URL link for distributed shell application
Date Wed, 18 Sep 2013 00:55:52 GMT

    [ https://issues.apache.org/jira/browse/YARN-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770258#comment-13770258

Xuan Gong commented on YARN-1157:

bq.all users of the trackingUrl, for e.g. ApplicationReport will have the same issue. So let's
make sure that once registration and finish-app is done, the url in RM's memory is always
"N/A" if not explicitly set by AM.

Adding this logic in both AMRegisteredTransition/AMUnregisteredTransition
      String url = registrationEvent.getTrackingurl();
      if (url == null || url.trim().isEmpty()) {
        appAttempt.origTrackingUrl = "N/A";
      } else {
        appAttempt.origTrackingUrl = url;

bq.Let's document RegisterApplicationMasterRequest.getTrackingUrl() and setTrackingUrl() to
describe that empty, null, "N/A" strings are all valid besides a real URL.


bq.Similarly FinishApplicationMasterRequest.


Also added a new testcase, fixed the testcase failure
> ResourceManager UI has invalid tracking URL link for distributed shell application
> ----------------------------------------------------------------------------------
>                 Key: YARN-1157
>                 URL: https://issues.apache.org/jira/browse/YARN-1157
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Tassapol Athiapinya
>            Assignee: Xuan Gong
>             Fix For: 2.1.1-beta
>         Attachments: YARN-1157.1.patch
> Submit YARN distributed shell application. Goto ResourceManager Web UI. The application
definitely appears. In Tracking UI column, there will be history link. Click on that link.
Instead of showing application master web UI, HTTP error 500 would appear.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message