Open arulajmani opened 1 day ago
@arulajmani I'm adding a new setting that is completely independent of kv.transaction.reject_over_max_intents_budget.enabled
and kv.transaction.max_intents_bytes
for now. I'm going to update the node on kv.transaction.reject_over_max_intents_budget.enabled
to recommend against using it.
Sounds good @andrewbaptist. I'll assign the issue to you in that case.
Describe the problem
Currently, the only way to reject large write transactions is
kv.transaction.reject_over_max_intents_budget.enabled
, which rejects any transaction that goes over thekv.transaction.max_intents_bytes
tracking limit. It's not great that these settings are always tied together [1].We should introduce a new cluster setting to reject large writing transactions that isn't tied to the
kv.transaction.max_intents_bytes
cluster setting.Jira issue: CRDB-44747