Description
This issue can occur when running an aggregation pipeline that uses the internal $exchange stage configured with key-range partitioning and order-preserving delivery. If a single key range produces enough documents to fill its exchange buffer (that is, many results are routed to the same consumer), the server reaches the code path where a full per-consumer buffer is detected but the internal "high watermark" for that key range is not updated as intended.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
MongoDB MongoDB Server
Default version status: unaffected
8.3.0 to < 8.3.3affected8.2.0 to < 8.2.10affected8.0.0 to < 8.0.24affected7.0.0 to < 7.0.35affected