hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4214) AppAttemptInfo should have ApplicationAttemptId
Date Wed, 30 Sep 2015 23:16:04 GMT

     [ https://issues.apache.org/jira/browse/YARN-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Wangda Tan updated YARN-4214:
-----------------------------
    Attachment: YARN-4214.1.patch

Attached ver.1 patch, it's a simple fix.

> AppAttemptInfo should have ApplicationAttemptId
> -----------------------------------------------
>
>                 Key: YARN-4214
>                 URL: https://issues.apache.org/jira/browse/YARN-4214
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>         Attachments: YARN-4214.1.patch
>
>
> Currently YARN RM REST API {{ws/v1/cluster/apps/application_1443559871354_0008/appattempts}}
only returns int id for each attempts. 
> Such as:
> {code}
>     "appAttempt": [
>       {
>         "id": "1",
>         "startTime": "1443645213960",
>         "containerId": "container_1443559871354_0008_01_000001",
>         "nodeHttpAddress": "localhost:8042",
>         "nodeId": "localhost:62978",
>         "logsLink": "
> http://localhost:8042/node/containerlogs/container_1443559871354_0008_01_000001/wtan
> "
>       },
> {code}
> It's better to have a string ApplicationAttemptId like: {{appattempt_1443649107010_0001_000001}}
in REST API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message