Skip to content

Fix: Modify the recommended backup node #518

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.

Sign up for GitHub

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

Open
warku123 wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Fix: Modify the recommended backup node #518

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
78e72b7
Change description about Backup_configure
warku123 Nov 18, 2025
43029c7
Modify grammar
warku123 Nov 18, 2025
e6e4056
Spelling mistake
warku123 Nov 18, 2025
6400529
Modify number
warku123 Nov 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 8 additions & 24 deletions docs/using_javatron/installing_javatron.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,9 +101,9 @@ java -Xmx24g -XX:+UseConcMarkSweepGC -jar FullNode.jar --witness -c config.conf

### Master-Slave Mode for Block Production FullNodes

To enhance the reliability of block production FullNodes, you can deploy multiple block production FullNodes for the same account, forming a master-slave mode. When an account with block production rights deploys two or more nodes, it's necessary to configure `node.backup` in each node's configuration file. The description of `node.backup` configuration items is as follows:
To enhance the reliability of block production FullNodes, you can deploy multiple block production FullNodes for the same account, forming a master-slave mode. When an account with block production rights deploys two or more nodes **(Recommended number: 2)**, it's necessary to configure `node.backup` in each node's configuration file. The description of `node.backup` configuration items is as follows:

```
```ini
node.backup {
# udp listen port, each member should have the same configuration
port = 10001
Expand All @@ -114,14 +114,14 @@ node.backup {
# time interval to send keepAlive message, each member should have the same configuration unit: ms
keepAliveInterval = 3000

# peer's ip list, can't contain myself
# peers' IP list, must not include myself
members = [
# "ip",
# "ip"
]
}
```ini
For example, if an account with block production rights deploys three nodes with IPs 192.168.0.100, 192.168.0.101, and 192.168.0.102 respectively, their `node.backup` configurations should be as follows:
```
For example, if an account with block production rights deploys two nodes with IPs 192.168.0.100 and 192.168.0.101 respectively, their `node.backup` configurations should be as follows:

- Configuration for IP 192.168.0.100
```ini
Expand All @@ -130,36 +130,20 @@ node.backup {
priority = 8
keepAliveInterval = 3000
members = [
"192.168.0.101",
"192.168.0.102"
"192.168.0.101"
]
}
```

* Configuration for IP 192.168.0.101

```
```ini
node.backup {
port = 10001
priority = 7
keepAliveInterval = 3000
members = [
"192.168.0.100",
"192.168.0.102"
]
}
```

* Configuration for IP 192.168.0.102

```
node.backup {
port = 10001
priority = 6
keepAliveInterval = 3000
members = [
"192.168.0.100",
"192.168.0.101"
"192.168.0.100"
]
}
```
Expand Down