[ https://issues.apache.org/jira/browse/YARN-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143262#comment-16143262 ]
Junping Du commented on YARN-6091: ---------------------------------- bq. This will end up having stderr print to stderr of the NM, but I think that is better than silently swallowing stderr altogether. This also has side effect - you have to find in NM stderr to get error/debug message that belongs to container/AM. [~suma.shivaprasad] is doing some enhancement in this area. Suma, any comments here? > the AppMaster register failed when use Docker on LinuxContainer > ---------------------------------------------------------------- > > Key: YARN-6091 > URL: https://issues.apache.org/jira/browse/YARN-6091 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager, yarn > Affects Versions: 2.8.1 > Environment: CentOS > Reporter: zhengchenyu > Assignee: Eric Badger > Priority: Critical > Attachments: YARN-6091.001.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > In some servers, When I use Docker on LinuxContainer, I found the aciton that > AppMaster register to Resourcemanager failed. But didn't happen in other > servers. > I found the pclose (in container-executor.c) return different value in > different server, even though the process which is launched by popen is > running normally. Some server return 0, and others return 13. > Because yarn regard the application as failed application when pclose return > nonzero, and yarn will remove the AMRMToken, then the AppMaster register > failed because Resourcemanager have removed this applicaiton's token. > In container-executor.c, the judgement condition is whether the return code > is zero. But man the pclose, the document tells that "pclose return -1" > represent wrong. So I change the judgement condition, then slove this > problem. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org