[SERVER-5929] Expand limit for rollback beyond existing 300mb Created: 25/May/12  Updated: 06/Dec/22  Resolved: 21/Apr/16

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

Type: Improvement Priority: Major - P3
Reporter: Azat Khuzhin Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-23392 Increase Replication Rollback (Data) ... Closed
Assigned Teams:
Replication
Participants:

 Description   

I think that this 300mb limit must be calculating using such things as
"syncdelay" mongod option, and sysctl "vm.dirty_expire_centisecs" - flushing parameters.
And also can be set using config directive.

In my case his 300mb limit probably not enough, because I use
"syncdelay=180" and "vm.dirty_expire_centisecs=12000"

See
https://groups.google.com/d/msg/mongodb-user/SZe0nCBCR80/n5aDQ2wb_6MJ



 Comments   
Comment by Eric Milkie [ 21/Apr/16 ]

SERVER-23392

Generated at Thu Feb 08 03:10:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.