- Newest
- Most votes
- Most comments
Hello,
From the information provided, it looks like it is related to a growing terms index. Even though newer versions of ElasticSearch try to use less memory, it could be because it's constantly trying to cleanup the exhausted heap space (memory). Also, check how are your shards setup.
AWS ElasticSearch Instances allocate half of their memory to heap space. Wether to scale up, out, or both, depends a lot on your mapping. You'll find some quick relief by scaling up to an instance with more memory, but you'll have to take a deeper look at your mapping and queries to get the best long-term scalability.
Elastic search is very picky. The hardware environment it likes to run on, although always memory intensive, varies a lot based your mapping and the types of queries you throw at it. It is likely that, after you get it stable, you'll have to tweak it to find the happy-spot based on your performance/cost/storage needs.
I would advise opening up a case with the AWS PS team and work with them on the same to double check.
Relevant content
- asked a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago