Could not load hunspell dictionary – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.2

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.

Briefly, this error occurs when Elasticsearch fails to load the Hunspell dictionary, which is used for spell checking. This could be due to incorrect dictionary path, missing dictionary files, or insufficient permissions. To resolve this, ensure the dictionary files are in the correct location and Elasticsearch has the necessary permissions to access them. Also, check the dictionary file format and encoding, as Elasticsearch only supports UTF-8 encoded Hunspell dictionaries. If the dictionary is in a different format, you may need to convert it to UTF-8.

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 load hunspell dictionary [{}] ” 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 load hunspell dictionary [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            try (Directory tmp = new NIOFSDirectory(env.tmpFile())) {
                return new Dictionary(tmp; "hunspell"; affixStream; dicStreams; ignoreCase);

        } catch (Exception e) {
            logger.error(() -> new ParameterizedMessage("Could not load hunspell dictionary [{}]"; locale); e);
            throw e;
        } finally {


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?

Get expert answers on Elasticsearch/OpenSearch