Could not get token document for refresh retrying – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.2-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.

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 [{}] for refresh; 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 [{}] for refresh; retrying” classname is TokenService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                                @Override
                                public void onFailure(Exception e) {
                                    if (isShardNotAvailableException(e)) {
                                        if (backoff.hasNext()) {
                                            logger.info("could not get token document [{}] for refresh; retrying"; tokenDocId);
                                            client.threadPool()
                                                .schedule(
                                                    () -> getTokenDocAsync(tokenDocId; refreshedTokenIndex; true; this);
                                                    backoff.next();
                                                    GENERIC

 

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?