You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case of redeployments into Kubernetes the pod gets a signal to shut down, then new pods are created doubling the cluster size.
In this situation, the pods shutting down should block their voting mechanism to allow the cluster to converge quicker.
The text was updated successfully, but these errors were encountered:
…ubernetes to perform a graceful shutdown. As a result, the pods shutting down will not vote. Closes Raft - Block voting when node shutdown #18
Better usage of IPMessageEndpoint, so that it does not starve the SWIM messages in case the Raft leader cannot receive a response from its followers.
Sample has an example for a distributed counter with exposed API
Multi-targeting enabled to take some improvements in the .net6 UDP client
Signed-off-by: Tomasz Maruszak <maruszaktomasz@gmail.com>
…ubernetes to perform a graceful shutdown. As a result, the pods shutting down will not vote. Closes Raft - Block voting when node shutdown #18
Better usage of IPMessageEndpoint, so that it does not starve the SWIM messages in case the Raft leader cannot receive a response from its followers.
Sample has an example for a distributed counter with exposed API
Multi-targeting enabled to take some improvements in the .net6 UDP client
Signed-off-by: Tomasz Maruszak <maruszaktomasz@gmail.com>
In case of redeployments into Kubernetes the pod gets a signal to shut down, then new pods are created doubling the cluster size.
In this situation, the pods shutting down should block their voting mechanism to allow the cluster to converge quicker.
The text was updated successfully, but these errors were encountered: