Shard must have a valid translog UUID but got null – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch cannot find a valid transaction log (translog) UUID for a shard. This could be due to corruption or deletion of the translog. To resolve this issue, you can try to restore the data from a backup. If a backup is not available, you may need to delete and recreate the index. However, this will result in data loss. Another option is to use the Elasticsearch “shrink” API to create a new index from the existing one, which may bypass the corrupted translog.

This guide will help you check for common problems that cause the log ” shard must have a valid translog UUID but got: [null] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: shard, index.

Log Context

Log “shard must have a valid translog UUID but got: [null]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 // Retrieve the generation and UUID from the existing data
 final Map commitData = new HashMap<>(commits.get(commits.size() - 1).getUserData());
 final String translogUUID = commitData.get(Translog.TRANSLOG_UUID_KEY);  if (translogUUID == null) {
 throw new ElasticsearchException("shard must have a valid translog UUID but got: [null]");
 }  final boolean clean = isTranslogClean(shardPath; clusterState; translogUUID);  if (clean) {


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?