Previously, active mgrs ended up waiting around
until the next periodic message. This is a lot
more noticeable now that the mgr isn't considered
active until it has loaded the digest data.
Signed-off-by: John Spray <john.spray@redhat.com>
pending_map.active_gid = 0;
pending_map.available = false;
pending_map.active_addr = entity_addr_t();
+
+ // So that when new active mgr subscribes to mgrdigest, it will
+ // get an immediate response instead of waiting for next timer
+ cancel_timer();
}
void MgrMonitor::drop_standby(uint64_t gid)