Skip to content
This repository has been archived by the owner on Aug 16, 2022. It is now read-only.

Optimization required on ES service during ES High CPU usage ( Data loss ) #439

Closed
pcinnusamy opened this issue Mar 9, 2021 · 1 comment

Comments

@pcinnusamy
Copy link

Hi Team ,

On last week ,One of our ODES (open distro Elastic search) cluster experienced high CPU load (NewRelic) and caused the indices to be out of sync (temporarily outdated, but eventually recovered).

We are suspecting that ES itself is not optimized, and during high loads, this causes delay and missing data while syncing data from MongoDB.

Please can you suggest how to optimize the ODES during High CPU usage or How to optimize the Mongo connector Index

@pcinnusamy pcinnusamy changed the title Optimization required on ES cluster during High CPU usage ( Data loss ) Optimization required on ES service during ES High CPU usage ( Data loss ) Mar 9, 2021
@aetter
Copy link
Contributor

aetter commented May 19, 2021

Hi there, it's true that high periods of sustained CPU load can cause Elasticsearch to throw errors, etc. Part of the solution is just throwing more hardware at the Elasticsearch cluster. The other part is having some sort of retry logic in your indexer (although in this case, it sounds like it recovered over time).

@aetter aetter closed this as completed May 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants