We need information regarding elastic search configuration for our application environment.
We use elastic search very extensively for our application for search and indexing.
Our application is using Liferay (portal development) with Java as development platform.
We are facing slowness in application related to elastic search when more users are using the application. In application we do a lot of index read and write with several operations.
As per our application monitoring we see many thread are in waiting status for read/write indexing.
Please suggest the best elastic search configuration as per below mentioned application details.
Application: Portal developed on Liferay with Java
Database :- Oracle
Java Version :- Open JDK 8
Search Engine :- Elastic Search
Elastic Search Version :- 6.1.3
Operation System: - Linux
Number of nodes :- 2/4
CPU Cores :- 4 cores
Number of concurrent users at a time :- 100 - 200 (2 nodes) / 250 - 400 (4 nodes)
We use LINUX servers (not laptops) with no additional SSD storage.
Workload mostly includes Searching articles/ documents and media, searching users , updating users (write actions) . Also it includes getting list of articles by type . etc
As per our monitoring I see queries are mostly search ,
org.elasticsearch.action.bulk.BulkRequest (count of 1400 for a 10 minute test),
org.elasticsearch.action.admin.indices.refresh.RefreshRequest (count of 900 for a 10 minute test)
etc.
Also we see LIMIT EXCEEDED BUCKET in monitoring log queries for elastic search (count of 1841 for a 10 minute test).
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.