raftlease.Store.Refresh is a no-op

Bug #1814735 reported by John A Meinel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

Currently the raft lease engine ignores requests to Refresh the state. However, we know that the FSM can be locally out of sync with the master. We could change Store.Refresh() to be a wait-until-next-appendEntries call, so that we know that any recent changes on primayr have been acknowledged.
It isn't a pure sync, but it does handle the case that 1-of-3 replicas is slightly behind, and gets a request that it thinks it can handle, but gets denied by the primary.

The code was already written such that it would reread from Mongo when it saw the chance for stale information, we're just using the same synchronization points when we think we see stale information from the FSM as well.

John A Meinel (jameinel)
tags: added: leadership
removed: leade
description: updated
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Medium → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.