You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
The current limit on total_shards_per_node doesn't help in case of segrep since primaries do the actual work and we can run into situations where we have multiple primary on one node and multiple replica on another node causing a skew in resource utilisation and decreased throughput
Describe the solution you'd like
Having a limit on total_primary_shard_per_node will help distribute primary load for segrep indices across all nodes
Related component
Cluster Manager
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
The current limit on total_shards_per_node doesn't help in case of segrep since primaries do the actual work and we can run into situations where we have multiple primary on one node and multiple replica on another node causing a skew in resource utilisation and decreased throughput
Describe the solution you'd like
Having a limit on total_primary_shard_per_node will help distribute primary load for segrep indices across all nodes
Related component
Cluster Manager
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: