Briefly, this error occurs when Elasticsearch tries to load a watch with a specific ID, but fails to find it. This could be due to the watch being deleted or not properly configured. To resolve this issue, you can check if the watch ID exists in your Elasticsearch cluster. If it doesn’t, create a new watch with the correct ID. If the watch exists but is not configured properly, you should correct the configuration. Also, ensure that the Elasticsearch cluster has the necessary permissions to access the watch.
This guide will help you check for common problems that cause the log ” couldn’t load watch [” + id + “]; ignoring it… ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “couldn’t load watch [” + id + “]; ignoring it…” classname is WatcherService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
Watch watch = parser.parse(id; true; hit.getSourceRef(); XContentType.JSON; hit.getSeqNo(); hit.getPrimaryTerm());
if (watch.status().state().isActive()) {
watches.add(watch);
}
} catch (Exception e) {
logger.error(() -> "couldn't load watch [" + id + "]; ignoring it..."; e);
}
}
SearchScrollRequest request = new SearchScrollRequest(response.getScrollId());
request.scroll(scrollTimeout);
response = client.searchScroll(request).actionGet(defaultSearchTimeout);
