Briefly, this error occurs when Elasticsearch tries to forcefully close jobs but fails to isolate all datafeeds associated with those jobs. This could be due to network issues, heavy load, or a bug in the system. To resolve this issue, you can try the following: 1) Retry closing the jobs after some time, 2) Check the system’s health and load, and optimize if necessary, 3) Investigate for any bugs in the system that might be causing this issue, and 4) If the problem persists, consider restarting the Elasticsearch cluster.
This guide will help you check for common problems that cause the log ” could not isolate all datafeeds while force closing jobs ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “could not isolate all datafeeds while force closing jobs ” classname is TransportCloseJobAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
// after the isolation request fails but before we follow up with the force close. In this case force stopping
// the datafeed will gracefully close the associated job if the datafeed has an end time; which is not what we
// want. But this will be a rare edge case. Hopefully the loopholes can be closed during the job/datafeed
// unification project. In the meantime we'll log at a level that is usually enabled; to make diagnosing the
// race condition easier.
logger.info("could not isolate all datafeeds while force closing jobs " + openJobs; e);
listener.onResponse(null);
})
);
for (String runningDatafeedId : runningDatafeedIds) {
