You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Lerer (Jira)" <ji...@apache.org> on 2020/10/29 16:10:00 UTC
[jira] [Assigned] (CASSANDRA-16232) batch_size_fail_threshold_in_kb
does not account for LWTs
[ https://issues.apache.org/jira/browse/CASSANDRA-16232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Lerer reassigned CASSANDRA-16232:
------------------------------------------
Assignee: Benjamin Lerer
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org