Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-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 C237811AB7 for ; Fri, 15 Aug 2014 01:31:19 +0000 (UTC) Received: (qmail 7474 invoked by uid 500); 15 Aug 2014 01:31:19 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 7418 invoked by uid 500); 15 Aug 2014 01:31:19 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 7405 invoked by uid 99); 15 Aug 2014 01:31:19 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Aug 2014 01:31:19 +0000 Date: Fri, 15 Aug 2014 01:31:19 +0000 (UTC) From: "James Thomas (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-6853) MiniDFSCluster.isClusterUp() should not check if null NameNodes are up 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/HDFS-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098034#comment-14098034 ] James Thomas commented on HDFS-6853: ------------------------------------ Looks like a few tests rely on this behavior ... will hold off on this for now. > MiniDFSCluster.isClusterUp() should not check if null NameNodes are up > ---------------------------------------------------------------------- > > Key: HDFS-6853 > URL: https://issues.apache.org/jira/browse/HDFS-6853 > Project: Hadoop HDFS > Issue Type: Bug > Reporter: James Thomas > Assignee: James Thomas > Attachments: HDFS-6853.patch > > > Suppose we have a two-NN cluster and then shut down one of the NN's (NN0). When we try to restart the other NN (NN1), we wait for isClusterUp() to return true, but this will never happen because NN0 is null and isNameNodeUp returns false for a null NN. -- This message was sent by Atlassian JIRA (v6.2#6252)