Failed to create token document – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.2-7.15

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch fails to create a token document, which is essential for security features like user authentication and authorization. This could be due to insufficient permissions, a full disk, or a network issue. To resolve this, you can check and adjust the user permissions, ensure there’s enough disk space, or troubleshoot the network connectivity. Also, verify the Elasticsearch version compatibility with the security features and ensure the cluster health status is green.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” failed to create token document [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, document.

Log Context

Log “failed to create token document [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 // Such nodes might exist in a mixed cluster during a rolling upgrade.
 listener.onResponse(new CreateTokenResult(versionedAccessToken; refreshToken;authentication));
 } else {
 listener.onFailure(traceLog("create token";
 new ElasticsearchException("failed to create token document [{}]"; indexResponse)));
 }; listener::onFailure)));


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?