Sharded Cluster Chunk error

Ops and Admin Sharding
1

I have sharded Cluster.
I am using 4 shards.
Other collections work fine, but one collection doesn’t.

An example of what I think the normal state :

{
test.item
    shard key : {"num" : "hashed"}
    unique : false
    balancing : true
    chunks: 
                  shard1 2
                  shard2 2
                  shard3 2
                  shard4 2
}

Abnormal collection currently being output :

{
test.item
    shard key : {"num" : "hashed"}
    unique : false
    balancing : true
    chunks: 
                  shard1 1
                  shard3 1
                  shard4 1
}

Is the output now normal?
If it’s not normal, how can I fix it?

2

Hi @Park_49739 ,

I assume you are referring to your second collection only existing on three shards at the moment?

This would be expected if the collection only has three chunk ranges. Additional chunks will be created as needed when more data is inserted to the collection, and chunks will be distributed across shards by the Sharded Cluster Balancer.

If you are concerned about some other aspect of this output, please provide more details.

Regards,
Stennie

3

Hi. @Stennie_X

I’m experiencing the same symptoms.
However, is this the hashed shard key, and even though there are about 10,000 total documents, can the above phenomenon occur?