Hi !
We are trying to understand if parameter indexing_pressure.memory.limit can be adjusted and how. We cannot find any info on how to change it, we found only this help link Indexing pressure | Elasticsearch Guide [8.2] | Elastic
Thanks a lot!
Why do you want to adjust this?
We've had an indexing pressure situation with below rejection errors:
"Caused by: org.Elasticsearch.transport.RemoteTransportException: [elk-mon-es-eu-central-1b-data-1][192.168.19.104:9300][indices:data/write/bulk[s]]",
"Caused by: org.Elasticsearch.common.util.concurrent.EsRejectedExecutionException: rejected execution of primary operation [coordinating_and_primary_bytes=3221225182, replica_bytes=0, all_bytes=3221225182, primary_operation_bytes=2121, max_coordinating_and_primary_bytes=3221225472]",
"at org.Elasticsearch.index.IndexingPressure.markPrimaryOperationStarted(IndexingPressure.java:105) ~[Elasticsearch-7.12.1.jar:7.12.1]",
"at org.Elasticsearch.action.support.replication.TransportWriteAction.checkOperationLimits(TransportWriteAction.java:80) ~[Elasticsearch-7.12.1.jar:7.12.1]",
"at org.Elasticsearch.action.support.replication.TransportWriteAction.checkOperationLimits(TransportWriteAction.java:49) ~[Elasticsearch-7.12.1.jar:7.12.1]",
"at org.Elasticsearch.action.support.replication.TransportReplicationAction.handleOperationRequest(TransportReplicationAction.java:277) ~[Elasticsearch-7.12.1.jar:7.12.1]",
"at org.Elasticsearch.xpack.security.transport.SecurityServerTransportInterceptor$ProfileSecuredRequestHandler$1.doRun(SecurityServerTransportInterceptor.java:261) ~[?:?]",
"at org.Elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26) ~[Elasticsearch-7.12.1.jar:7.12.1]",
"at org.Elasticsearch
So we have found there is a parameter that controls limit. We just wanted to understand if this is something adjustable, or we have to stick with default (10% of heap) and better not touch it.
It'd be useful if you shared the full error please.
We don't have full callstack unfortunately.