[
https://issues.apache.org/jira/browse/MAPREDUCE-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153432#comment-16153432
]
Peter Bacsko commented on MAPREDUCE-5124:
-----------------------------------------
Just a question - we already have
https://issues.apache.org/jira/browse/HADOOP-10597. Can't we just enable this
feature inside the MRAppMaster when it creates the RCP server for
TaskUmbilicalProtocol? (I guess that's the message which mappers/reducers
call). Then in {{TaskReporter}} we handle {{RetriableException}} and increase
the heartbeat interval, let's say double it. If it succeeds after a couple of
reports, we can try to decrease it again, back to the original value. This
might not be the best flow control method, but we can think about this.
> AM lacks flow control for task events
> -------------------------------------
>
> Key: MAPREDUCE-5124
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5124
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mr-am
> Affects Versions: 2.0.3-alpha, 0.23.5
> Reporter: Jason Lowe
> Assignee: Haibo Chen
> Attachments: MAPREDUCE-5124-proto.2.txt, MAPREDUCE-5124-prototype.txt
>
>
> The AM does not have any flow control to limit the incoming rate of events
> from tasks. If the AM is unable to keep pace with the rate of incoming
> events for a sufficient period of time then it will eventually exhaust the
> heap and crash. MAPREDUCE-5043 addressed a major bottleneck for event
> processing, but the AM could still get behind if it's starved for CPU and/or
> handling a very large job with tens of thousands of active tasks.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
