Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 3 Oct 2013 17:15:45 +0000 (UTC)
From: "Alejandro Abdelnur (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12654046.1371772481006.7997.1380820545692@arcas>
In-Reply-To: <JIRA.12654046.1371772481006@arcas>
References: <JIRA.12654046.1371772481006@arcas>
Subject: [jira] [Commented] (YARN-867) Isolation of failures in aux services
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/YARN-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785364#comment-13785364 ] 

Alejandro Abdelnur commented on YARN-867:
-----------------------------------------

the try/catch should be around each aux service method invocation so a failure of a given service does not affect delivery to other services.

> Isolation of failures in aux services 
> --------------------------------------
>
>                 Key: YARN-867
>                 URL: https://issues.apache.org/jira/browse/YARN-867
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>            Reporter: Hitesh Shah
>            Assignee: Xuan Gong
>            Priority: Critical
>         Attachments: YARN-867.1.sampleCode.patch, YARN-867.3.patch, YARN-867.4.patch, YARN-867.5.patch, YARN-867.6.patch, YARN-867.sampleCode.2.patch
>
>
> Today, a malicious application can bring down the NM by sending bad data to a service. For example, sending data to the ShuffleService such that it results any non-IOException will cause the NM's async dispatcher to exit as the service's INIT APP event is not handled properly. 


--
This message was sent by Atlassian JIRA
(v6.1#6144)