...
Function | Effect |
|---|---|
No | Can read the batches created by this user |
| Can read all the batches from the index of the organisation of this user |
| Can read all batches from all indices |
PATCH batches/ 24.3+
Following functions are needed to partially update a batch:
Function | When needed? |
|---|---|
| Own batches |
| Batches from the same organisation |
| Batches from other organisations |
DELETE batches/ 24.3+
For cancelling a batch you need the same functions as for PATCH.
Cleanup 24.2+
Completed batches are cleaned up 30 days after their finish date.
...
Normally, a batch is executed on the index of the organization to which the user belongs. When a batch is started by the zeticon@installation or system@installation user, it will be executed across all indices available on the system.
...
Heavy batches 24.3+
A batch can be cancelled To prevent heavy batches from clogging the system, following actions can be taken:
Lower the priority of the batch using a PATCH
Change the worker daemon zone using a PATCH
Cancel the batch by sending a DELETE request, which sets the status to
Cancelling. The cancellation is not an instant process, but instead, it will let the existing jobs of the batch finish. No new jobs will be created. After the jobs are finished, the status is set toCancelled.