Hi, We have a map/reduce task that insert to hbase (in the reduce phase). Our problem is that some reduce jobs finish early and then the framework use them in-order to "backup" running reducers (As it should do). This causes to multiple redundant writes to hbase (which is costly). These reducers are eventually killed since the original reducers finish their job.
Can we configure our job to start the "backup" reducer only in case a failure actually occurs (we don't want to compromise robustness) ? Thanks, Lior
