Liferay Enterprise Search
- [LES]: How to install and run the Elastic Support Diagnostics Troubleshooting Utility
- [LES] About Elasticsearch License expiration
- [LES] Elasticsearch Virtual Machine Considerations
- [LES] Getting Started with Liferay Enterprise Search
- [LES] How to use a load balancer with Elasticsearch?
- [LES] Installing the Learning-to-Rank plugin on Elasticsearch fails with "IllegalStateException: ltr requires Java 14"
- [LES] What is the recommended Java heap size for Elasticsearch?
- [LES] Which node types are charged as part of the Liferay Enterprise Search Subscription
- Easily customize Liferay's search behavior with Blueprints
- Elasticsearch 7.17 End of Life (EOL) Timeline and Liferay DXP Elasticsearch Compatibility Update & FAQ
- Liferay Enterprise Search Experiences (Blueprints) 1.1.0 for DXP 7.3 Release Highlights & Upgrade Instructions
[LES] Which node types are charged as part of the Liferay Enterprise Search Subscription
This article explains the Elasticsearch node types that are charged as part of the Liferay Enterprise Search subscription.
Resolution
The following Elasticsearch nodes count towards your Liferay Enterprise Search subscription:
- Data nodes
- Master nodes (including “voting-only”)
- Tribe nodes
- Cross Cluster Search nodes
- Machine Learning nodes
The following node types do NOT count against your subscription:
- Dedicated Coordinating nodes
- Dedicated Ingest nodes
In addition, you may have one dedicated 1-node monitoring cluster as part of your subscription which will NOT count against your total amount, with the following restrictions:
- This cluster may only be used for monitoring data from the production cluster
- This monitoring node should have the non-production license applied to it
- The only plugins which may be used, besides Monitoring itself, are Security and Watcher (to allow alerting on monitoring data).
Please note that if a node combines multiple roles, you will need a license for that node if any of the roles require a license. However, if more than one role requires a license, you don't need multiple licenses for that node. Each node requires at most one license for all the roles it carries.