[
https://issues.apache.org/jira/browse/CASSANDRA-13975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16235982#comment-16235982
]
Aleksey Yeschenko commented on CASSANDRA-13975:
-----------------------------------------------
A straight-forward change pushed
[here|https://github.com/iamaleksey/cassandra/commits/13975-3.0]. Unit test run
[here|https://circleci.com/gh/iamaleksey/cassandra/63], dtest run
[here|https://builds.apache.org/job/Cassandra-devbranch-dtest/407/].
> Add a workaround for overly large read repair mutations
> -------------------------------------------------------
>
> Key: CASSANDRA-13975
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13975
> Project: Cassandra
> Issue Type: Bug
> Components: Coordination
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Priority: Major
> Fix For: 3.0.x, 3.11.x
>
>
> It's currently possible for {{DataResolver}} to accumulate more changes to
> read repair that would fit in a single serialized mutation. If that happens,
> the node receiving the mutation would fail, and the read would time out, and
> won't be able to proceed until the operator runs repair or manually drops the
> affected partitions.
> Ideally we should either read repair iteratively, or at least split the
> resulting mutation into smaller chunks in the end. In the meantime, for
> 3.0.x, I suggest we add logging to catch this, and a -D flag to allow
> proceeding with the requests as is when the mutation is too large, without
> read repair.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
