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

Improve logging for 'monitor_replication_lag_thread' when 'Seconds_Behind_Master' is NULL #3288

Closed
2 tasks done
JavierJF opened this issue Feb 4, 2021 · 0 comments
Closed
2 tasks done

Comments

@JavierJF
Copy link
Collaborator

JavierJF commented Feb 4, 2021

  • A clear description of the issue

Right now if 'Seconds_Behind_Master' is detected to be NULL for a replica, nothing is logged in the error log. This should be corrected, for now on ProxySQL should report an error if 'Seconds_Behind_Master' is detected to be NULL for a server.

  • ProxySQL version

  • v2.0.17

  • v2.1.1

JavierJF added a commit that referenced this issue Feb 4, 2021
… to reflect when 'Seconds_Behind_Master' is NULL
JavierJF added a commit that referenced this issue Feb 4, 2021
… to reflect when 'Seconds_Behind_Master' is NULL
JavierJF added a commit that referenced this issue Feb 4, 2021
… to reflect when 'Seconds_Behind_Master' is NULL
renecannao added a commit that referenced this issue Feb 5, 2021
Closes #3288: Added extra logging to 'monitor_replication_lag_thread' when 'Seconds_Behind_Master' is NULL
renecannao added a commit that referenced this issue Feb 5, 2021
Closes #3288: Added extra logging to 'monitor_replication_lag_thread' when 'Seconds_Behind_Master' is NULL
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants