[
https://issues.apache.org/jira/browse/HDFS-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284651#comment-14284651
]
Konstantin Shvachko commented on HDFS-7611:
-------------------------------------------
Was looking at {{TestOpenFilesWithSnapshot}} which also restarts NameNode and
fails intermittently with the same timeout. I see similar behavior as Byron
described.
The test creates two files {{/test/test/test2}} and {{/test/test/test3}}, then
aborts the streams, creates a snapshot, deletes the files, and restarts the the
NameNode. If any of the replicas of the files were created on any of DNs, then
the test succeeds. If the stream is aborted before the replicas are created,
then the test fails.
So some blocks, which were deleted before the NN restart are not being garbage
collected on restart, and NN cannot get out of safe mode then.
This test does not use truncate, but does use snapshots.
> TestFileTruncate.testTruncateEditLogLoad times out waiting for Mini HDFS
> Cluster to start
> -----------------------------------------------------------------------------------------
>
> Key: HDFS-7611
> URL: https://issues.apache.org/jira/browse/HDFS-7611
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Konstantin Shvachko
> Assignee: Byron Wong
> Attachments: testTruncateEditLogLoad.log
>
>
> I've seen it failing on Jenkins a couple of times. Somehow the cluster is not
> comming ready after NN restart.
> Not sure if it is truncate specific, as I've seen same behaviour with other
> tests that restart the NameNode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
