hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1685) Bugs around log URL
Date Fri, 14 Mar 2014 06:26:43 GMT

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

Zhijie Shen commented on YARN-1685:

Vinod, good suggestion. We can make use of the existing info to construct a log url string
when rendering it. However, there's one issue. Based on current stored container information,
we're unable to know whether the container has been launched before or not. If the container
was not launched, we should not show the log url. Anyway, I agree not storing log url is a
right way. How about we go back to fix the container not launched case separately, by enhancing
the container exit status, state or something to indicate what happened to a container before?

> Bugs around log URL
> -------------------
>                 Key: YARN-1685
>                 URL: https://issues.apache.org/jira/browse/YARN-1685
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Mayank Bansal
>            Assignee: Zhijie Shen
>         Attachments: YARN-1685-1.patch, YARN-1685.2.patch, YARN-1685.3.patch, YARN-1685.4.patch,
> 1. Log URL should be different when the container is running and finished
> 2. Null case needs to be handled
> 3. The way of constructing log URL should be corrected

This message was sent by Atlassian JIRA

View raw message