Failed to update shard information for ClusterInfoUpdateJob within 15s timeout – How to solve related issues

Failed to update shard information for ClusterInfoUpdateJob within 15s timeout – How to solve related issues

Opster Team

Feb-21, Version: 1.7-8.0

To understand why Elasticsearch failed to update shard information for ClusterInfoUpdateJob within 15s timeout, we recommend run the Elasticsearch Error Check-Up. It will help you configure your settings optimally to avoid this log in the future.

This guide will help you check for common problems that cause the log “Failed to update shard information for ClusterInfoUpdateJob within 15s timeout” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cluster and shard.

Log Context

Log “Failed to update shard information for ClusterInfoUpdateJob within 15s timeout” classname is InternalClusterInfoService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
            try {
                indicesLatch.await(fetchTimeout.getMillis(); TimeUnit.MILLISECONDS);
            } catch (InterruptedException e) {
                Thread.currentThread().interrupt(); // restore interrupt status
                logger.warn("Failed to update shard information for ClusterInfoUpdateJob within 15s timeout");
            }

            for (Listener l : listeners) {
                try {
                    l.onNewInfo(getClusterInfo());




 

Run the Check-Up to get customized recommendations like this:

error

The high disk watermark threshold is about to be reached in specific nodes

error-img

Description

There are various “watermark” thresholds on each Elasticsearch cluster. When the high disk watermark threshold has been exceeded, it means disk space is running out. The node will…

error-img

Recommendations

Based on your specific ES deployment you should…

1

X-PUT curl -H [a customized code snippet to resolve the issue]

Optimize Elasticsearch Performance

Run The Tool