Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
With SLING-2979 support for running singleton jobs on specific instance was provided. In most cases we want to run a job as singleton and not want to "pin" it to specific nodes. For this scheduler.runOn needs to be set to SINGLE.
However per current implementation SINGLE is treated as LEADER. This effectively causes all singleton jobs to get executed on leader only thus putting extra load.
For better utilization of cluster resources it should be possible to distribute such singleton jobs on other cluster nodes and still ensure that singleton contract is honoured!
We would like to make use of this feature to ensure Oak AsyncIndexTask to run on different cluster nodes (OAK-2749)
Attachments
Issue Links
- is related to
-
SLING-7037 Scheduler does not retain provided name
- Closed
-
OAK-6605 Provide job name for async index update
- Closed
- relates to
-
SLING-2979 Add support for running scheduled task on specific instances
- Closed
-
OAK-1246 Make AsynchIndexUpdate task to run only on a single node in a cluster
- Closed
-
OAK-2749 Provide a "different lane" for slow indexers in async indexing
- Closed