1
82%
main: 82%

Ran 04 Nov 2024 05:41AM UTC

Files 57

Run time 3s

Badge

Embed ▾

Committed 01 Nov 2024 03:19PM UTC coverage: 85.426% (-0.009%) from 85.435%

Job # 11658207804.1

Build Type

push

github

Committed by

web-flow

Commit Message

[FIXED] Handle recreating file-based stream to be memory on meta recovery (#6069)

For the following scenario:
1. create file-based R3 stream
2. delete stream
3. create memory-based R3 stream
4. add a consumer

The call to `js.processStreamAssignment(sa)` even while we're recovering
would mean that on meta recovery we'd first create the file-based
stream, then create the memory-based stream and fail to do so since we
can't change storage types. Which then leaves us stranded with 2 nodes
having a memory-based stream, and that one node with a file-based
stream.

This change proposes to have the stream additions be consistent with the
other collecting of state into `ru *recoveryUpdates` before applying,
and waiting until recovery is finished to do so.

Signed-off-by: Maurice van Veen <github@mauricevanveen.com>
Co-authored-by: Neil Twigg <neil@nats.io>

Coverage Stats

67566 of 79093 relevant lines covered (85.43%)

923785.8 hits per line

nats-io / nats-server / 11658207804 / 1
82%
main: 82%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 11658207804.1

nats-io / nats-server / 11658207804 / 1 82% main: 82%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 11658207804.1

nats-io / nats-server / 11658207804 / 1
82%
main: 82%

README BADGES
x