Como solucionar problemas de exceção do interruptor no Amazon OpenSearch Service?

Como resolvo a exceção “failed to obtain in-memory shard lock” (falha ao obter o bloqueio de fragmento na memória) no Amazon OpenSearch Service?

Como posso resolver o erro “You have exceeded the allowed number of AWS accounts” (Você excedeu o número permitido de contas da AWS) para o AWS Organizations?

Como soluciono o erro “The security token included in the request is expired” (O token de segurança incluído na solicitação está expirado) ao executar aplicações Java no Amazon EC2?

ElasticSearch Service have a useful metric **JVM memory pressure** that specifies the percentage of the Java heap occupied in a cluster node. **CMSInitiatingOccupancyFraction** is the threshold value on which Garbage collection activity starts to clean deleted items from ES node memory to reduce JVM Memory pressure.  [refer article for more information](https://medium.com/naukri-engineering/garbage-collection-in-elasticsearch-and-the-g1gc-16b79a447181)

Our application have clean up tasks executed on weekly basis and we are exploring options to lower down CMSInitiatingOccupancyFraction (which is by default set to 75%) value. As cleanup tasks gets executed we are thinking of setting this threshold to 65-70%. We didn't found any configuration options to fix this value. Is there any other mechanism to activate Garbage collector?

Does AWS Elastic search service provide options to configure these default values? If yes then guide us through steps.

Configure CMSInitiatingOccupancyFraction value for Elasticsearch service

Conteúdo relevante