Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 2 Feb 2012 01:19:53 +0000 (UTC)
From: "Siddharth Seth (Updated) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1470550004.854.1328145593420.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <471314898.15697.1325875299262.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (MAPREDUCE-3634) All daemons should crash instead
 of hanging around when their EventHandlers get exceptions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MAPREDUCE-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Siddharth Seth updated MAPREDUCE-3634:
--------------------------------------

    Status: Open  (was: Patch Available)

Other than Sharad's change request, 1 change required to AsyncDispatcher.
{{eventQueue.put(event);}} used to throw an Exception in case of interruption. That exception should be added back.
                
> All daemons should crash instead of hanging around when their EventHandlers get exceptions
> ------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3634
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3634
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>             Fix For: 0.23.1
>
>         Attachments: MAPREDUCE-3634-20120118.1.txt, MAPREDUCE-3634-20120119.txt
>
>
> We should make sure that the daemons crash in case the dispatchers get exceptions and stop processing. That way we will be debugging RM/NM/AM crashes instead of hard-to-track hanging jobs. 

--
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