Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit160ebf0

Browse files
committed
excluding
1 parenta2ea334 commit160ebf0

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

‎doc/administration.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -239,7 +239,15 @@ Suppose we have working cluster of three nodes (```node1```, ```node2```, ```nod
239239
240240
## Excluding nodes from cluster
241241
242+
Generally it is okay to just shutdown cluster node but all transaction in cluster will be freezed while other nodes will detect that node is gone (this period is controlled by the ```multimaster.heartbeat_recv_timeout``` parameter). To avoid such situation it is possible to exclude node from cluster in advance.
242243
244+
For example to stop node 3 run on any other node:
245+
246+
```
247+
select mtm.stop_node(3);
248+
```
249+
250+
This will disable node 3 on all cluster nodes.
243251
244252
245253

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp