Consistency checker wakes up to generate new jobs regardless of available migration jobs.
Migrator retrieves either generated or non-generated jobs, according to weights specified in configuration. Migration and consistency checking can run in parallel and their participation can be controlled.
This is not very clean approach, but at least I didn't need to touch the thread management logic, which I find really complex.
Coverage increased (+0.02%) to 67.703% when pulling a4cacb55cd3b130feabad005996ece7d85080269 on inproportion into c357f47d1072271a67d84f3b7fe0f5a27274bde6 on master.
Coverage decreased (-0.05%) to 67.633% when pulling 2523fa6eb9b11b28ab407c8c1ba44940f136922e on inproportion into c357f47d1072271a67d84f3b7fe0f5a27274bde6 on master.
Coverage decreased (-0.05%) to 67.633% when pulling 417486be7254b43f3b2cbca0870d12c4db2d886d on inproportion into c357f47d1072271a67d84f3b7fe0f5a27274bde6 on master.
2 things changed:
This is not very clean approach, but at least I didn't need to touch the thread management logic, which I find really complex.
TODO: unit test