[
https://issues.apache.org/jira/browse/HDFS-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang updated HDFS-3811:
------------------------------
Attachment: testfail.log
I reproduced this locally by running 6 cpuburn threads concurrently with the
test, log attached.
It seems that we're getting client NPEs when the NN is being restarted. There's
also an error at the end, where the DFSClient thinks the file is still being
written even though it's already been closed.
Both of these involve the BlocksMap, so I suspect we're missing some
synchronization.
> TestPersistBlocks#TestRestartDfsWithFlush appears to be flaky
> -------------------------------------------------------------
>
> Key: HDFS-3811
> URL: https://issues.apache.org/jira/browse/HDFS-3811
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.2.0-alpha
> Reporter: Andrew Wang
> Attachments: testfail.log
>
>
> This test failed on a recent Jenkins build, but passes for me locally. Seems
> flaky.
> See:
> https://builds.apache.org/job/PreCommit-HDFS-Build/3021//testReport/org.apache.hadoop.hdfs/TestPersistBlocks/TestRestartDfsWithFlush/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
