[SERVER-78542] Improve serverless lock logging Created: 29/Jun/23  Updated: 29/Oct/23  Resolved: 12/Jul/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Didier Nadeau Assignee: Didier Nadeau
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Serverless
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2023-07-10, Server Serverless 2023-07-24
Participants:

 Description   

In order to help users diagnose issues around serverless lock errors, we should log the following when failing to acquire the lock :

  • The type we're trying to acquire the lock for
  • The operationId we're trying to acquire the lock for
  • The type that already hold the lock
  • The list of operationIds that are already active

We should also improve the logging of TenantMigrationDonor to say "failed" rather than "Tenant Migration completed".



 Comments   
Comment by Githook User [ 12/Jul/23 ]

Author:

{'name': 'Didier Nadeau', 'email': 'didier.nadeau@mongodb.com', 'username': 'nadeaudi'}

Message: SERVER-78542 Improve serverless lock logging
Branch: master
https://github.com/mongodb/mongo/commit/f6844c908aa02afa1f1e75693464a07133120c2c

Generated at Thu Feb 08 06:38:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.