From ae9998c1f736f3391e302ecc9d92eab9f83a78c9 Mon Sep 17 00:00:00 2001 From: Ivan Kozlovic Date: Wed, 19 Feb 2020 14:50:05 -0700 Subject: [PATCH] Add note about MEM store and connection lost This is in relation to issue: https://github.com/nats-io/stan.java/issues/146 Signed-off-by: Ivan Kozlovic --- nats-streaming-server/configuring/persistence/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/nats-streaming-server/configuring/persistence/README.md b/nats-streaming-server/configuring/persistence/README.md index 68914b3..af08b72 100644 --- a/nats-streaming-server/configuring/persistence/README.md +++ b/nats-streaming-server/configuring/persistence/README.md @@ -1,6 +1,7 @@ # Persistence -By default, the NATS Streaming Server stores its state in memory, which means that if the streaming server is stopped, all state is lost. Still, this level of persistence allows applications to stop and later resume the stream of messages, and protect against applications disconnect \(network or applications crash\). +By default, the NATS Streaming Server stores its state in memory, which means that if the streaming server is stopped, all state is lost. On server restart, since no connection information is recovered, running applications will stop receiving messages and new published messages will be rejected with an `invalid publish request` error. Client libraries that support and set the `Connection Lost` handler \(refer to [this](https://github.com/nats-io/stan.go#connection-status) for more information\) will be notified that the connection is lost with the error `client has been replaced or is no longer registered`.
+Still, this level of persistence allows applications to stop and later resume the stream of messages, and protect against applications disconnect \(network or applications crash\). * [File Store](file_store.md) * [SQL Store ](sql_store.md)