Details
-
Task
-
Resolution: Won't Do
-
Major - P3
-
None
-
None
-
None
-
Storage Execution
Description
[ReplicaSetFixture:job9:secondary] 2019-01-16T20:03:29.431+0000 I REPL [replication-4] Completing collection drop for test.system.drop.1547668969i105t1.index_bigkeys_background_test with drop optime { ts: Timestamp(1547668969, 105), t: 1 } (notification optime: { ts: Timestamp(1547669004, 2), t: 2 })
|
[ReplicaSetFixture:job9:secondary] 2019-01-16T20:03:29.431+0000 I REPL [replication-7] Completing collection drop for test.system.drop.1547668969i105t1.index_bigkeys_background_test with drop optime { ts: Timestamp(1547668969, 105), t: 1 } (notification optime: { ts: Timestamp(1547669005, 1), t: 2 })
|
[ReplicaSetFixture:job9:secondary] 2019-01-16T20:03:29.431+0000 I REPL [replication-3] Completing collection drop for test.system.drop.1547668969i105t1.index_bigkeys_background_test with drop optime { ts: Timestamp(1547668969, 105), t: 1 } (notification optime: { ts: Timestamp(1547669004, 2), t: 2 })
|
[ReplicaSetFixture:job9:secondary] 2019-01-16T20:03:29.431+0000 I REPL [replication-5] Completing collection drop for test.system.drop.1547668969i105t1.index_bigkeys_background_test with drop optime { ts: Timestamp(1547668969, 105), t: 1 } (notification optime: { ts: Timestamp(1547669005, 2), t: 2 })
|
[ReplicaSetFixture:job9:secondary] 2019-01-16T20:03:29.431+0000 I REPL [replication-0] Completing collection drop for test.system.drop.1547668969i105t1.index_bigkeys_background_test with drop optime { ts: Timestamp(1547668969, 105), t: 1 } (notification optime: { ts: Timestamp(1547669004, 1), t: 2 })
|
[ReplicaSetFixture:job9:secondary] 2019-01-16T20:03:29.431+0000 I REPL [replication-2] Completing collection drop for test.system.drop.1547668969i105t1.index_bigkeys_background_test with drop optime { ts: Timestamp(1547668969, 105), t: 1 } (notification optime: { ts: Timestamp(1547669004, 1), t: 2 })
|
[ReplicaSetFixture:job9:secondary] 2019-01-16T20:03:29.431+0000 I REPL [replication-1] Completing collection drop for test.system.drop.1547668969i105t1.index_bigkeys_background_test with drop optime { ts: Timestamp(1547668969, 105), t: 1 } (notification optime: { ts: Timestamp(1547669004, 2), t: 2 })
|
[ReplicaSetFixture:job9:secondary] 2019-01-16T20:03:29.434+0000 I REPL [replication-6] Completing collection drop for test.system.drop.1547668969i105t1.index_bigkeys_background_test with drop optime { ts: Timestamp(1547668969, 105), t: 1 } (notification optime: { ts: Timestamp(1547669005, 1), t: 2 })
|
Replication has many threads that run the code that notifies the drop-pending-reaper of work and executes that work synchronously. And the drop-pending-reaper does not prevent multiple callers from running drop collection for the same collection: it is a race between whether the first caller finishes the drop collection and deletes entries from the reaper's map before the next caller redundantly accesses the map to find drops to execute.
Attachments
Issue Links
- related to
-
SERVER-39235 Support SE-based 2-phase drop for SE's not supporting recoveryToTimestamp
-
- Closed
-