[SERVER-17622] Total storage size for Journal substantially different for WT and MMAPv1 Created: 16/Mar/15 Updated: 30/Mar/15 Resolved: 17/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MMAPv1, Storage, WiredTiger |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alvin Richards (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | 28qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Steps To Reproduce: | /home/alvin/mongodb-linux-x86_64-3.0.1/bin/mongod --dbpath /data-nfs/db --logpath /data3/logs/db/sysbench/server.log --fork --syncdelay 14400 --storageEngine=mmapv1 --bind_ip 127.0.0.1 sh /home/alvin/alvin-sysbench-new/run.simple.bash 16 |
| Participants: |
| Description |
| Comments |
| Comment by Michael Cahill (Inactive) [ 16/Mar/15 ] |
|
It's true that syncdelay is ignored by WiredTiger. See I'm left unclear about whether you consider this a bug in the WiredTiger storage engine – what would you consider to be a fix for this issue? |
| Comment by Alvin Richards (Inactive) [ 16/Mar/15 ] |
|
--syncdelay 14400 causes the journal directory to be pruned only after this limit has been exceeded on MMAPv1. Reducing this limit to the default (60 seconds) resulted in a 2GB journal directory (similar to WiredTiger's). It appears that WiredTiger does not use this parameter to control how the journal directory is pruned when its the storage engine. Not clear which is the right model here - but clearly MMAPva and WitedTiger are different. |