[
https://issues.apache.org/jira/browse/CASSANDRA-19428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17826905#comment-17826905
]
Ekaterina Dimitrova edited comment on CASSANDRA-19428 at 3/14/24 1:28 AM:
--------------------------------------------------------------------------
To put breakpoints and debug I need to raise range_request_timeout and enable
SAI_TEST_DISABLE_TIMEOUT.
I noticed in the artifacts logs that there is a strong self-ref loop detected.
(not too surprising, there is also CASSANDRA-19222). However, I have not seen
that leak locally so far.
I decided to apply the patch to 5.0. This is from the 5.0 run where the test
fails simply with read timeout.
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2667/workflows/29de6ee7-dd02-4da2-88eb-1e670ef75288]
(the dtest failures seem to be OS error, environmental, we've seen this
before, ignore them)
{code:java}
com.datastax.driver.core.exceptions.ReadTimeoutException: Cassandra timeout
during read query at consistency LOCAL_ONE (1 responses were required but only
0 replica responded). In case this was generated during read repair, the
consistency level is not representative of the actual consistency.{code}
I am planning to spend more time on 5.0 as it seems it would be easier to find
out the problem and then move to trunk where there might be more than 1 problem
and not only from my patch (?)
was (Author: e.dimitrova):
To put breakpoints and debug I need to raise range_request_timeout and enable
SAI_TEST_DISABLE_TIMEOUT.
I noticed in the artifacts logs that there is a strong self-ref loop detected.
(not too surprising, there is also CASSANDRA-19222). However, I have not seen
that leak locally so far.
I decided to apply the patch to 5.0. This is from the 5.0 run where the test
fails simply with read timeout, even without raising any timeouts, etc.
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2667/workflows/29de6ee7-dd02-4da2-88eb-1e670ef75288]
(the dtest failures seem to be OS error, environmental, we've seen this
before, ignore them)
{code:java}
com.datastax.driver.core.exceptions.ReadTimeoutException: Cassandra timeout
during read query at consistency LOCAL_ONE (1 responses were required but only
0 replica responded). In case this was generated during read repair, the
consistency level is not representative of the actual consistency.{code}
I am planning to spend more time on 5.0 as it seems it would be easier to find
out the problem and then move to trunk where there might be more than 1 problem
and not only from my patch (?)
> Clean up KeyRangeIterator classes
> ---------------------------------
>
> Key: CASSANDRA-19428
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19428
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/2i Index
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Low
> Fix For: 5.0.x, 5.x
>
>
> Remove KeyRangeIterator.current and simplify
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
