No longer hard-coding HDFS replication factor.

HDFS replication factor was set equal to Voldemort replication factor. This doesn't bring benefit (you can't ensure the HDFS fetcher jobs use distinct data nodes), could cause potential issues, can be done done without hard-coding (by setting it as a parameter when running the M/R job).
baepiff · Mar 22, 2010 · 368f2c4 · 368f2c4
1 parent d96839b
commit 368f2c4
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/.../hadoop-store-builder/src/java/voldemort/store/readonly/mr/HadoopStoreBuilderReducer.java b/.../hadoop-store-builder/src/java/voldemort/store/readonly/mr/HadoopStoreBuilderReducer.java
@@ -120,8 +120,8 @@ public void configure(JobConf job) {
             logger.info("Opening " + this.taskIndexFileName + " and " + this.taskValueFileName
                         + " for writing.");
             FileSystem fs = this.taskIndexFileName.getFileSystem(job);
-            this.indexFileStream = fs.create(this.taskIndexFileName, (short) replicationFactor);
-            this.valueFileStream = fs.create(this.taskValueFileName, (short) replicationFactor);
+            this.indexFileStream = fs.create(this.taskIndexFileName);
+            this.valueFileStream = fs.create(this.taskValueFileName);
         } catch(IOException e) {
             throw new RuntimeException("Failed to open Input/OutputStream", e);
         }