Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-30947

checkOplogs function should dump more oplog entries on failure

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.4.16, 3.5.13
    • None
    • Replication
    • Fully Compatible
    • v3.4
    • Repl 2017-09-11, Repl 2017-10-02

    Description

      In replsettest.js, the checkOplogs function verifies that the oplogs of each node in a replica set match. If there is a discrepancy between two oplogs, it will currently print the last 10 oplog entries of each node to the logs. A test may execute hundreds or thousands of operations, and this amount (10 entries) is somewhat arbitrary and not always helpful when trying to debug a failure. We should consider increasing this amount significantly, to 100 entries or 1000, or possibly just dumping the entire oplog of each node. This is (hopefully) not a check that fails often, so when it does, it would be nice to have as much debugging information as possible. Dumping the entire oplog of each node to the logs could aid with this.

      Attachments

        Activity

          People

            katherine.walker@mongodb.com Katherine Walker (Inactive)
            william.schultz@mongodb.com William Schultz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: