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
@ashtonian Thanks. I can't remember seing that last error line, will investigate.
Clearly, your cluster is out of sync since it does empty synchronization (certain batches, like 566, are always repeating).
States like that are introduced by cluster joins with non-empty histories. It's not clear what exact version you use; newer releases have mitigated some of the effects. The latest release has a configurable setting to completely prevent non-empty SWC nodes to join a cluster.
The only quick and clear procedure to resolve this is unfortunately a full reset of the cluster, ie. scaling down to 0 and up again. (be aware this might loose state in the cluster).
👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
👉 Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.
Environment
Current Behavior
Cluster seems unstable and seems to be unable to sync.
Expected behaviour
No crash report
Configuration, logs, error output, etc.
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: