Avoid obscuring network errors in OplogFetcher

XMLWordPrintableJSON

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

      InĀ  OplogFetcher::_checkTooStaleToSyncFromSource, all raised execptions in this try/catch block are treated as treated as "too stale to sync from source" errors, even network errors, leading to the stall seen in HELP-83793. Instead, we should likely both log the error message itself and return ErrorCodes::OplogStartMissing, as we do at the end of the function.

            Assignee:
            Unassigned
            Reporter:
            Joseph Obaraye
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: