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 not behaving as documented #15803
Comments
I think it is caused by |
and 7.10 backport elastic/elasticsearch@e4054e4
I will port those docs + mention in docs that On auto-expanding replicas (which we have enabled by default, it's 0-1). UPD: https://www.elastic.co/guide/en/elasticsearch/reference/7.17/index-modules.html
Probably by design, but I will check why we cannot do it like @jeeminso proposed in #15805
|
Hi @hlcianfagna could you please post your initital create table statment(s) - how you got those 26/27 shards? Also, couldn't exactly reproduce locally: do you get 32 shards per node after running What I'm saying is that slightly overshooting limit might be expected behavior but reporting error and still incrementing number of shards would be a bug. I suspect that actually 32 shards were already there after |
They were already there on a cluster that I do not have at hand anymore, however I just reproduced this again successfully using this on an empty cluster: create table hernan.legacytables (a int) clustered into 40 shards; I confirmed the 32 shards per node are there right after the command with |
ok, then I will follow my original plan - improve docs (basically expected behaviour for auto-expanding replicas). As said, throwing an error |
CrateDB version
5.6.3
CrateDB setup information
3 nodes cluster deployed with https://github.com/crate/crate-terraform
Problem description
According to https://cratedb.com/docs/crate/reference/en/5.6/config/cluster.html#shard-limits
However in a multi-node cluster (could not repro this on single-node environments) it seems under certain conditions the limit is not strictly enforced.
Steps to Reproduce
Actual Result
The nodes end up with 32 shards
Expected Result
The limit of 30 shards is enforced, or the documentation is updated explaining how the limit works/when it may not be enforced.
The text was updated successfully, but these errors were encountered: