taigrr/nats.docs
1
0
Fork 0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00
Code Issues Projects Releases Wiki Activity

Merge pull request #93 from nats-io/kozlovic-patch-1

Browse Source 
Note about SQL and clustering
This commit is contained in:
Ginger Collison 2020-04-27 11:50:47 -05:00 committed by GitHub
commit 5a57d4ddc5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
nats-streaming-concepts/clustering/supported-stores.md
View File

@ -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` 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 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`. 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 nodes should share the same tables.