-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: manual
-
Labels:
-
Environment:All
*Location*: http://docs.mongodb.org/manual/tutorial/merge-chunks-in-sharded-cluster/
*User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36
*Referrer*: https://www.google.com/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: tutorial/merge-chunks-in-sharded-cluster
All *Location*: http://docs.mongodb.org/manual/tutorial/merge-chunks-in-sharded-cluster/ *User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36 *Referrer*: https://www.google.com/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: tutorial/merge-chunks-in-sharded-cluster
The command to determine if a chunk is empty needs to be run on the database in which the chunk resides. The documentation does not mention this, and it should! Would have saved me a good deal of time 
.
EX:
db.runCommand({
"dataSize": "test.users",
"keyPattern":
,
"min":
,
"max":
})
Needs to be run while in the context of the "test" database.
- related to
-
SERVER-21976 dataSize cmd should ignore current database in mongos
-
- Closed
-