[DOCS-5682] Document that the size and count in collection stats is not guaranteed to be 100% accurate Created: 19/Jun/15  Updated: 11/Jan/17  Resolved: 04/Dec/15

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Major - P3
Reporter: Daniel Pasette (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: docs-3.2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-19472 count() incorrect after recovery with... Closed
documents SERVER-19052 Remove sizeStorer recalculations at s... Closed
Related
related to DOCS-7979 Size and count in collection stats ar... Closed
Participants:
Days since reply: 8 years, 10 weeks, 6 days ago

 Description   

See: SERVER-19052
With WiredTiger, the size and count stats are not guaranteed to be accurate in the event of an unclean shutdown because the size and count are only persisted every 1000 writes. Accurate values can be restored by performing a validate command on any collection that has drifted.



 Comments   
Comment by Githook User [ 04/Dec/15 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-5682 size and count stats for WT
Branch: master
https://github.com/mongodb/docs/commit/1769b8687cdca9df03ffda67e08118d18d0cfa91

Comment by Max Hirschhorn [ 21/Jun/15 ]

It is probably worth mentioning that the user must perform a full validation

db.runCommand({validate: "collName", full: true})

in order to restore the accuracy of the size and count stats. Implementation details.

Generated at Thu Feb 08 07:50:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.