Introduced new HG attribute 'monitor_slave_lag_when_null' which takes precedence over 'mysql_thread_monitor_slave_lag_when_null' #4528
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduced a new hostgroup attribute 'monitor_slave_lag_when_null' in 'mysql_hostgroup_attibutes->hostgroup_settings', which takes precedence over 'mysql_thread_monitor_slave_lag_when_null' if both are configured.
Example usage:
INSERT INTO mysql_hostgroup_attributes (hostgroup_id, hostgroup_settings) VALUES (1, '{"monitor_slave_lag_when_null": 100}');
Note:
* Permitted values for 'mysql-monitor_slave_lag_when_null' also apply to the 'monitor_slave_lag_when_null' attribute.
* If 'Seconds_Behind_Master' is negative, it will bring previously shunned server, due to replication lag, back online.
* True 'Seconds_Behind_Master' values returned by the server will be logged in 'mysql_server_replication_lag_log table. (Previously negative values were logged as null)
Closes #4521