Elasticsearch indexing error- NoNodeAvailableException
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
legacy-article
learn-legacy-article-disclaimer-text
Issue
- Elasticsearch indexing error is getting thrown as below while upgrading the Liferay portal DB.
2020-02-21 11:39:23.096 ERROR [Framework Event Dispatcher: Equinox Container: 6783392e-6833-4d6c-bcda-f2debdcd5865][Framework:93] FrameworkEvent ERROR
java.lang.RuntimeException: org.elasticsearch.client.transport.NoNodeAvailableException: NoNodeAvailableException[None of the configured nodes are available: [{#transport#-1}{0EQaFBKLSc2rU8jpBqU6CQ}{10.85.18.55}{10.85.18.55:9300}]]
Resolution
- The above error shows that the data nodes seem to be not available and Liferay cannot find the aforesaid ES node.
-
Cluster Sniffing is enabled by default in the Liferay DXP connector which looks for data nodes from "transportAddresses" property configuration. If none of the nodes are available, the connector may throw "NoNodeAvailableException" in the console log.
-
For complete reference: Go through this help center article which describes the configuration in detail to resolve the "NoNodeAvailableException" issue.
did-this-article-resolve-your-issue