Improve serverless lock logging

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Serverless
    • Fully Compatible
    • Server Serverless 2023-07-10, Server Serverless 2023-07-24
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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".

            Assignee:
            Didier Nadeau
            Reporter:
            Didier Nadeau
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: