Cannot create job – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch is unable to create a new job due to a variety of reasons such as insufficient permissions, lack of resources, or a conflict with an existing job. To resolve this issue, you can check if the user has the necessary permissions to create a job, ensure there are enough resources available, and verify that there isn’t a job with the same name already existing. If the problem persists, you may need to check the Elasticsearch logs for more detailed error messages.

This guide will help you check for common problems that cause the log ” Cannot create job [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Cannot create job [” class name is TransportPutRollupJobAction.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 persistentTasksService.sendStartRequest(job.getConfig().getId(); RollupField.TASK_NAME; job;
 ActionListener.wrap(
 rollupConfigPersistentTask -> waitForRollupStarted(job; listener; persistentTasksService);
 e -> {
 if (e instanceof ResourceAlreadyExistsException) {
 e = new ElasticsearchStatusException("Cannot create job [" + job.getConfig().getId() +
 "] because it has already been created (task exists)"; RestStatus.CONFLICT; e);
 }
 listener.onFailure(e);
 }));
 }

 

 [ratemypost]