DUCC does not have an automatic resubmit capability. Usually a high error count is indicative of a flawed job, and the default DUCC plug-in error handler cancels the job after 15 errors have occurred so as to not waste resources. Normally, one debugs the pipeline before scaling-out and the number of errors should be zero. This error limit can be raised. Information on the plug-in error handler is available in the DUCC documentation.
You can also change the timeout value at job submit time by using: --process_per_item_time_max <integer> Maximum elapsed time (in minutes) for processing one CAS. Lou. On Tue, Jun 3, 2014 at 8:59 AM, reshu.agarwal <[email protected]> wrote: > > Hi, > > I faces some times the "CanceledByDriver" status to a job in DUCC, If > error count reaches to 14. The all errors are due to Cas Timed Out > exception and after 5 continuous errors the Cas timed out on server is > null. Whole Job is cancelled and documents get skipped by this. > > Can I set some configuration in DUCC to reprocess this particular job > again as new job if job is cancelled by driver? > > > -- > Thanks, > Reshu Agarwal > >
