hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sandflee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3668) Long run service shouldn't be killed even if Yarn crashed
Date Wed, 27 May 2015 07:18:17 GMT

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

sandflee commented on YARN-3668:

when the AM restarts its JARs are re-downloaded from HDFS. If you update the JAR before the
restart, the new version is picked up. This is how we actually implement zero-downtime upgrades
of slider-managed clusters.
seems you're using DistributedCache, one problem:
1,am launched at Node1,and am jars are distributed to Node1 too
2,am jars updated and restart am
3,am are assigned to Node1 again, so am are using old jars, not the updated one

could you share how to solve this problem?

> Long run service shouldn't be killed even if Yarn crashed
> ---------------------------------------------------------
>                 Key: YARN-3668
>                 URL: https://issues.apache.org/jira/browse/YARN-3668
>             Project: Hadoop YARN
>          Issue Type: Wish
>            Reporter: sandflee
> For long running service, it shouldn't be killed even if all yarn component crashed,
with RM work preserving and NM restart, yarn could take over applications again.

This message was sent by Atlassian JIRA

View raw message