Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.7.0
Description
Per my understanding, it was due to:
commit 3b173d95171d01ab55042b1162569d1cf14a8d43
Author: Colin Patrick Mccabe <cmccabe@cloudera.com>
Date: Wed Dec 17 16:41:59 2014 -0800
HDFS-7531. Improve the concurrent access on FsVolumeList (Lei Xu via Colin P. McCabe)
- volatile List<FsVolumeImpl> volumes = null;
+ private final AtomicReference<FsVolumeImpl[]> volumes =
+ new AtomicReference<>(new FsVolumeImpl[0]);
so the old case will complain at here:
assertTrue("The DN should have started with this directory",
si.contains(dataDir1Actual.getPath()));
Attachments
Attachments
Issue Links
- duplicates
-
HDFS-7547 Fix TestDataNodeVolumeFailureToleration#testValidVolumesAtStartup
- Closed