Error notifying global checkpoint listener of closed shard – How to solve related issues

Average Read Time

2 Mins

Error notifying global checkpoint listener of closed shard – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Error notifying global checkpoint listener of closed shard ” 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: index, listeners and shard.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

{{mpg_logstarted}}

Log “Error notifying global checkpoint listener of closed shard” classname is GlobalCheckpointListeners.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         new ParameterizedMessage(
                                "error notifying global checkpoint listener of updated global checkpoint [{}]";
                                globalCheckpoint);
                        caught);
            } else if (e instanceof IndexShardClosedException) {
                logger.warn("error notifying global checkpoint listener of closed shard"; caught);
            } else {
                logger.warn("error notifying global checkpoint listener of timeout"; caught);
            }
        }
    }




 

Run the Check-Up to get a customized report like this:

Analyze your cluster