[jira] [Created] (CASSANDRA-17853) Sporadic CL switch from LOCAL_QUORUM to ALL

["Manjunath Angadi (Jira)" <ji...@apache.org>]

Manjunath Angadi created CASSANDRA-17853:
--------------------------------------------

             Summary: Sporadic CL switch from LOCAL_QUORUM to ALL
                 Key: CASSANDRA-17853
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17853
             Project: Cassandra
          Issue Type: Bug
            Reporter: Manjunath Angadi


Team - we see that the Consitency Level is changing to ALL, when there is a read timeout.

Used Cassandra session has next main properties:
 * Load balancing policy - DCAwareRoundRobinPolicy(localDc, usedHostPerRemoteDc = 3, allowRemoteDcForLocalConsistencyLevel = true)
 * Retry policy - DefaultRetryPolicy
 * Query options - QueryOptions with set consistency level to ConsistencyLevel.{*}LOCAL_QUORUM{*}

 

we have the table as defined below.
{code:java}
CREATE TABLE table_name (
    key text,
    column1 text,
    column2 text,
    value text,
    PRIMARY KEY (key, column1, column2)
) WITH COMPACT STORAGE
    AND CLUSTERING ORDER BY (column1 ASC, column2 ASC)
    AND bloom_filter_fp_chance = 0.1
    AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
    AND comment = ''
    AND compaction = {'class': 'org.apache.cassandra.db.compaction.LeveledCompactionStrategy', 'sstable_size_in_mb': '180'}
    AND compression = {'chunk_length_in_kb': '64', 'class': 'org.apache.cassandra.io.compress.SnappyCompressor'}
    AND crc_check_chance = 1.0
    AND dclocal_read_repair_chance = 0.0
    AND default_time_to_live = 0
    AND gc_grace_seconds = 864000
    AND max_index_interval = 2048
    AND memtable_flush_period_in_ms = 0
    AND min_index_interval = 128
    AND read_repair_chance = 0.0
    AND speculative_retry = '99PERCENTILE'; {code}
 

On Read Timeout, below exception is observed.
{code:java}
Caused by: com.datastax.driver.core.exceptions.ReadTimeoutException: Cassandra timeout during read query at consistency ALL (5 responses were required but only 4 replica responded)
    at com.datastax.driver.core.exceptions.ReadTimeoutException.copy(ReadTimeoutException.java:88) ~[cassandra-driver-core-3.1.4.jar!/:?]
    at com.datastax.driver.core.exceptions.ReadTimeoutException.copy(ReadTimeoutException.java:25) ~[cassandra-driver-core-3.1.4.jar!/:?]
    at com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:37) ~[cassandra-driver-core-3.1.4.jar!/:?]
    at com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:245) ~[cassandra-driver-core-3.1.4.jar!/:?]
    at com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:68) ~[cassandra-driver-core-3.1.4.jar!/:?] {code}
This could be an issue re-occurred in Cassandra 3.11.0, which is the version used currently.Also - this could be related to https://issues.apache.org/jira/browse/CASSANDRA-7868

Please provide your feedback on the same.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org