Generation = manifest getGlobalGeneration – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7-7.5

Briefly, this error occurs when Elasticsearch is unable to match the current global generation number with the one stored in the manifest file. This could be due to a synchronization issue or a problem with the cluster state. To resolve this, you could try restarting the Elasticsearch node, ensuring that all nodes in the cluster are running the same version of Elasticsearch, or checking the integrity of the manifest file. If the problem persists, you may need to restore from a backup or reindex your data.

This guide will help you check for common problems that cause the log ” [generation = ” + manifest.getGlobalGeneration() + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster.

Log Context

Log ” [generation = ” + manifest.getGlobalGeneration() + “]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 terminal.println(Terminal.Verbosity.VERBOSE; "Loading global metadata file");
 final MetaData metaData = MetaData.FORMAT_PRESERVE_CUSTOMS.loadGeneration(
 logger; NamedXContentRegistry.EMPTY; manifest.getGlobalGeneration(); dataPaths);
 if (metaData == null) {
 throw new ElasticsearchException(NO_GLOBAL_METADATA_MSG + " [generation = " + manifest.getGlobalGeneration() + "]");
 }  return Tuple.tuple(manifest; metaData);


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?