Could not get token document that should have been created retrying – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.7-8.9

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 retrieve a token document that should have been created. This could be due to issues with the security index or network connectivity problems. To resolve this, you can try the following: 1) Check the health of your Elasticsearch cluster and ensure all nodes are connected. 2) Verify the security index and its permissions. 3) Check the Elasticsearch logs for more detailed error messages. 4) If the issue persists, consider restarting your Elasticsearch cluster.

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 ” could not get token document [{}] that should have been created; retrying ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, document.

Log Context

Log “could not get token document [{}] that should have been created; retrying” classname is TokenService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                final Consumer onFailure = ex -> listener.onFailure(
                    traceLog("decrypt and get superseding token"; tokenDocId; ex)
                );
                final Consumer> maybeRetryGet = actionListener -> {
                    if (backoff.hasNext()) {
                        logger.info("could not get token document [{}] that should have been created; retrying"; tokenDocId);
                        client.threadPool()
                            .schedule(() -> getTokenDocAsync(tokenDocId; tokensIndex; false; actionListener); backoff.next(); GENERIC);
                    } else {
                        logger.warn("could not get token document [{}] that should have been created after all retries"; tokenDocId);
                        onFailure.accept(invalidGrantException("could not refresh the requested token"));

 

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?