From 99d710348a20ff99044207df4b92ab3bff31bd69 Mon Sep 17 00:00:00 2001 From: Haohui Mai Date: Tue, 4 Nov 2014 15:18:51 -0800 Subject: [PATCH] HDFS-7355. TestDataNodeVolumeFailure#testUnderReplicationAfterVolFailure fails on Windows, because we cannot deny access to the file owner. Contributed by Chris Nauroth. --- hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt | 4 ++++ .../hdfs/server/datanode/TestDataNodeVolumeFailure.java | 5 +++++ 2 files changed, 9 insertions(+) diff --git a/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt b/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt index b4e0fa1ee6..c896ead731 100644 --- a/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt +++ b/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt @@ -1003,6 +1003,10 @@ Release 2.6.0 - UNRELEASED HDFS-7334. Fix periodic failures of TestCheckpoint #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 HDFS-6387. HDFS CLI admin tool for creating & deleting an diff --git a/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestDataNodeVolumeFailure.java b/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestDataNodeVolumeFailure.java index 8429055a20..6b9c4b18de 100644 --- a/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestDataNodeVolumeFailure.java +++ b/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestDataNodeVolumeFailure.java @@ -205,6 +205,11 @@ public void testVolumeFailure() throws Exception { */ @Test 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 cluster.startDataNodes(conf, 1, true, null, null); cluster.waitActive();