multikey index ops in a transaction can cause secondaries to hang

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 4.1.5
    • Component/s: Replication
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      If a replication batch has an operation that causes the setIndexIsMultikey to get triggered, it can block indefinitely trying to acquire the database X lock if a prepared transaction is holding on it.

            Assignee:
            Siyuan Zhou
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: