Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
Fully Compatible
-
ALL
-
-
Sharding 2019-10-21
Description
Output of getShardDistribution():
data : 63KiB docs : 108 chunks : 0
|
estimated data per chunk : 0B
|
estimated docs per chunk : 0
|
|
|
data : 53KiB docs : 92 chunks : 0
|
estimated data per chunk : 0B
|
estimated docs per chunk : 0
|
|
|
Totals
|
data : 116KiB docs : 200 chunks : 0
|
Shard query_fuzzer-524659-1569598253645-0-rs1 contains 53.86% data, 54% docs in cluster, avg obj size on shard : 597B
|
Shard query_fuzzer-524659-1569598253645-0-rs0 contains 46.13% data, 46% docs in cluster, avg obj size on shard : 600B
|
config.chunks.find({ns: 'fuzzer.fuzzer_coll'}).itcount() = 4 // so there are actually 4, not 0 chunks
|
|
Attachments
Issue Links
- is related to
-
SERVER-44051 getShardDistribution() does not report "Collection XYZ is not sharded" on dropped but previously sharded collections
-
- Closed
-
-
SERVER-44052 Inconsistencies in sharded collections
-
- Closed
-