Stopping task with force – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

Briefly, this error occurs when a task in Elasticsearch is stopped with force, which can cause issues with the operation of the task and Elasticsearch. To resolve this issue, you can try to check the task for errors, or try to restart the task.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Stopping task with force ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin and task.

Log Context

Log “[{}] Stopping task with force [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


                    protected void doRun() {
              "[{}] Stopping task with force [{}]"; task.getParams().getId(); request.isForce());
                        task.stop("stop_data_frame_analytics (api)"; request.getTimeout());
                        listener.onResponse(new StopDataFrameAnalyticsAction.Response(true));


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content