big-data/hadoop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

HDFS-7355. TestDataNodeVolumeFailure#testUnderReplicationAfterVolFailure fails on Windows, because we cannot deny access to the file owner. Contributed by Chris Nauroth.

Browse Source
This commit is contained in:
Haohui Mai 2014-11-04 15:18:51 -08:00
parent 2e1d9a4127
commit 99d710348a
2 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
View File

@ -1003,6 +1003,10 @@ Release 2.6.0 - UNRELEASED
HDFS-7334. Fix periodic failures of TestCheckpoint HDFS-7334. Fix periodic failures of TestCheckpoint
#testTooManyEditReplayFailures. (Charles Lamb via wheat9) #testTooManyEditReplayFailures. (Charles Lamb via wheat9)
HDFS-7355. TestDataNodeVolumeFailure#testUnderReplicationAfterVolFailure
fails on Windows, because we cannot deny access to the file owner.
(Chris Nauroth via wheat9)
BREAKDOWN OF HDFS-6134 AND HADOOP-10150 SUBTASKS AND RELATED JIRAS BREAKDOWN OF HDFS-6134 AND HADOOP-10150 SUBTASKS AND RELATED JIRAS
HDFS-6387. HDFS CLI admin tool for creating & deleting an HDFS-6387. HDFS CLI admin tool for creating & deleting an

5
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestDataNodeVolumeFailure.java
View File

@ -205,6 +205,11 @@ public void testVolumeFailure() throws Exception {
*/ */
@Test @Test
public void testUnderReplicationAfterVolFailure() throws Exception { public void testUnderReplicationAfterVolFailure() throws Exception {
// This test relies on denying access to data volumes to simulate data volume
// failure. This doesn't work on Windows, because an owner of an object
// always has the ability to read and change permissions on the object.
assumeTrue(!Path.WINDOWS);
// Bring up one more datanode // Bring up one more datanode
cluster.startDataNodes(conf, 1, true, null, null); cluster.startDataNodes(conf, 1, true, null, null);
cluster.waitActive(); cluster.waitActive();