On 7/21/22 4:08 PM, manish khandelwal wrote:
Consistency can also be set on a statement basis. So please check in your code that you might be setting consistency 'ALL' for some queries.On Thu, Jul 21, 2022 at 7:23 PM pwozniak <pwozn...@man.poznan.pl <mailto:pwozn...@man.poznan.pl>> wrote:Hi, we have the following code (java driver): cluster =Cluster.builder().addContactPoints(contactPoints).withPort(port) .withProtocolVersion(ProtocolVersion.V3) .withQueryOptions(new QueryOptions() .setConsistencyLevel(ConsistencyLevel.QUORUM)) .withTimestampGenerator(new AtomicMonotonicTimestampGenerator()) .withCredentials(userName, password).build(); session =cluster.connect(keyspaceName); where ConsistencyLevel.QUORUM is our default consistency level. But we keep receiving the following exceptions: com.datastax.driver.core.exceptions.ReadTimeoutException: Cassandra timeout during read query at consistency ALL (3 responses were required but only 2 replica responded) Why the consistency level is ALL in there? Availability of our cluster is reduced because of that. We verified all our source code and haven't found places where ALL is set. We also did heap dump and found only ConsistencyLevel.QUORUM there. Regards, Pawel
smime.p7s
Description: S/MIME Cryptographic Signature
