Improve the Error Handler making the jobs resubission more smart about crab2 HOT 7 CLOSED

Comment by fanzago on Tue Mar 18 06:49:10 2008

in order to report the wrapperExitCode and the exeExitCode,
I have to add a new script to send in inputSandbox, to create if necessary and modify the FJR to include these info.

from crab2.

Comment by fanzago on Fri Mar 28 05:31:37 2008

Preparing the script to parse the FJR returned by job, in order to updat the BossDB with ExeExitCode and WrapperExitCode

from crab2.

Closed by fanzago on Wed May 21 10:32:16 2008

from crab2.

Comment by spiga on Wed May 21 15:54:31 2008

I would say that this is another task that cannot be closed yet...

1. The submissionError plugin has not been implemented...

Here the aim is to have a plugin which is able to handle the submission failure.. making the actual mechanism a little bit more smart. At the moment we just rely on a 3-4 next submissions...and then if the submission don't appear we just declare the jobs not submitted... of course it's not enough.

2. in addition, we should also discuss how to extrapolate the failure reason and where put the related info once the jobs is declared as finished.. this is needed for both running and submission error...One possible approach is to ask to TT to take care of that..

3. Finally one of the most important point is to start to think about a queue of jobs to resubmit since we must go to a bulk resubmission (where possible). The right place to do that could be the the EH itself..or maybe the CrabServerWorker..

Daniele

from crab2.

Open by spiga on Wed May 21 15:54:31 2008

from crab2.

Comment by belforte on Thu Jul 11 05:22:34 2013

close old task from old Crab2 era. Will use this tracker for Crab2 support/operation tasks.

from crab2.

Closed by belforte on Thu Jul 11 05:22:58 2013

from crab2.