SERVER-135372ClosedFixed

Flush per-batch multikey catalog writes in the pipelined oplog applier before publishing lastApplied

When a worker applies an oplog entry that turns an index multikey, the catalog write is deferred until just before the batch is completed. It must commit at the *earliest* timestamp that index became multikey in the batch, strictly below the stable timestamp, before lastApplied advances past the batch. This ticket adds the per-batch multikey accumulator to the POA component, and flushes the multikey writes in the advancer before publishing lastApplied. Multikey path tracking on workers threads

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix
9.1.0-rc09.1.0-rc1025
Components
Server components related to this issue

No components specified.

Labels
Tags and classification

No labels assigned.