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

max shards per node reached (1000 by default) #44

Open
nbittich opened this issue Jul 29, 2022 · 2 comments
Open

max shards per node reached (1000 by default) #44

nbittich opened this issue Jul 29, 2022 · 2 comments

Comments

@nbittich
Copy link
Contributor

Issue when indexing a lot of data (app-loket).

Current workaround:

curl -X PUT localhost:9200/_cluster/settings -H "Content-Type: application/json" -d '{ "persistent": { "cluster.max_shards_per_node": "7000" } }'
{"acknowledged":true,"persistent":{"cluster":{"max_shards_per_node":"3000"}},"transient":{}}
@nvdk
Copy link
Member

nvdk commented Aug 11, 2022

it would probably be a good idea to run multiple nodes (even if only on the same server)

@nbittich
Copy link
Contributor Author

@nvdk it seems to be the safe solution, however it can be fine tuned (https://www.elastic.co/guide/en/elasticsearch/reference/current/size-your-shards.html#field-count-recommendation) . I guess in some cases it could be fine tuned based on recommenfations of elasticsearch? FYI for a poc for loket, we had more than 1.8k indices:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants