The normal_transfer_queue_consumer thread pool is created by default in OpenSearch. It is used for facilitating communication and data movement within the cluster.
In essence, while you don’t have to directly configure it, normal_transfer_queue_consumer is a vital, low-level component that OpenSearch automatically manages to ensure smooth and reliable data flow between its nodes, which is fundamental to its operation as a distributed database and search engine.
In my case normal_transfer_queue_consumer is always active and it’s count is 24. Will there be any performance impact ? Any reason why the thread count is 24.
Below is the resource configuration used for opensearch pods