Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Wed, 9 Apr 2014 19:30:19 +0000 (UTC)
From: "Arpit Agarwal (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12696260.1392908210623.88228.1397071819721@arcas>
In-Reply-To: <JIRA.12696260.1392908210623@arcas>
References: <JIRA.12696260.1392908210623@arcas>
Subject: [jira] [Resolved] (HDFS-5983)
 TestSafeMode#testInitializeReplQueuesEarly fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arpit Agarwal resolved HDFS-5983.
---------------------------------

    Resolution: Duplicate

Resolving since this should be fixed now.

> TestSafeMode#testInitializeReplQueuesEarly fails
> ------------------------------------------------
>
>                 Key: HDFS-5983
>                 URL: https://issues.apache.org/jira/browse/HDFS-5983
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>            Reporter: Kihwal Lee
>            Assignee: Ming Ma
>         Attachments: HDFS-5983-updated.patch, HDFS-5983.patch, testlog.txt
>
>
> It was seen from one of the precommit build of HDFS-5962.  The test case creates 15 blocks and then shuts down all datanodes. Then the namenode is restarted with a low safe block threshold and one datanode is restarted. The idea is that the initial block report from the restarted datanode will make the namenode leave the safemode and initialize the replication queues.
> According to the log, the datanode reported 3 blocks, but slightly before that the namenode did repl queue init with 1 block.  I will attach the log.


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