JobId Failed to clear finished time – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch fails to clear the finished time for a specific job ID. This could be due to a variety of reasons such as insufficient permissions, network issues, or a bug in the system. To resolve this issue, you can try the following: 1) Check and adjust the user permissions if necessary, 2) Investigate network connectivity issues, 3) Restart the Elasticsearch service, 4) Update Elasticsearch to the latest version to fix potential bugs, and 5) Check the job ID for any inconsistencies or errors.

This guide will help you check for common problems that cause the log ” [” + jobId + “] Failed to clear finished_time ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[” + jobId + “] Failed to clear finished_time” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        TimeValue masterNodeTimeout;
        ActionListener listener
    ) {
        final JobUpdate update = new JobUpdate.Builder(jobId).setClearFinishTime(true).build();
        ActionListener clearedTimeListener = ActionListener.wrap(job -> listener.onResponse(response); e -> {
            logger.error(() -> "[" + jobId + "] Failed to clear finished_time"; e);
            // Not a critical error so continue
        ActionListener mappingsUpdatedListener = ActionListener.wrap(
            mappingUpdateResponse -> jobConfigProvider.updateJob(jobId; update; null; clearedTimeListener);


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?