[SERVER-36481] when we use MongoDB sharding, wiredtigerlas,wt grows very big Created: 07/Aug/18  Updated: 15/Nov/21  Resolved: 26/Apr/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: lifei dang Assignee: Ramon Fernandez Marina
Resolution: Incomplete Votes: 1
Labels: Bug
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

centos


Operating System: ALL
Participants:

 Description   

1 when we use MongoDB sharding, wiredtigerlas,wt grows very big, the file size exceed disk size



 Comments   
Comment by Nick Brewer [ 14/Sep/18 ]

danglifei006 Since we haven't heard back from you, I'm going to close this ticket - if you'd like us to re-open it, feel free to comment here. We'll need the information requested previously.

Thanks,
-Nick

Comment by Nick Brewer [ 20/Aug/18 ]

danglifei006 Just wanted to check in with you to see if you've had a chance to get the data we requested previously.

Thanks,
Nick

Comment by Nick Brewer [ 07/Aug/18 ]

danglifei006 Thanks for your report. Some information I'd like to confirm:

  • Is this a sharded replica set? If so, please include the output of rs.conf().protocolVersion
  • Are all of the mongod processes running on the same version? What version(s) are in use?
  • An archive (tar or zip) of the $dbpath/diagnostic.data directory from a mongod that is experiencing this issue

Thanks,
Nick

Generated at Thu Feb 08 04:43:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.