[
https://issues.apache.org/jira/browse/CASSANDRA-16232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17223028#comment-17223028
]
Benjamin Lerer commented on CASSANDRA-16232:
--------------------------------------------
This behavior is not a bug. Single partition batches have been excluded from
the warning on purpose (see CASSANDRA-10876 and the discussion in
CASSANDRA-6487 starting
[there|https://issues.apache.org/jira/browse/CASSANDRA-6487?focusedCommentId=15013748&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-15013748]).
Could you elaborate what you mean by: {quote} when that same batch contains a
LWT write it's effectively still as heavy as a logged batch{quote} ?
> batch_size_fail_threshold_in_kb does not account 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
> Assignee: Benjamin Lerer
> 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: [email protected]
For additional commands, e-mail: [email protected]
