Running DBQ on String join indexNames get for job jobId – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.7

Briefly, this error occurs when Elasticsearch attempts to run a DBQ (Delete By Query) operation on a string join indexNames for a specific job and encounters an issue. This could be due to a variety of reasons such as incorrect syntax, insufficient permissions, or the index not existing. To resolve this, ensure the syntax of your DBQ operation is correct, check that the user has the necessary permissions to perform the operation, and verify that the index you’re trying to query actually exists.

This guide will help you check for common problems that cause the log ” Running DBQ on [” + String.join(“; “; indexNames.get()) + “] for job [” + jobId + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Running DBQ on [” + String.join(“; “; indexNames.get()) + “] for job [” + jobId + “]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        // Step 7. If we did not delete the indices; we run a delete by query
        ActionListener deleteByQueryExecutor = ActionListener.wrap(
                response -> {
                    if (response && indexNames.get().length > 0) {
              "Running DBQ on [" + String.join("; "; indexNames.get()) + "] for job [" + jobId + "]");
                        DeleteByQueryRequest request = new DeleteByQueryRequest(indexNames.get());
                        ConstantScoreQueryBuilder query =
                                new ConstantScoreQueryBuilder(new TermQueryBuilder(Job.ID.getPreferredName(); jobId));


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?