[
https://issues.apache.org/jira/browse/CASSANDRA-14330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16408133#comment-16408133
]
Aleksey Yeschenko commented on CASSANDRA-14330:
-----------------------------------------------
Branches for [3.0|https://github.com/iamaleksey/cassandra/tree/14330-3.0],
[3.11|https://github.com/iamaleksey/cassandra/tree/14330-3.11], and
[4.0|https://github.com/iamaleksey/cassandra/tree/14330-4.0]. CI:
[3.0|https://circleci.com/gh/iamaleksey/cassandra/70],
[3.11|https://circleci.com/gh/iamaleksey/cassandra/73],
[4.0|https://circleci.com/gh/iamaleksey/cassandra/74].
Minimal reproduction dtest
[here|https://github.com/iamaleksey/cassandra-dtest/tree/14330].
> Handle repeat open bound from SRP in read repair
> ------------------------------------------------
>
> Key: CASSANDRA-14330
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14330
> Project: Cassandra
> Issue Type: Bug
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Priority: Major
> Fix For: 3.0.x, 3.11.x, 4.x
>
>
> If there is an open range tombstone in an iterator, a short read protection
> request for it will include a repeat open bound. Currently, {{DataResolver}}
> doesn't expect this, and will raise an assertion, timing out the request.
> As this is a completely normal/common scenario, we should allow for this, and
> relax the assertion.
> Additionally, the linked branch makes the re-trhowing {{AssertionError}} more
> detailed and more correct: the responses are now printed out in the correct
> order, respecting {{isReversed}}, the command causing the assertion is now
> logged, as is {{isReversed}} itself, and local deletion times for RTs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
