Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 21 Jul 2014 21:30:40 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12416186.1236234965916.13639.1405978240829@arcas>
In-Reply-To: <JIRA.12416186.1236234965916@arcas>
References: <JIRA.12416186.1236234965916@arcas>
Subject: =?utf-8?Q?[jira]_[Resolved]_(MAPREDUCE-175)_Sometim?=
 =?utf-8?Q?es,_Reduce_tasks_hang=EF=BC=8C_State_is_unassigned?=
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/MAPREDUCE-175?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved MAPREDUCE-175.
----------------------------------------

    Resolution: Incomplete

Closing this as either stale or already fixed or whatever.

> Sometimes, Reduce tasks hang=EF=BC=8C State is unassigned
> -------------------------------------------------
>
>                 Key: MAPREDUCE-175
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-175
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: ZhuGuanyin
>
> Hi, all
> When our cluster runs for a long time, some reduce tasks running on some =
tasktrackers hang. Their states are UNASSIGNED.  Then, all reduce tasks on =
these tasktracker will hang.
> We kill the hang reduce task, then the reduce task attempt is re-schedule=
d to this tasktracker, the attempt task continues to hang. We fail it, it g=
oes to another tasktracker, it is executed successfully.=20
> Tasktracker which has hang reduce task will receive new reduce task, but =
the reduce  task continue to hang for ever.
> When we reboot the tasktracker machine, reduce task no longer hangs.


--
This message was sent by Atlassian JIRA
(v6.2#6252)