Make blocking callbacks in migrationConflictHandler async

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      To provide a futurized replacement for migrationConflictHandler, we need to replace the following blocking callbacks with non-blocking counterparts:

      • checkIfCanReadOrBlock(opCtx, dbName)
      • checkIfCanWriteOrBlock(opCtx)

      The non-blocking counterparts will return Future<void> as the return value.

            Assignee:
            Amirsaman Memaripour
            Reporter:
            Amirsaman Memaripour
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: