[SERVER-16392] ShardInfo should stop using mapped to get size estimate Created: 02/Dec/14  Updated: 26/May/17  Resolved: 19/Dec/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.8.0-rc1
Fix Version/s: 2.8.0-rc4

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: wiredtiger
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-15831 Enhanced top chunk auto split tests Closed
Documented
is documented by DOCS-9849 Documentation about maxSize parameter... Closed
Tested
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Some storage engine will not be using memory mapping, so this will be zero. This is currently used only for determining whether a shard has reached the "maxSize" setting.



 Comments   
Comment by Githook User [ 19/Dec/14 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-16392 ShardInfo should stop using mapped to get size estimate
Branch: master
https://github.com/mongodb/mongo/commit/434a0837fa81a501c0e1426506d0dcaba0be43c0

Comment by Daniel Pasette (Inactive) [ 12/Dec/14 ]

cc: schwerin.
This ticket refers to the maxSize setting used in addShard.

Comment by Randolph Tan [ 02/Dec/14 ]

It looks like we can use the totalSize field from the listDatabases command instead.

Generated at Thu Feb 08 03:40:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.