[SERVER-55352] Missing uuid in collection info returned by TenantDatabaseCloner's listCollections command Created: 19/Mar/21  Updated: 29/Oct/23  Resolved: 27/May/21

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 5.0.0-rc1, 5.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: pm-1791_non-cloud-blocking, post-rc0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-56023 listCollections can return empty meta... Closed
is depended on by SERVER-52713 [testing] Add stepdown/kill/terminate... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0
Sprint: Repl 2021-05-03, Repl 2021-05-17, Repl 2021-05-31
Participants:

 Description   

Based on the EVG patch builds for SERVER-52713, the listCollections command run TenantDatabaseCloner sometimes can return collection info without uuid, causing the migration to abort with FailedToParse error.

buildscripts.resmokelib.errors.ServerFailure: Tenant migration with donor primary on port 20002 of replica set 'rs0' has aborted due to an error: {'state': 'aborted', 'abortReason': {'code': 9, 'codeName': 'FailedToParse', 'errmsg': 'Tenant migration recipient command failed :: caused by :: Collection info could not be parsed : { name: "fts_index3", type: "collection", options: {}, info: { readOnly: false }, idIndex: { v: 2, key: { _id: 1 }, name: "_id_" } } :: caused by :: BSON field \'TenantDatabaseCloner::listCollectionsStage.info.uuid\' is missing but a required field'}, 'ok': 1.0, '$clusterTime': {'clusterTime': Timestamp(1616068833, 18), '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(1616068833, 18)}.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 27/May/21 ]

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: SERVER-55352: Remove denylisted abort reasons from tenant migration hook

(cherry picked from commit a0c70edc5763449c4a02c846a4ef3af6d1d61936)
Branch: v5.0
https://github.com/mongodb/mongo/commit/9c07be3f6e61537c0da24279952660af8b197442

Comment by Githook User [ 27/May/21 ]

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: SERVER-55352: Remove denylisted abort reasons from tenant migration hook
Branch: master
https://github.com/mongodb/mongo/commit/a0c70edc5763449c4a02c846a4ef3af6d1d61936

Comment by Lingzhi Deng [ 28/Apr/21 ]

Once SERVER-56023 is fixed, this ticket will need to remove the TODO.

Comment by Lingzhi Deng [ 28/Apr/21 ]

I think this is the same as SERVER-56023

Generated at Thu Feb 08 05:36:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.