Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Support total_primary_shards_per_node limit for segrep indices #12556

Open
Bukhtawar opened this issue Mar 7, 2024 · 0 comments
Labels
enhancement Enhancement or improvement to existing feature or request ShardManagement:Placement

Comments

@Bukhtawar
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement or improvement to existing feature or request ShardManagement:Placement
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant