Skip to content

Add HA query SHOW REPLICATION LAG #1357

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

Merged
merged 3 commits into from
Aug 21, 2025
Merged

Add HA query SHOW REPLICATION LAG #1357

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f8f9e0f
Add replication lag
as51340 Aug 14, 2025
ab20a4e
Merge branch 'memgraph-3-5' into add-repl-lag
matea16 Aug 21, 2025
a309f25
Merge branch 'memgraph-3-5' into add-repl-lag
matea16 Aug 21, 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
11 changes: 10 additions & 1 deletion pages/clustering/high-availability.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -295,7 +295,6 @@ e.g during a maintenance work on the instance where the current main is deployed
</Callout>



### Unregister instance

There are various reasons which could lead to the decision that an instance needs to be removed from the cluster. The hardware can be broken,
Expand Down Expand Up @@ -366,6 +365,16 @@ This query will return the information about:

If the query `ADD COORDINATOR` wasn't run for the current instance, the value of the bolt server will be "".

### Show replication lag

The user can find the current replication lag on each instance by running `SHOW REPLICATION LAG` on the cluster's leader. The replication lag is expressed with
the number of committed transactions. Such an info is made durable through snapshots and WALs so restarts won't cause the information loss. The information
about the replication lag can be useful when manually performing a failover to check whether there is a risk of a data loss.

```plaintext
SHOW REPLICATION LAG;
```


## Setting config for highly-available cluster

Expand Down