Github user pnowojski commented on the issue:
https://github.com/apache/flink/pull/4239
Indeed it seems like you are right. `read_committed` doesn't play along
with long `max.transaction.timeout.ms`. I'm not sure about Beam, but in Flink
we can not use one single `transactional.id`, because our checkpoints are
asynchronous - `notifyCheckpointComplete` (which triggers
`KafkaProducer#commit`) can come long after `preCommit`. In that time we can
not use the same `transactional.id` for new transactions.
We can walk around this issue by implementing a pool of
`transactional.id`s, which we can save on the state. This will allows on
restoring state to not only `recoverAndCommit` all pending transactions, but to
abort all other unknown "lingering" transactions
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
