cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13975) Add a workaround for overly large read repair mutations
Date Thu, 02 Nov 2017 15:45:00 GMT


Aleksey Yeschenko commented on CASSANDRA-13975:

A straight-forward change pushed [here|].
Unit test run [here|], dtest run [here|].

> Add a workaround for overly large read repair mutations
> -------------------------------------------------------
>                 Key: CASSANDRA-13975
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message