From 6ff1c12835f3156a098a500bdfc31ddf1b8ca399 Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Mon, 27 Apr 2020 11:49:59 -0500 Subject: [PATCH] Update supported-stores.md --- nats-streaming-concepts/clustering/supported-stores.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nats-streaming-concepts/clustering/supported-stores.md b/nats-streaming-concepts/clustering/supported-stores.md index c1fc972..0841aac 100644 --- a/nats-streaming-concepts/clustering/supported-stores.md +++ b/nats-streaming-concepts/clustering/supported-stores.md @@ -2,10 +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 and messages to the storage you configure using the `--store` option. +The NATS Streaming Server 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`. **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. +- Each node in the cluster needs to have its own "database", that is, no two nodes should share the same tables.