SERVER-138726ClosedWorks as Designed
Duplicate reshardCollection change events emitted when a reshard commit is retried
A single reshard operation can emit *two* {{reshardCollection}} change events (i.e., the completion noop oplog entry is written twice to the same shard). This is user-visible: a client consuming change streams receives the event twice for one reshard. It was observed in CI on the change-streams sharding FSM suites (3 failures in ~35 runs on the all-feature-flags variants, tracked in BF-47107) and reproduced deterministically with a diagnostic failpoint. I spoke with , who is of the opinion th