You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the problem: Dendrite stops processing events if nats is restarted.
Who is affected: Everybody
How is this bug manifesting: Restart the entire nats cluster in a non-rolling fashion. This will trigger a nats: Server Shutdown error which exits the JetStreamConsumers, but leaves the rest of the system running. Only remediation seems to be to restart the server.
When did this first appear:
Steps to reproduce
Start Dendrite
Kill all nats servers simultaneously
Messages are no longer processed
Ideally Dendrite would reconnect once nats is available again. Alternatively the service should exit, or at the very list trigger a signal somewhere that streams are no longer being processed.
The text was updated successfully, but these errors were encountered:
S7evinK
added
the
T-Defect
Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
label
Aug 28, 2023
Background information
go version
: 1.19.7Description
nats: Server Shutdown
error which exits the JetStreamConsumers, but leaves the rest of the system running. Only remediation seems to be to restart the server.Steps to reproduce
Ideally Dendrite would reconnect once nats is available again. Alternatively the service should exit, or at the very list trigger a signal somewhere that streams are no longer being processed.
The text was updated successfully, but these errors were encountered: