Jason Gustafson 3356faf8de KAFKA-13099; Transactional expiration should account for max batch size (#11098) ... When expiring transactionalIds, we group the tombstones together into batches. Currently there is no limit on the size of these batches, which can lead to `MESSAGE_TOO_LARGE` errors when a bunch of transactionalIds need to be expired at the same time. This patch fixes the problem by ensuring that the batch size respects the configured limit. Any transactionalIds which are eligible for expiration and cannot be fit into the batch are postponed until the next periodic check. Reviewers: David Jacot <djacot@confluent.io>, Guozhang Wang <wangguoz@gmail.com>		2021-07-29 13:52:28 -07:00
..
src	KAFKA-13099; Transactional expiration should account for max batch size (#11098)	2021-07-29 13:52:28 -07:00
.gitignore	…