[SERVER-30167] Vsize / res in mongostat Created: 17/Jul/17  Updated: 09/Oct/17  Resolved: 30/Aug/17

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

Type: Question Priority: Minor - P4
Reporter: max hoarau [X] Assignee: Mark Agarunov
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

1 replicaset with three identical servers( 4 cpu / 32 Go RAM under linux ubuntu v16)
1 primary and two secondaries.
No delay in replication every thing is up ta date.
The engine is WiredTigger.


Participants:

 Description   

Hi all,
I would like to have your opinion and of course an explanation on the following.
During insertion or update time I have the following
Primary : vsize : 3.73 G/ res : 3.02 G
1st secondary : vsize : 3.28 G / res : 2.63 G
2nd secondary : vsize : 5.66 G / res : 5.02G
I am wondering why is there this difference between the vsize/res of the 2nd secondary and the 1st one?
I was guessing that I should see some kind of equality between them because they both support the same informations from the primary.
Any help or informations will bee appreciated. Thanks in advance and best regards.
Max.



 Comments   
Comment by Mark Agarunov [ 30/Aug/17 ]

Hello mHoarau,

Thanks for your report. Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group.

Thanks,
Mark

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