Partial response while loading watches – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch’s Watcher feature is unable to load all watches due to some watches being in a faulty state. This could be due to issues like incorrect watch configuration or insufficient resources. To resolve this, you can try the following: 1) Check and correct the configuration of your watches. 2) Increase the resources allocated to Elasticsearch if they are insufficient. 3) Delete and recreate the problematic watches. 4) Check the Elasticsearch logs for more detailed error messages that can help identify the problem.

This guide will help you check for common problems that cause the log ” Partial response while loading watches ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: response, plugin.

Log Context

Log “Partial response while loading watches” class name is WatcherService.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 .preference(Preference.ONLY_LOCAL.toString())
 .source(new SearchSourceBuilder().size(scrollSize).sort(SortBuilders.fieldSort("_doc")).seqNoAndPrimaryTerm(true));
 response = client.search(searchRequest).actionGet(defaultSearchTimeout);  if (response.getTotalShards() != response.getSuccessfulShards()) {
 throw new ElasticsearchException("Partial response while loading watches");
 }  if (response.getHits().getTotalHits().value == 0) {
 return Collections.emptyList();
 }

 

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?