[
https://issues.apache.org/jira/browse/HDFS-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger updated HDFS-11094:
-------------------------------
Attachment: HDFS-11094.001.patch
The problem is that the MiniDFSCluster doesn't wait for the DN(s) to heartbeat
before it declares itself as "active" or "up". Since the DNs haven't
heartbeated in yet, if the test asks the DN for the active NN it will return
null. This will then cause the test to fail.
So I am proposing that we wait for the DN(s) to hearbeat into the NN before
allowing the cluster to return from its {{build()}} method. This may also have
a performance boost since it will cause the DNs to be proactive in talking to
the namenode instead of waiting and doing it on a timer.
> TestLargeBlockReport fails intermittently
> -----------------------------------------
>
> Key: HDFS-11094
> URL: https://issues.apache.org/jira/browse/HDFS-11094
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Eric Badger
> Assignee: Eric Badger
> Attachments: HDFS-11094.001.patch
>
>
> {noformat}
> java.lang.NullPointerException: null
> at
> org.apache.hadoop.hdfs.server.datanode.TestLargeBlockReport.testBlockReportSucceedsWithLargerLengthLimit(TestLargeBlockReport.java:96)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
