Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 384AC101A9 for ; Fri, 13 Feb 2015 05:49:13 +0000 (UTC) Received: (qmail 40432 invoked by uid 500); 13 Feb 2015 05:49:13 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 40377 invoked by uid 500); 13 Feb 2015 05:49:13 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 40365 invoked by uid 99); 13 Feb 2015 05:49:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Feb 2015 05:49:13 +0000 Date: Fri, 13 Feb 2015 05:49:12 +0000 (UTC) From: "Hadoop QA (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3025) Provide API for retrieving blacklisted nodes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319631#comment-14319631 ] Hadoop QA commented on YARN-3025: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12698631/yarn-3025-v1.txt against trunk revision b0d81e0. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 core tests{color}. The patch failed these unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client: org.apache.hadoop.yarn.client.TestApplicationMasterServiceProtocolOnHA The following test timeouts occurred in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client: org.apache.hadoop.yarn.client.TestRMFailover Test results: https://builds.apache.org/job/PreCommit-YARN-Build/6630//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6630//console This message is automatically generated. > Provide API for retrieving blacklisted nodes > -------------------------------------------- > > Key: YARN-3025 > URL: https://issues.apache.org/jira/browse/YARN-3025 > Project: Hadoop YARN > Issue Type: Improvement > Reporter: Ted Yu > Assignee: Ted Yu > Attachments: yarn-3025-v1.txt > > > We have the following method which updates blacklist: > {code} > public synchronized void updateBlacklist(List blacklistAdditions, > List blacklistRemovals) { > {code} > Upon AM failover, there should be an API which returns the blacklisted nodes so that the new AM can make consistent decisions. > The new API can be: > {code} > public synchronized List getBlacklistedNodes() > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)