Using 50% of the controller memory for the JVM heap was the default behavior when we were using ElasticSearch. Now that we have switched to OpenSearch we have discovered that it is configured to default to a 1GB heap which is negatively affecting some of our queries.
Using 50% of the controller memory for the JVM heap was the default behavior when we were using ElasticSearch. Now that we have switched to OpenSearch we have discovered that it is configured to default to a 1GB heap which is negatively affecting some of our queries.