...
- When the HarvestJobManager is restarted, all queue jobs are resubmitted which will cause dublicate processing of the HarvestJobs
- Modifing HarvestDefinitions will not have an effect on queue jobs.
Test specification
Create 4 selektive harvest jobs
Create selective harvest and add domain for | agilos.org |
Create selective harvest and add domain for | mikis.dk |
Create selective harvest and add domain for | agilis-software.dk |
Create selective harvest | kb.dk |
Activate all harvests Verify jobs exist |
Because only 2 selective harvesters (high-priority) are available, only 2 of the jobs should be started initially. one of the remaining jobs should be queued, and the last one should remain in state 'New' until a harvest finishs and the queue job is
Verify jobs are created | 1,2,3,4 |
Verify number of jobs started are | 2 |
Verify number of jobs submitted are | 1 |
Verify number of jobs new are | 1 |
Wait for the first job is done (with 5 minuts timeout)
Wait for next done job | 300 |
Verify number of jobs started are | 2 |
Verify number of jobs submitted are | 1 |
Verify number of jobs new are | 0 |