Expand limit for rollback beyond existing 300mb

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Azat Khuzhin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: