Fix AWS Aurora replicas not being SHUNNED due to replication lag

Since the same 'AWS_Aurora_status_entry' index was being used for
computing the previous and current statuses, no difference was being
found, and no action taken.
v2.x-aurora_autodiscovery_shunned_promotion
Javier Jaramago Fernández 3 years ago
parent 9e3ab519e8
commit 4524bcba6c

@ -6493,7 +6493,7 @@ void MySQL_Monitor::evaluate_aws_aurora_results(unsigned int wHG, unsigned int r
if (strcmp(prev_hse->server_id,hse->server_id)==0) {
bool prev_enabled = true;
unsigned int prev_lag_ms = estimate_lag(hse->server_id, lasts_ase, ase_idx, add_lag_ms, min_lag_ms, lag_num_checks);
unsigned int prev_lag_ms = estimate_lag(hse->server_id, lasts_ase, prev_ase_idx, add_lag_ms, min_lag_ms, lag_num_checks);
if (prev_lag_ms > max_latency_ms) {
prev_enabled = false;
}

Loading…
Cancel
Save