Log Failed to get token since index is not available – How To Solve Related Issues



Log Failed to get token since index is not available – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

 

Before you read this guide, we recommend you run the Elasticsearch Error Check-Up which detects issues in ES that cause log errors. It’s a free tool that requires no installation and takes 2 minutes to complete.

This guide will help you check for common problems that cause the log ” Failed to get token since index is not available ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: index and plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them. Among the dozens of checks included are: shards sizes, thread pools, management queue size, search errors, circuit breakers and many more (join over 700 users who use this free tool).

Log Context

Log “Failed to get token [{}] since index is not available” classname is TokenService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                                                     }
                                                }; e -> {
                                                    // if the index or the shard is not there / available we assume that
                                                    // the token is not valid
                                                    if (isShardNotAvailableException(e)) {
                                                        logger.warn("failed to get token [{}] since index is not available"; tokenId);
                                                        listener.onResponse(null);
                                                    } else {
                                                        logger.error(new ParameterizedMessage("failed to get token [{}]"; tokenId); e);
                                                        listener.onFailure(e);
                                                    }






Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Java ElasticSearch None of the configured nodes are available -views 128.72 K ,score 52

2 Github Issue Number 12366






Optimize Elasticsearch Performance

Try The Tool