Messages: Make it possible to produce messages w/o a transaction #793
Labels
scope/backend
Related to backend changes
status/triage/completed
Automatic triage completed
type/bug
Something isn't working
Issue submitter TODO list
Is your proposal related to a problem?
No response
Describe the feature you're interested in
Issue Title: How to Disable Transactional Producer in Kafka-UI When Broker Transactions Are Disabled?
Description:
Hello,
I am experiencing an issue with Kafka-UI when trying to send messages to a Kafka broker that has transactions disabled (
transactions.enable=false
). I'd like to report this problem and ask for guidance on how to configure Kafka-UI to send messages without initiating transactions on the client side.Environment:
Problem Description:
Local Kafka Broker:
transactions.enable
parameter is set totrue
(transactions are enabled).Remote Kafka Broker:
transactions.enable
parameter is set tofalse
(transactions are disabled).Analysis:
It appears that Kafka-UI uses a transactional producer when sending messages. If the broker does not support transactions, attempts to send messages fail because the client tries to start a transaction that the broker cannot handle.
I prefer not to change the server (broker) configuration to enable transactions, especially in production environments, where modifying broker settings might have unintended consequences.
Question:
Attempts Made:
transactional.id
and by ensuring thatenable.idempotence
is set appropriately.Request for Assistance:
Additional Information:
transactions.enable=true
on the remote broker, Kafka-UI can successfully send messages.Thank You:
Thank you for your time and for providing Kafka-UI as a valuable tool for the community. I appreciate your assistance and look forward to your guidance on resolving this issue.
Note: If any logs or error messages would be helpful, please let me know, and I'll provide them accordingly.
Describe alternatives you've considered
No response
Version you're running
ghcr.io/kafbat/kafka-ui:latest
Additional context
No response
The text was updated successfully, but these errors were encountered: