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

Logging changes for FCBIS initial syncs

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • ALL

      It looks like we are seeing issues with how the failed attempts for FCBIS initial syncs are being tracked. The expectation is that an initial sync will generate a unique ID and then generate logs for each attempt made, failed or successful.

      The successful attempt will have the total failed sync attempts, and we can get the failure rate by looking at the failed attempts in the successful log against the total count of that unique sync ID in our logs.

      For FCBIS, we are seeing multiple instances where the successful attempt will indicate that there were multiple failed attempts, but there are not enough logs in our data to correspond to those failures. You can see the issue for our sync ID 630cfaec0fc33c767db4a539 , which has 6 failed attempts but only 5 logs in our system. This export has the metadata if you'd like to review.

      I want to confirm either if this is expected behavior for FCBIS (the other methods do not have this issue) or if it is an issue that should be fixed. Thanks for the help!

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            mike.schoppmann@mongodb.com Mike Schoppmann
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: