[
https://issues.apache.org/jira/browse/CASSANDRA-16232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17222214#comment-17222214
]
Tom van der Woerdt commented on CASSANDRA-16232:
------------------------------------------------
It seems that the specific case that's not handled in the batch_size_* settings
is the situation in which a single-partition LWT batch is large. A normal
logged batch to a single partition gets turned into an unlogged batch, but when
that same batch contains a LWT write it's effectively still as heavy as a
logged batch and the limits (or some other configuration key) should probably
apply.
> Need something like batch_size_fail_threshold_in_kb for LWTs
> ------------------------------------------------------------
>
> Key: CASSANDRA-16232
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16232
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Lightweight Transactions
> Reporter: Tom van der Woerdt
> Priority: Normal
> Fix For: 3.11.x
>
>
> Subject probably says it all, but basically there's a
> batch_size_warn_threshold_in_kb and batch_size_fail_threshold_in_kb in the
> config but these don't apply to LWTs.
> So of course I found a situation in which devs were doing LWT operations of
> many megabytes :D
> Can we make it possible to forbid these, the same way it can be done for
> batches?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
