Collection drops are not replicated under protocol version 0

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.6.0, 3.6.9
    • Component/s: Replication
    • None
    • Replication
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Create a replica set on 3.6.9 and configure it to run protocol version 0, then create a collection and drop it. The mongod log on the secondaries show the following messages

      2019-01-18T13:11:36.368-0500 I COMMAND  [repl writer worker 0] CMD: drop test.c91
2019-01-18T13:11:36.368-0500 I STORAGE  [repl writer worker 0] dropCollection: test.c91 (230159df-a788-4c1c-a5bd-22161ea8a674) - renaming to drop-pending collection: test.system.drop.1547835095i373t-1.c91 with drop optime { ts: Timestamp(1547835095, 373), t: -1 }

      but there is no "completing collection drop" message, and the WT table is never dropped on the secondary.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Bruce Lucas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: