Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # user >> What is the best to terminate a Map job without it being retried


Copy link to this message
-
Re: What is the best to terminate a Map job without it being retried
How about deleting/moving the dirty files in your mapper or in another job ?

On Fri, Oct 8, 2010 at 4:30 PM, Steve Kuo <[EMAIL PROTECTED]> wrote:

> I have a collection of dirty data files, which I can detect during the
> setup() phase of my Map job.  It would be best that I can quit the map job
> and prevent it from being retried again.  What is the best practice to do
> this?
>
> Thanks in advance.
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB