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

Update recipientForgetMigration error handling logic to properly handle CallbackCanceled

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.0.0-rc0, 6.3.2
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v6.3
    • Server Serverless 2023-02-20, Server Serverless 2023-03-06
    • 7

      the recipientSyncData command currently has logic for converting a CallbackCanceled error code into a retryable error. recipientForgetMigration does not currently do the same conversion: https://github.com/10gen/mongo/blob/1049af0cf89571f65cf9a22dfe75119b9059d785/src/mongo/db/repl/tenant_migration_recipient_service.cpp#L3279-L3286

      we should update this code to ensure that callers can retry in the event of a CallbackCanceled, since in the case when during a failover, a PrimaryOnlyService's scoped task executor rejects a task (instead of seeing an interrupted OperationContext), we would see kExecutorShutdownStatus propagated down the future chain.

            Assignee:
            christopher.caplinger@mongodb.com Christopher Caplinger
            Reporter:
            christopher.caplinger@mongodb.com Christopher Caplinger
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: