Alexey Serbin created KUDU-3023:
-----------------------------------
Summary: Enforce consistency between maximum RPC size and maximum
size of transaction
Key: KUDU-3023
URL: https://issues.apache.org/jira/browse/KUDU-3023
Project: Kudu
Issue Type: Improvement
Components: master, tserver
Reporter: Alexey Serbin
Current default settings for the {{\-\-rpc_max_message_size}} and the
{{\-\-tablet_transaction_memory}} (50MB and 64MB correspondingly) might lead to
situations like described in KUDU-3016. In other words, a transaction of a
size between 50 and 64 MBytes can get into the WAL of a leader tablet replica,
but the leader replica cannot push the corresponding Raft update to follower
replicas.
It would be nice to establish a group validator to prevent such situations from
happening.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
