In coordinator/workers setup one can create workers manually. However, it is more convenient to have them created automatically, according to some definition. The
WorkersCreationTaskHandler does just that. Here's a short description how to configure it.
workManagement section defines here two important things:
- Segmentation of work into buckets:
- We create 20 buckets, each having 50 items. (So the first one is 0..49, then 50..99, 100..149, up to 950..999.)
- What workers are used to process the work:
- There will be four workers on each cluster node.
- Each worker will execute NoOpTaskHandler. (It does nothing in particular; just iterates through fictitious objects.)
Here we describe
workers configuration section. (The
buckets section is explained elsewhere.)
How to derive names for worker tasks. It is possible to use substitution strings of
|handlerUri||Worker tasks handler URI.||Might be known from the context; otherwise there is no default and the URI has to be specified.|
|otherDeltas||Other deltas to be applied to newly created worker task.||-|
|workersPerNode||Configuration of how many and what workers to be created for given cluster node(s).||Single worker per node.|
Workers per node are configured using the following items:
Node identifier(s) for which we are going to generate the tasks.
|All nodes currently defined in the repository.|
|count||How many workers to create for given node(s).||1|
How to derive names for the tasks.
|taskName defined in the parent element|
|executionGroup||Execution group for created workers. It is possible to use substitution strings here.|
|otherDeltas||Other deltas to be applied to newly created worker task in this group. Applied in addition to the deltas defined in parent element.||-|