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

Donor's listDatabases response missing operationTime

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.9
    • Sprint:
      Sharding 2021-05-03, Sharding 2021-05-17
    • Linked BF Score:
      53

      Description

      The recipient's tenant all databases cloner uses the operationTime in the listDatabases response as the afterClusterTime to wait for the listDatabases result to be majority committed on the donor. But if the listDatabases response doesn't contain an operationTime. The afterClusterTime would be null and the migration would fail with "afterClusterTime cannot be a null timestamp".

      buildscripts.resmokelib.errors.ServerFailure: Tenant migration 'b7b18b5e-2986-44d1-93dc-05e1171fee1d' with donor replica set 'rs0' aborted due to an error: {'state': 'aborted', 'abortReason': {'code': 72, 'codeName': 'InvalidOptions', 'errmsg': 'Tenant migration recipient command failed :: caused by :: TenantAllDatabaseCloner failed to get listDatabases result majority-committed :: caused by :: afterClusterTime cannot be a null timestamp'}, 'ok': 1.0, '$clusterTime': {'clusterTime': Timestamp(1619673554, 10), 'signature': {'hash': b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00', 'keyId': 0}}, 'operationTime': Timestamp(1619673554, 10)}
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jack.mulrow Jack Mulrow
              Reporter:
              lingzhi.deng Lingzhi Deng
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: