Briefly, this error occurs when the Elasticsearch Watcher feature, which monitors data changes, is interrupted during its polling process. This could be due to system resource constraints, network issues, or an abrupt shutdown. To resolve this, you can increase system resources, check network connectivity, ensure a stable environment to prevent abrupt shutdowns, or adjust the Watcher’s polling interval to reduce its frequency. If the issue persists, consider checking for any underlying issues with your Elasticsearch cluster.
This guide will help you check for common problems that cause the log ” Watch[{}] reporting[{}] thread was interrupted; while waiting for polling. Aborting. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, thread.
Log Context
Log “Watch[{}] reporting[{}] thread was interrupted; while waiting for polling. Aborting.” class name is ReportingAttachmentParser.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
private void sleep(long sleepMillis; WatchExecutionContext context; ReportingAttachment attachment) {
try {
Thread.sleep(sleepMillis);
} catch (InterruptedException e) {
Thread.currentThread().interrupt();
throw new ElasticsearchException("Watch[{}] reporting[{}] thread was interrupted; while waiting for polling. Aborting.";
context.watch().id(); attachment.id());
}
} /**
