This ticket is a workaround for SERVER-90023. To summarize, some catalog events in a sharded cluster might get identical resume tokens and therefore might get "skipped" when resuming from the previous event. The fix affects only the test code.
- is related to
-
SERVER-90023 dropIndexes events do not have total ordering in change streams
- Backlog