[SERVER-40108] Improve IndexCatalog::dropAllIndexes() error logging (prior to fassert'ing) to include nss, index specs and any min visible timestamps or drop timestamps Created: 13/Mar/19  Updated: 06/Dec/22  Resolved: 13/Mar/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Participants:

 Description   

Current logging:

...
...
[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.


Generated at Thu Feb 08 04:54:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.