[SERVER-20600] the flush of journal log on WiredTiger Created: 24/Sep/15 Updated: 24/Sep/15 Resolved: 24/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Edision chow | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
In MMAP the journal flush every 100ms by default. What`s the Principle of journal log flush in WiredTiger,And journal log flush every 100ms? Thanks |
| Comments |
| Comment by Ramon Fernandez Marina [ 24/Sep/15 ] |
|
eshujiushiwo, please note that the 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, where your question will reach a larger audience. In the future, questions like this one which may involve more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources. Regards, |
| Comment by Michael Cahill (Inactive) [ 24/Sep/15 ] |
|
eshujiushiwo, in WiredTiger, the journal is flushed by "j:true" updates, or when a journal file becomes full (every 100MB of data written), or by checkpoints (which are triggered every 60s by default). |