[ https://issues.apache.org/jira/browse/CASSANDRA-17226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francisco Guerrero updated CASSANDRA-17226: ------------------------------------------- Change Category: Performance Complexity: Normal Component/s: Local/Startup and Shutdown Status: Open (was: Triage Needed) > Consistency Level Considered Connectivity Checker > ------------------------------------------------- > > Key: CASSANDRA-17226 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17226 > Project: Cassandra > Issue Type: Improvement > Components: Local/Startup and Shutdown > Reporter: Francisco Guerrero > Assignee: Francisco Guerrero > Priority: Normal > > The connectivity checker runs during the startup of Cassandra, more > specifically right after {{CassandraDaemon#setup}}. In general, it blocks for > a certain period of time in order to establish connections with the peers in > the cluster. The blocking is a best-effort one, meaning that the checker > allows Cassandra to continue booting even if the criteria is not met. > The Consistency Level Considered Connectivity Checker prioritizes the peers > to connect, while still satisfying the desired Consistency Level. The goal of > the new connectivity checker is to solve the read unavailable/timeout. -- This message was sent by Atlassian Jira (v8.20.1#820001) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org