Open abolipai99 opened 2 years ago
thanks - i have reproduced, looking into it.
it appears to be a bug in the KIP-360 implementation whereby librdkafka may errantly make a second InitProducerId call.
additional InitProducerId
calls seem to only occur after a concurrent_transactions
error result though. and this is also what the java implementation seems to do. still looking into it.
Read the FAQ first: https://github.com/edenhill/librdkafka/wiki/FAQ
Do NOT create issues for questions, use the discussion forum: https://github.com/edenhill/librdkafka/discussions
Description
We wrote an application which deploys a transactional client (transactional consumer +. producer) . There is a single transactional producer created with a unique transactional id. After few hours, the producer shows this error due to which the application shuts down:
During the run, no other producer instances were created.
How to reproduce
This is the application code which uses the confluent-kafka-python library. (input topics, producer and consumer configurations are taken as user input)
IMPORTANT: Always try to reproduce the issue on the latest released version (see https://github.com/edenhill/librdkafka/releases), if it can't be reproduced on the latest version the issue has been fixed.
Checklist
IMPORTANT: We will close issues where the checklist has not been completed.
Please provide the following information:
master