Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 1 Jun 2017 14:20:04 +0000 (UTC)
From: "Kihwal Lee (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13001371.1472572219000.341753.1496326804812@Atlassian.JIRA>
In-Reply-To: <JIRA.13001371.1472572219000@Atlassian.JIRA>
References: <JIRA.13001371.1472572219000@Atlassian.JIRA> <JIRA.13001371.1472572219583@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HDFS-10816)
 TestComputeInvalidateWork#testDatanodeReRegistration fails due to race
 between test and replication monitor
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 01 Jun 2017 14:20:10 -0000


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

Kihwal Lee commented on HDFS-10816:
-----------------------------------

+1

> TestComputeInvalidateWork#testDatanodeReRegistration fails due to race between test and replication monitor
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-10816
>                 URL: https://issues.apache.org/jira/browse/HDFS-10816
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Eric Badger
>            Assignee: Eric Badger
>         Attachments: HDFS-10816.001.patch
>
>
> {noformat}
> java.lang.AssertionError: Expected invalidate blocks to be the number of DNs expected:<3> but was:<2>
> 	at org.junit.Assert.fail(Assert.java:88)
> 	at org.junit.Assert.failNotEquals(Assert.java:743)
> 	at org.junit.Assert.assertEquals(Assert.java:118)
> 	at org.junit.Assert.assertEquals(Assert.java:555)
> 	at org.apache.hadoop.hdfs.server.blockmanagement.TestComputeInvalidateWork.testDatanodeReRegistration(TestComputeInvalidateWork.java:160)
> {noformat}
> The test fails because of a race condition between the test and the replication monitor. The default replication monitor interval is 3 seconds, which is just about how long the test normally takes to run. The test deletes a file and then subsequently gets the namesystem writelock. However, if the replication monitor fires in between those two instructions, the test will fail as it will itself invalidate one of the blocks. This can be easily reproduced by removing the sleep() in the ReplicationMonitor's run() method in BlockManager.java, so that the replication monitor executes as quickly as possible and exacerbates the race. 
> To fix the test all that needs to be done is to turn off the replication monitor. 


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org