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.

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

Need Of a replication lag Metric #2021

Closed
akhtar-a opened this issue Sep 9, 2024 · 0 comments · Fixed by #2026
Closed

Need Of a replication lag Metric #2021

akhtar-a opened this issue Sep 9, 2024 · 0 comments · Fixed by #2026
Assignees
Labels
enhancement New feature or request

Comments

@akhtar-a
Copy link

akhtar-a commented Sep 9, 2024

What happened
In a master slave configuration, where we have a master node and many followers nodes, a continuous asynchronous replication is happening between the the primary node to the secondary/replica node. There could be a chances where there is a signification lag in the replication.
What you expected to happen
In order to efficiently monitor the replication lag, there is a need to have a metric which accounts for the replication lag between the primary and the followers. Replication lag metic can be used for monitoring and alerting in case of the lag increase a certain threshold which will be useful in a cluster architecture.
How to reproduce it (as minimally and precisely as possible)
Create a primary-slave configuration.
Environment

# run "immu* version" and copy/paste the output here

Additional info (any other context about the problem)

@akhtar-a akhtar-a added the bug Something isn't working label Sep 9, 2024
@ostafen ostafen added enhancement New feature or request and removed bug Something isn't working labels Sep 16, 2024
@ostafen ostafen self-assigned this Sep 19, 2024
@ostafen ostafen linked a pull request Sep 19, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants