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

Add a flag to CheckMetadataConsistency for a more aggresive locking behavior

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Catalog and Routing
    • 1

      In some scenarios with a lot of concurrent DDL we want to ensure checkMetadataConsistency eventually gets the lock in order to do the checks. For this, we propose to add a new flag (it could be called something like forceMetadataLockAfterBackoff) that will aggresively grab the lock if it is unable to grab it after some some time.

      Also as part of this ticket, we should change how the ddl lock manager is using the backoff strategy, it should by default give up if it doesn't manage to grab the lock, and, if specified, instead of giving up, forcefully grabbing it, like it is working today.

            Assignee:
            Unassigned Unassigned
            Reporter:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: