[Feature Request] segment replication and merged segment warmer use a dedicated threadpool

[guojialiang92]

Is your feature request related to a problem? Please describe

Currently, both segment replication and merged segment warmer are scheduled using the GENERIC thread pool, which is responsible for node discovery, peer recovery, and many transport actions.

When the number of shards increases, the number of segment replication and merged segment warmer task will also increase accordingly.

Using an dedicate thread pool can not only avoid resource contention but also make it easier to monitor segment replication-related tasks.

Describe the solution you'd like

We should use a dedicated threadpool (say REPLICATION) to avoid any contention due to resource starvation.

Related component

Indexing:Replication

Describe alternatives you've considered

No response

Additional context

No response

[guojialiang92]

Hi, @ashking94 @mch2 @Bukhtawar

I would like to hear from the community on whether this change makes sense.

[Bukhtawar]

Thanks @guojialiang92
Sounds good to introduce a replication threadpool

[guojialiang92]

@Bukhtawar

Thanks @guojialiang92 Sounds good to introduce a replication threadpool

OK, I will submit a PR to support a dedicated replication threadpool. :)

[ashking94]

@guojialiang92 I have reviewed the PR.