canonical / dqlite

Embeddable, replicated and fault-tolerant SQL engine.
https://dqlite.io
Other
3.9k stars 219 forks source link

no known leader error forever #628

Closed koh-osug closed 8 months ago

koh-osug commented 8 months ago

I started 3 nodes and stopped them later. Now I'm starting again only the first node but it displays forever:

2024-03-09T20:45:25+01:00 | WARN | attempt 3630: server 127.0.0.1:10001: no known leader 2024-03-09T20:45:25+01:00 | WARN | attempt 3630: server 127.0.0.1:10003: dial: dial tcp 127.0.0.1:10003: connect: connection refused

How to restore the functionality of this single node again? Is this an error which will now be displayed forever or is the node even dysfunctional?

How can this automatically healed? When the other nodes are also starting again, will this be also automatically handled?