hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weiwei Yang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4621) Job failed if time on one NM is out of sync even other nodes are sync'd
Date Fri, 22 Jan 2016 06:50:39 GMT

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

Weiwei Yang updated YARN-4621:
------------------------------
    Description: 
RM tried allocated more than 10 containers on a NM (on which time is out of sync), they all
failed with token expired error, and job eventually failed. We can add a new state to NodeState,
e.g DESYNC, if a node is not sync'd with RM, RM then can skip allocating containers on this
node.



  was:
RM tried allocated more than 10 containers on a NM (on which time is out of sync), they all
failed with token expired error, and job eventually failed. We can add a new state to NodeState,
e.g UNSYNC, if a node is not sync'd with RM, RM then can skip allocating containers on this
node.




> Job failed if time on one NM is out of sync even other nodes are sync'd
> -----------------------------------------------------------------------
>
>                 Key: YARN-4621
>                 URL: https://issues.apache.org/jira/browse/YARN-4621
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager, resourcemanager
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>         Attachments: terasort_job_failed.log
>
>
> RM tried allocated more than 10 containers on a NM (on which time is out of sync), they
all failed with token expired error, and job eventually failed. We can add a new state to
NodeState, e.g DESYNC, if a node is not sync'd with RM, RM then can skip allocating containers
on this node.



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

Mime
View raw message