[
https://issues.apache.org/jira/browse/MAPREDUCE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730539#action_12730539
]
Milind Bhandarkar commented on MAPREDUCE-257:
---------------------------------------------
I have seen this in one of our production clusters. The java task itself is
killed due to memory limits, but there is a runaway task consuming lost of
memory. So, I think killing the entire process tree did not work.
> Preventing node from swapping
> -----------------------------
>
> Key: MAPREDUCE-257
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-257
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Hong Tang
>
> When a node swaps, it slows everything: maps running on that node, reducers
> fetching output from the node, and DFS clients reading from the DN. We should
> just treat it the same way as if OS exhausts memory and kill some tasks to
> free up memory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
