I want to understand what would be the actual behaviour of the WIRED Tiger engine in the below case
Write IOPS is very high, exceeding provisioned or expected capacity for several 5-mins intervals together, almost 2-3 times of expected capacity. For eg if its M10 or M20 the peak IOPS is 100. Lets say if the IOPS is going beyond 250 consistently for 30 mins
What exactly happens during this sceario. Would the Wired Tiger engine queue all the operations and then keep clearing the queue based on Disk IOPS. If this is the case, assuming the relevant documnts are in memory set (cache) would it do the writes to the memory cache first and then write to the DB. So basically even if the write operation takes time to get completed (based on how far it is down the queue), future reads of the same document wont be affected since it will be read from cache.
This is my guess. I would like to know how the WiredTiger engine works