[ https://issues.apache.org/jira/browse/MAPREDUCE-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160448#comment-13160448
]
Siddharth Seth commented on MAPREDUCE-3460:
-------------------------------------------
New container requests ignore node blacklisting - and make an entry into {{mapsHostMapping}}.
That would be one way to recreate this issue (or alternately fix it).
Something like
1. request _1 on h1
2. am heartbeat
3. h1 heartbeat
4. am heartbeat - container assigned
5. fail _1 on h1
6. request fast_fail replacement for _1
7. am heartbeat - to update request
8. request _3 on h3 / h1,h3
9. h1 heartbeat - to schedule (RM only aware fast_fail _1 at this point)
10. am heartbeat - to get a fast_fail allocated on a blacklisted node.
11. h1 heartbeat
12. h3 heartbeat
> MR AM can hang if containers are allocated on a node blacklisted by the AM
> --------------------------------------------------------------------------
>
> Key: MAPREDUCE-3460
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3460
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mr-am, mrv2
> Affects Versions: 0.23.0, 0.24.0
> Reporter: Siddharth Seth
> Assignee: Robert Joseph Evans
> Priority: Blocker
> Attachments: MR-3460.txt, MR-3460.txt
>
>
> When an AM is assigned a FAILED_MAP (priority = 5) container on a nodemanager which it
has blacklisted - it tries to
> find a corresponding container request.
> This uses the hostname to find the matching container request - and can end up returning
any of the ContainerRequests which may have requested a container on this node. This container
request is cleaned to remove the bad node - and then added back to the RM 'ask' list.
> The AM cleans the 'ask' list after each heartbeat - The RM Allocator is still aware of
the priority=5 container (in 'remoteRequestsTable') - but this never gets added back to the
'ask' set - which is what is sent to the RM.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
|