[
https://issues.apache.org/jira/browse/CASSANDRA-20049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895461#comment-17895461
]
Cameron Zemek commented on CASSANDRA-20049:
-------------------------------------------
[~brandon.williams] thanks. Yes this resolves the issue. I wasn't able to find
any documentation on this. Checked [cassandra.yaml file configuration | Apache
Cassandra
Documentation|https://cassandra.apache.org/doc/stable/cassandra/configuration/cass_yaml_file.html]
and also cassandra.yaml in the tarball download.
> Timeout in config is not respected
> ----------------------------------
>
> Key: CASSANDRA-20049
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20049
> Project: Cassandra
> Issue Type: Bug
> Reporter: Cameron Zemek
> Priority: Normal
> Attachments: image-2024-11-04-11-43-55-089.png
>
>
> Come across a bad data model where the request_timeout and
> read_request_timeout had been increased. On upgrading to 4.1 I noticed the
> query to the bad partitions (ie. large number of rows and tombstones and
> large amount of data on disk) would fail with timeout.
> I have setup test cluster to reproduce on 5.0.2. I write1Kb rows to the same
> partition. The client and server side are both set to 15 minute timeouts.
> Setting page-size to 1 million (so fetching the page takes awhile). I get the
> following error on the client:
>
> !image-2024-11-04-11-43-55-089.png!
> And a read timeout shows in the metrics and max latency is 12.1 seconds.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
