README mention- ElasticSeach heap size

[MarcinGinszt]

Name and Version

bitnami/elasticsearch

What is the problem this feature will solve?

Currently, ElasticSearch heap size is set using ELASTICSEARCH_HEAP_SIZE env variable.
Elastic docs say, leaving it alone is fine and even recommended, since ES can figure it out itself basing on the available memory.
Default value of ELASTICSEARCH_HEAP_SIZE is very low, so it forces the user to modfiy it for most of the cases.

What is the feature you are proposing to solve the problem?

I think it would be valuable to point out the reason for using ELASTICSEARCH_HEAP_SIZE in the README, and suggest changing it together with memory limit.

What alternatives have you considered?

No response

[carrodher]

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

[MarcinGinszt]

I'd be glad to contribute, but honestly I don't know the reason behind using ELASTICSEARCH_HEAP_SIZE

[rafariossaa]

Hi,
Thanks for bringing this, I am creating and internal task in to evaluate the needed changes as this would also need changes in the container image.
We will be back as soon as we have news.