I’m chipping away at a Hadoop group with CDH4.2.0 introduced and kept running into this blunder. It’s been settled in later forms of Hadoop yet I don’t approach refresh the group. Is there an approach to advise Hadoop to utilize this container when running my activity through the charge line contentions like
hadoop jostle MyJob.jar - D hadoop.mapreduce.client=hadoop-mapreduce-customer center 2.0.0-cdh4.2.0.jar
where the new MapReduce-customer core.jar record is the fixed jug from the ticket. Or then again should Hadoop be totally recompiled with this new jug? I’m new to Hadoop so I don’t have the foggiest idea about all the summon line alternatives that are conceivable.