mirror of
https://github.com/scylladb/scylladb.git
synced 2026-06-05 06:23:03 +00:00
ad7423649f
1) Stick to the specific server in control connections. It could happen that, when starting a cluster and checking if a specific node is up, the check would actually execute against an already running node. Prevent this from happening by setting a white list connection balancing policy for control connections. 2) When checking if CQL is up, ignore timeout errors Scylla in debug mode can easily time out on a DDL query, and the timeout error at start up would lead to the entire cluster marked as broken. This is too harsh, allow timeouts at start. 3) No longer force schema migration when starting the server By default, Raft is on, so the nodes are getting schema through Raft leader. Schema migration significantly slows down cluster start in debug mode (60 seconds -> 100 seconds), and even though it was a great test that helped discover several bugs in Scylla, it shouldn't be part of normal cluster boot, so disable it.