From 4807c129765a3e9692af4b88376ac739fc7a9f53 Mon Sep 17 00:00:00 2001 From: Ivan Kozlovic Date: Thu, 23 Apr 2020 13:31:36 -0600 Subject: [PATCH] Note about SQL and clustering Should mention that each node in the cluster needs to point to their own tables. Resolves https://github.com/nats-io/nats-streaming-server/issues/1038 --- nats-streaming-concepts/clustering/supported-stores.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/nats-streaming-concepts/clustering/supported-stores.md b/nats-streaming-concepts/clustering/supported-stores.md index 88eaef6..c1fc972 100644 --- a/nats-streaming-concepts/clustering/supported-stores.md +++ b/nats-streaming-concepts/clustering/supported-stores.md @@ -2,9 +2,10 @@ In order to run NATS Streaming Server in clustered mode, you need to specify a persistent store. At this time you have the choice between `FILE` and `SQL` -The NATS Streaming stores server meta information, messages and subscriptions to the storage you configure using the `--store` option. +The NATS Streaming stores server meta information and messages to the storage you configure using the `--store` option. However, in clustered mode, we use RAFT for leader election. The raft layer uses its own stores which are currently necessarily file based. The location of the RAFT stores defaults to the current directory under a sub-directory named after the cluster ID, or you can configure it using `--cluster_log_path`. -This means that even if you select a SQL Store, there will still be a need for storing data on the file system. - +**Important if using a SQL Store:** +- There is still a need for storing RAFT data on the file system. +- Each node in the cluster needs to have its own "database", that is, no two node should share the same tables.