>> My question is: Is there a way to force the snapshot creation / sync
from the leader?
3.5.6 will automatically create a clean snapshot as part of server start up
process. So a snapshot should be available after initial upgrade and there
is no need to force a snapshot creation.
On Mon, Dec 9, 2
Hi,
I am working on upgrading a Kubernetes based 3.4.14 cluster to 3.5.6.
I are hitting the issue where the new snapshot checks prevent the newly
upgraded 3.5.6 cluster from starting. This usually happens in our test
set-up as the 3.4.14 cluster is not very old and has not hit the snapCount
limit
