Could not find token document for refresh – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Could not find token document for refresh ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: document, plugin and refresh.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Could not find token document [{}] for refresh” classname is TokenService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                                         });
                                    client::update);
                            }
                        }
                    } else {
                        logger.info("could not find token document [{}] for refresh"; tokenDocId);
                        onFailure.accept(invalidGrantException("could not refresh the requested token"));
                    }
                }; e -> {
                    if (isShardNotAvailableException(e)) {
                        innerRefresh(tokenDocId; userAuth; listener; attemptCount);




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content