[
https://issues.apache.org/jira/browse/HDFS-5983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee updated HDFS-5983:
-----------------------------
Attachment: testlog.txt
Attaching the log from the precommit build. NN starts with 0 block, then
initializes the repl queue, then 3 blocks are reported by the datanode.
The test makes assumption that by the time it acquires and releases the
namesystem write lock, block report is processed completely and repl queues are
initialized. This is not true.
> TestSafeMode#testInitializeReplQueuesEarly fails
> ------------------------------------------------
>
> Key: HDFS-5983
> URL: https://issues.apache.org/jira/browse/HDFS-5983
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Kihwal Lee
> Attachments: 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.1.5#6160)
