Skip to content
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

add-note-for-sync-when-wal-expires #1831

Merged
merged 2 commits into from
Jan 5, 2023
Merged

add-note-for-sync-when-wal-expires #1831

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c3112b9
add-note-for-sync-when-wal-expires
abby-cyber Dec 27, 2022
60e572e
Update replication-between-clusters.md
abby-cyber Dec 28, 2022
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
5 changes: 5 additions & 0 deletions docs-2.0/synchronization-and-migration/replication-between-clusters.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,8 @@ The test environment for the operation example in this topic is as follows:

- On the primary and secondary cluster machines, modify `nebula-graphd.conf`, `nebula-metad.conf`, and `nebula-storaged.conf`. In all three files, set real IP addresses for `local_ip` instead of `127.0.0.1`, and set the IP addresses and ports for their own nebula-metad processes as the `meta_server_addrs` values. In `nebula-graphd.conf`, set `enable_authorize=true`.

- On the primary cluster, set `--snapshot_send_files=false` in both the `nebula-storaged.conf` file and the `nebula-metad.conf` file.

- On the Meta listener machine, modify `nebula-metad-listener.conf`. Set the IP addresses and ports of the **primary cluster's** nebula-metad processes for `meta_server_addrs`, and those of the listener process for `meta_sync_listener`.

- On the Storage listener machine, modify `nebula-storaged-listener.conf`. Set the IP addresses and ports of the **primary cluster's** nebula-metad processes for `meta_server_addrs`.
Expand Down Expand Up @@ -540,3 +542,6 @@ Fix the problems in the cluster, and then the synchronization will be automatica
You can run `SHOW SYNC STATUS` to check the status of the data sent by the primary cluster and run `SHOW DRAINER SYNC STATUS` to check the status of the data received by the secondary cluster. If all the data is sent successfully from the primary cluster and all the data is received successfully by the secondary cluster, the data synchronization is completed.


### My WAL log files has expired and will it affect the cluster synchronization?

Expired WAL files (beyond the time set by `--wal-ttl`) will cause unsynchronization of cluster data. You can manually add `--snapshot_send_files=false` to the configuration files of the Meta and Storage services to synchronize data. After updating the configuration files, you need to restart the services. For more information about the configuration files, see [Configuration Files](../5.configurations-and-logs/1.configurations/1.configurations.md).