Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.
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. Take a self-guided product tour to see for yourself (no registration required).
This guide will help you check for common problems that cause the log ” Problem fetching instance list for zone ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cloud-aws, discovery-gce, instances and plugins.
Log Context
Log “Problem fetching instance list for zone {}” classname is GceInstancesServiceImpl.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
});
// assist type inference
return instanceList.isEmpty() || instanceList.getItems() == null ?
Collections.emptyList() : instanceList.getItems();
} catch (IOException e) {
logger.warn((Supplier>) () -> new ParameterizedMessage("Problem fetching instance list for zone {}"; zoneId); e);
logger.debug("Full exception:"; e);
// assist type inference
return Collections.emptyList();
}
}).reduce(new ArrayList(); (a; b) -> {
Find & fix Elasticsearch problems
