Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000164Rosetta[All Projects] Bad Codingpublic2012-12-12 16:452012-12-12 16:45
Assigned To 
PlatformAll platformsOSAnyOS VersionAny
Product VersionTrunk 
Fixed in Version 
Summary0000164: -ntrials and -max_retry_job option confusion
DescriptionThe options -jd2:ntrials and -run:max_retry_job options appear to be doing almost the same thing, and appear to be doing it simultanteously.

In jd2::JobDistributor::go_main, if you get a FAIL_RETRY status from the mover, you'll terminate execution if you're above ntrials. If not, you'll call mark_current_job_id_for_repetition(), which for FileSystemJobDistributor then looks at max_retry_job, with the same cutoff logic. The upshot is that if you want to increase the number of trials when using the FileSystemJobDistributor, you'd have to set *both* -jd2:ntrials and -run:max_retry_job.

Steps To ReproduceRun an always-fails-with-FAIL_RETRY mover under jd2 and FileSystemJobDistributor with something like -jd2:ntrials 100. Note how you only ever get 10 repeats because of -run:max_retry_job.
Additional InformationThe -run:max_retry_job logic seems to have been added with a note about proper restart behavior on Boinc. [^]
It looks like this was before the -jd2:ntrials logic was added to JobDistributor.
TagsNo tags attached.
Application(s) Affectedany jd2
Command Line Usedany jd2 with FileSystemJobDistributor and -jd2:ntrials > 10
Developer OptionsConfirmed As Bug
Fixed in SVN Version
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2012-12-12 16:45 rmoretti New Issue

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker