[AVRO-1215] AvroMultipleOutputs not working when specifying baseOutputPath

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.2
• Fix Version/s: 1.7.4
• Component/s: java
• Labels: avro mapreduce
• Tags: avro
• Assignee: Ashish Nagavaram
• Reporter: Matthew Hayes
• Created: 07/Dec/12 04:44
• Updated: 20/Aug/15 19:10
• Resolved: 18/Feb/13 18:31

Description

I'm calling the write() method of AvroMultipleOutputs which takes the baseOutputPath. The reducer appears to begin hanging once it tries writing to a baseOuputPath value not already encountered. It then fails with:

org.apache.hadoop.ipc.RemoteException: org.apache.hadoop.hdfs.protocol.AlreadyBeingCreatedException: failed to create file ... because current leaseholder is trying to recreate file.

I think the problem has to do with this line in AvroMultipleOutputs:

// get the record writer from context output format
//FileOutputFormat.setOutputName(taskContext, baseFileName);

This line is not commented out in the similar code from Hadoop. So I think the baseOutputPath is ignored. As a result when each record writer is created it uses the same path, leading to the exception.

Uncommenting this line does not work because of visibility of the method. However what this method does is set "mapreduce.output.basename". But setting this doesn't work either.

After digging through Avro code I found that AvroOutputFormatBase is using "avro.mo.config.namedOutput" to create the path. If I replace the commented out line with this it seems to work:

taskContext.getConfiguration().set("avro.mo.config.namedOutput", baseFileName);  

Issue Links

• duplicates: AVRO-1236 AvroMultipleOutputs fails to close successfuly
• duplicates: AVRO-1179 AvroMultipleOutputs does not seem to be generating different base output paths
• is duplicated by: AVRO-1239 AvroMultipleOutput ignores schemas
• is related to: AVRO-1106 AvroMultipleOutputs for new Hadoop Version
• relates to: AVRO-1266 Fix mapred AvroMultipleOutputs class to write the schema to Jobconf rather than private Hashmap