hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4682) AMRM client to log when AMRM token updated
Date Wed, 10 Feb 2016 17:54:18 GMT

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

Steve Loughran commented on YARN-4682:

to get a patch we can put into Hadoop, yes, you need to check out trunk or branch-2; that's
where all patches go in, with some being cherry-picked earlier.

Moving off hadoop 2.4 to 2.6.1 should fix your problem, but having a log entry should  help

how to decrease the expiry time? that should be the key. Looking at the code, it needs to
be at least 3 times the value of {{yarn.am.liveness-monitor.expiry-interval-ms}}. Make that
nice and short

> AMRM client to log when AMRM token updated
> ------------------------------------------
>                 Key: YARN-4682
>                 URL: https://issues.apache.org/jira/browse/YARN-4682
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 2.7.2
>            Reporter: Steve Loughran
>         Attachments: YARN-4682.patch
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
> There's no information right now as to when the AMRM token gets updated; if something
has gone wrong with the update, you can't tell when it last when through.
> fix: add a log statement.

This message was sent by Atlassian JIRA

View raw message