-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
Labels:None
-
Storage Execution
... ... [ReplicaSetFixture:job9:secondary] 2019-01-16T20:03:29.419+0000 I REPL [replication-0] Completing collection drop for test.system.drop.1547668969i94t1.index_bigkeys_background_test with drop optime { ts: Timestamp(1547668969, 94), t: 1 } (notification optime: { ts: Timestamp(1547669004, 1), 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.434+0000 E INDEX [replication-0] About to fassert - numIndexesTotal(): 0 numSystemIndexesEntries: 1 _readyIndexes.size(): 0 indexNamesToDrop: 1 haveIdIndex: 0 [ReplicaSetFixture:job9:secondary] 2019-01-16T20:03:29.434+0000 F - [replication-0] Fatal Assertion 17328 at src/mongo/db/catalog/index_catalog_impl.cpp 810 [ReplicaSetFixture:job9:secondary] 2019-01-16T20:03:29.434+0000 F - [replication-0] [ReplicaSetFixture:job9:secondary] [ReplicaSetFixture:job9:secondary] ***aborting after fassert() failure [ReplicaSetFixture:job9:secondary] [ReplicaSetFixture:job9:secondary]
NamespaceString can currently only be inferred from prior logging, if it exists.
Index specs would be helpful in order to be able to track logging about the particular index causing the problem.
And since this failure pertains to two-phase collection drop in the repl layer, min visible timestamps on the collection and/or index entries could be helpful.