Closed smolkaj closed 2 years ago
AFAICT, the more sensible thing to do is to remove tuples when a controller disconnects, as it allows the controller to reconnect without a new election ID.
Are there any advantages to not allowing reuse of the same tuple in the above fashion?
@rhalstea pointed out the following related ambiguity in the spec:
Quick recap of our discussion during the P4 API WG meeting:
Use cases for reusing an election ID:
There were no concrete concerns around reusing the maximum election ID, as long as we keep ensuring uniqueness.
The next step here is for us to make a concrete proposal on how to clarify the spec.
Should we close this issue now?
Yes. The merged PR should resolve this.
The specification currently says:
But how is the set X of 3-tuples determined? It is clear that we add a tuple to X whenever a master arbitration succeeds. Do we also remove tuples from X when the controller owning the tuple disconnects?
@jonathan-dilorenzo @zhenk14 for visibility.