Prabhu Joseph created MAPREDUCE-7369:
----------------------------------------
Summary: MapReduce tasks timing out when spends more time on
MultipleOutputs#close
Key: MAPREDUCE-7369
URL: https://issues.apache.org/jira/browse/MAPREDUCE-7369
Project: Hadoop Map/Reduce
Issue Type: Bug
Affects Versions: 3.3.1
Reporter: Prabhu Joseph
Assignee: Prabhu Joseph
MapReduce tasks timing out when spends more time on MultipleOutputs#close.
MultipleOutputs#closes takes more time when there are multiple files to be
closed & there is a high latency in closing a stream.
{code}
2021-11-01 02:45:08,312 INFO [AsyncDispatcher event handler]
org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl: Diagnostics report
from attempt_1634949471086_61268_m_001115_0:
AttemptID:attempt_1634949471086_61268_m_001115_0 Timed out after 300 secs
{code}
MapReduce task timeout can be increased but it is tough to set the right
timeout value. The timeout can be disabled with 0 but that might lead to
hanging tasks not getting killed.
The tasks are sending the ping every 3 seconds which are not honored by
ApplicationMaster. It expects the status information which won't be send during
MultipleOutputs#close. This jira is to add a config which considers the ping
from task as part of Task Liveliness Check in the ApplicationMaster.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
