Files
scylladb/test/boost
Mikołaj Grzebieluch 6dad582796 raft: reduce max batch size of raft commands and raft entries
For now, `raft_sys_table_storage::_max_mutation_size` equals `max_mutation_size`
(half of the commitlog segment size), so with some additional information, it
can exceed this threshold resulting in throwing an exception when writing
mutation to the commitlog.

A batch of raft commands has the size at most `group0_state_machine::merger::max_command_size`
(half of the commitlog segment size). It doesn't have additional metadata, but
it may have a size of exactly `max_mutation_size`. It shouldn't make any trouble,
but it is prefered to be careful.

Make `raft_sys_table_storage::_max_mutation_size` and
`group0_state_machine::merger::max_command_size` more strict to leave space
for metadata.

Fixed typo "1204" => "1024".
2023-07-07 13:11:52 +02:00
..
2023-02-15 11:01:50 +02:00
2023-02-15 11:01:50 +02:00
2023-02-15 11:09:04 +02:00
2023-02-15 11:01:50 +02:00
2023-06-07 20:25:49 +03:00
2023-04-26 14:09:58 +08:00