Joost van de Wijgerd created KAFKA-9071:
-------------------------------------------
Summary: transactional.id.expiration.ms config value should be
implemented as a Long
Key: KAFKA-9071
URL: https://issues.apache.org/jira/browse/KAFKA-9071
Project: Kafka
Issue Type: Improvement
Components: config
Affects Versions: 2.3.0
Reporter: Joost van de Wijgerd
Currently the value of this config parameter is limited to MAX_INT effectively
limiting the transactional id expiration to ~ 25 days. This is causing some
issues for us on our Acceptance environment (which is not used that often /
heavily) where our transactional services will start failing because if this
issue.
I believe best practice for millisecond values should be to implement them as a
Long and not as an Integer
this is currently the max value: transactional.id.expiration.ms=2147483647
while I would like to set it to: transactional.id.expiration.ms=31540000000
(i.e. 1 year)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
