-
Notifications
You must be signed in to change notification settings - Fork 43
Database hot standby #4436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Database hot standby #4436
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
15 changes: 15 additions & 0 deletions
15
doc/code_snippets/snippets/config/instances.enabled/hot_standby_1/config.yaml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
groups: | ||
group001: | ||
replicasets: | ||
replicaset001: | ||
instances: | ||
instance001: | ||
database: | ||
hot_standby: true | ||
wal: | ||
dir: /tmp/wals | ||
snapshot: | ||
dir: /tmp/snapshots | ||
iproto: | ||
listen: | ||
- uri: '127.0.0.1:3301' |
1 change: 1 addition & 0 deletions
1
doc/code_snippets/snippets/config/instances.enabled/hot_standby_1/instances.yml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
instance001: |
15 changes: 15 additions & 0 deletions
15
doc/code_snippets/snippets/config/instances.enabled/hot_standby_2/config.yaml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
groups: | ||
group001: | ||
replicasets: | ||
replicaset001: | ||
instances: | ||
instance001: | ||
database: | ||
hot_standby: true | ||
wal: | ||
dir: /tmp/wals | ||
snapshot: | ||
dir: /tmp/snapshots | ||
iproto: | ||
listen: | ||
- uri: '127.0.0.1:3301' |
1 change: 1 addition & 0 deletions
1
doc/code_snippets/snippets/config/instances.enabled/hot_standby_2/instances.yml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
instance001: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1428,6 +1428,40 @@ The ``database`` section defines database-specific configuration parameters, suc | |
|
||
.. confval:: database.hot_standby | ||
|
||
Whether to start the server in the hot standby mode. | ||
This mode can be used to provide failover without :ref:`replication <replication>`. | ||
|
||
Suppose there are two cluster applications. | ||
Each cluster has one instance with the same configuration: | ||
|
||
.. literalinclude:: /code_snippets/snippets/config/instances.enabled/hot_standby_1/config.yaml | ||
:language: yaml | ||
:dedent: | ||
|
||
In particular, both instances use the same directory for storing write-ahead logs and snapshots. | ||
|
||
When you start both cluster applications on the same machine, the instance from the first one will be the primary instance and the second will be the standby instance. | ||
In the :ref:`logs <configuration_reference_log>` of the second cluster instance, you should see a notification: | ||
|
||
.. code-block:: text | ||
|
||
main/104/interactive I> Entering hot standby mode | ||
|
||
This means that the standby instance is ready to take over if the primary instance goes down. | ||
The standby instance initializes and tries to take a lock on a directory for storing write-ahead logs | ||
but fails because the primary instance has made a lock on this directory. | ||
|
||
If the primary instance goes down for any reason, the lock is released. | ||
In this case, the standby instance succeeds in taking the lock and becomes the primary instance. | ||
|
||
``database.hot_standby`` has no effect: | ||
|
||
* If :ref:`wal.mode <configuration_reference_wal_mode>` is set to ``none``. | ||
* If :ref:`wal.dir_rescan_delay <configuration_reference_wal_dir_rescan_delay>` is set to a large value on macOS or FreeBSD. On these platforms, the hot standby mode is designed so that the loop repeats every ``wal.dir_rescan_delay`` seconds. | ||
* If spaces are created with :ref:`engine <space_opts_engine>` set to ``vinyl``. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The old wording was clearer: Now it's ambiguous:
|
||
|
||
Examples on GitHub: `hot_standby_1 <https://github.com/tarantool/doc/tree/latest/doc/code_snippets/snippets/config/instances.enabled/hot_standby_1>`_, `hot_standby_2 <https://github.com/tarantool/doc/tree/latest/doc/code_snippets/snippets/config/instances.enabled/hot_standby_2>`_ | ||
|
||
| | ||
| Type: boolean | ||
| Default: false | ||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't guess from this example the correct way to use this mode in multi-instance apps. Set it for all instances of two identical apps? Or maybe select a subset of instances to run in standby?
Not sure though if the deeper explanation is needed in the reference. Perhaps somewhere in a task-oriented page in the admin's guide (out of this PR's scope).
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The correct way is using
two cluster applications
witheach cluster having one instance
. And the GitHub examples at the end should help a reader. I agree that we can document this feature better. But, honestly, I don't think it is a very popular use case for Tarantool (maybe, I'm wrong).This sounds like a feature request for a new configuration approach. For example, we can allow a user to add two instances, set
replication.failover
to smth likehot_standby
, and provide the same path to WALs/snapshots for both instances. But still not sure that this scenario might be popular. cc @Totktonada