Skip to content

[release/v26.0] [DB-2199] Fix write timeout regressions introduced with multi-stream appends - #5702

Draft
shaan1337 wants to merge 1 commit into
release/v26.0from
shaan1337/fix-write-timeout-msa-bugs-v26.0
Draft

[release/v26.0] [DB-2199] Fix write timeout regressions introduced with multi-stream appends#5702
shaan1337 wants to merge 1 commit into
release/v26.0from
shaan1337/fix-write-timeout-msa-bugs-v26.0

Conversation

@shaan1337

Copy link
Copy Markdown
Member

Manually cherry picked from #5699
(only tests had merge conflicts)

The failure constructor of `WriteEventsCompleted` leaves `FirstEventNumbers`
and `LastEventNumbers` empty, so `LowAllocReadOnlyMemory<T>.Single` throws
when the write result is not `Success`. Two write completion callbacks read
them unconditionally, and the throw happens before the failure handling runs.

- `CoreProjectionCheckpointWriter`: a failed checkpoint write is neither
  retried nor reported as a projection failure. The projection stops
  processing events and just sits at `Writing (N)` until the node or
  the projection subsystem is restarted.

- `PersistentSubscriptionMessageParker`: a failed park write is not retried
  and the event is silently lost - neither delivered, nor retried, nor
  written to the parked stream. The consumer's in-flight slot is leaked too,
  so enough failed parks and the connection stops receiving messages.

Guard both reads on `OperationResult.Success` and add a test for each.
@linear-code

linear-code Bot commented Aug 5, 2026

Copy link
Copy Markdown

DB-2199

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant