[
https://issues.apache.org/jira/browse/CASSANDRA-12783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134811#comment-16134811
]
Kurt Greaves commented on CASSANDRA-12783:
------------------------------------------
Kind of. Was actually working on fixing CASSANDRA-13608 which is somewhat
related, following Paulo's ideas from
[here|https://issues.apache.org/jira/browse/CASSANDRA-11670?focusedCommentId=15359128&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15359128]
to fix the limitation on the batchlog of only being able to contain
{{max_value_size}}. This also introduces the concept of "activating" a batch
mentioned in the description. Not really sure that it will prevent OOMs, but
description isn't really clear what that is about. I will upload my branch
somewhere shortly, have actually gotten sidetracked trying to work out why I
can generate time based UUIDs that are not ordered on time... but more on that
later
> Break up large MV mutations to prevent OOMs
> -------------------------------------------
>
> Key: CASSANDRA-12783
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12783
> Project: Cassandra
> Issue Type: Bug
> Components: Local Write-Read Paths, Materialized Views
> Reporter: Carl Yeksigian
> Assignee: Kurt Greaves
> Fix For: 4.x
>
>
> We only use the code path added in CASSANDRA-12268 for the view builder
> because otherwise we would break the contract of the batchlog, where some
> mutations may be written and pushed out before the whole batch log has been
> saved.
> We would need to ensure that all of the updates make it to the batchlog
> before allowing the batchlog manager to try to replay them, but also before
> we start pushing out updates to the paired replicas.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
