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.
This guide will help you check for common problems that cause the log ” Too many affix files exist for 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 “Too many affix files exist for hunspell dictionary [%s]”classname is HunspellService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :
Path[] affixFiles = FileSystemUtils.files(dicDir; "*.aff");
if (affixFiles.length == 0) {
throw new ElasticsearchException(String.format(Locale.ROOT; "Missing affix file for hunspell dictionary [%s]"; locale));
}
if (affixFiles.length != 1) {
throw new ElasticsearchException(String.format(Locale.ROOT; "Too many affix files exist for hunspell dictionary [%s]"; locale));
}
InputStream affixStream = null;
Path[] dicFiles = FileSystemUtils.files(dicDir; "*.dic");
List dicStreams = new ArrayList<>(dicFiles.length);
See how you can use AutoOps to resolve issues
