Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.
To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.
Take a self-guided product tour to see for yourself (no registration required).This guide will help you check for common problems that cause the log ” Could not find hunspell dictionary %s ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, analysis.
Log Context
Log “Could not find hunspell dictionary [%s]”classname is HunspellService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :
if (logger.isDebugEnabled()) {
logger.debug("Loading hunspell dictionary [{}]..."; locale);
}
Path dicDir = hunspellDir.resolve(locale);
if (FileSystemUtils.isAccessibleDirectory(dicDir; logger) == false) {
throw new ElasticsearchException(String.format(Locale.ROOT; "Could not find hunspell dictionary [%s]"; locale));
}
// merging node settings with hunspell dictionary specific settings
Settings dictSettings = HUNSPELL_DICTIONARY_OPTIONS.get(nodeSettings);
nodeSettings = loadDictionarySettings(dicDir; dictSettings.getByPrefix(locale + "."));
Find & fix Elasticsearch problems
