[ 
https://issues.apache.org/jira/browse/KAFKA-17859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

thanhnd1996 updated KAFKA-17859:
--------------------------------
    Description: 
Subject: Bug when Kafka Producer Initializes Message Publishing

Hi Admin,

I'm encountering an issue with my Kafka cluster (3 nodes, running in KRaft 
mode). After performing maintenance on one of the nodes and restarting the 
Kafka service (using systemd), I’m facing an error when trying to connect and 
initialize a transaction to a topic (e.g., {{{}topic_A{}}}, 1 partition, 2 
replicas).

After reconnecting, Kafka throws the following exception:# 
kafka-server-start.sh[77303]: [2024-10-22 12:19:25,145] ERROR [Controller 1] 
allocateProducerIds: unable to start processing because of 
NotControllerException. (org.apache.kafka.controller.QuorumController)
I’ve restarted the Kafka service, but the exception repeats each time the 
service initializes a transaction. Below is my configuration (in C#):

{   "Id": "ABC",   "Topic": "Topic_A",   "BootstrapServers": 
"IP_01,IP_02,IP_03",   "Acks": -1,   "TransactionTimeoutMs": 300000,   
"MessageTimeoutMs": 120000,   "QueueBufferingMaxMessages": 1048576,   
"EnableIdempotence": true,   "MaxInFlight": 5,   "LingerMs": 0 }

.

I hope admin can help me figure out the issue.

Thank you!

  was:
Subject: Bug when Kafka Producer Initializes Message Publishing

Hi Admin,

I'm encountering an issue with my Kafka cluster (3 nodes, running in KRaft 
mode). After performing maintenance on one of the nodes and restarting the 
Kafka service (using systemd), I’m facing an error when trying to connect and 
initialize a transaction to a topic (e.g., {{{}topic_A{}}}, 1 partition, 2 
replicas).

After reconnecting, Kafka throws the following exception:# 
kafka-server-start.sh[77303]: [2024-10-22 12:19:25,145] ERROR [Controller 1] 
allocateProducerIds: unable to start processing because of 
NotControllerException. (org.apache.kafka.controller.QuorumController)
I’ve restarted the Kafka service, but the exception repeats each time the 
service initializes a transaction. Below is my configuration (in C#):
{
  "Id": "Securities",
  "Topic": "Topic_A",
  "BootstrapServers": "10.26.7.58,10.26.7.59,10.26.7.60,10.26.7.68,10.26.7.69",
  "Acks": -1,
  "TransactionTimeoutMs": 300000,
  "MessageTimeoutMs": 120000,
  "QueueBufferingMaxMessages": 1048576,
  "EnableIdempotence": true,
  "MaxInFlight": 5,
  "LingerMs": 0
}.

I hope admin can help me figure out the issue.

Thank you!


> Bug
> ---
>
>                 Key: KAFKA-17859
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17859
>             Project: Kafka
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 3.2.0
>         Environment: dedicate server, kafka cluster 3 node , running on 
> systemd
>            Reporter: thanhnd1996
>            Priority: Critical
>         Attachments: Image-failed-Controller.png
>
>
> Subject: Bug when Kafka Producer Initializes Message Publishing
> Hi Admin,
> I'm encountering an issue with my Kafka cluster (3 nodes, running in KRaft 
> mode). After performing maintenance on one of the nodes and restarting the 
> Kafka service (using systemd), I’m facing an error when trying to connect and 
> initialize a transaction to a topic (e.g., {{{}topic_A{}}}, 1 partition, 2 
> replicas).
> After reconnecting, Kafka throws the following exception:# 
> kafka-server-start.sh[77303]: [2024-10-22 12:19:25,145] ERROR [Controller 1] 
> allocateProducerIds: unable to start processing because of 
> NotControllerException. (org.apache.kafka.controller.QuorumController)
> I’ve restarted the Kafka service, but the exception repeats each time the 
> service initializes a transaction. Below is my configuration (in C#):
> {   "Id": "ABC",   "Topic": "Topic_A",   "BootstrapServers": 
> "IP_01,IP_02,IP_03",   "Acks": -1,   "TransactionTimeoutMs": 300000,   
> "MessageTimeoutMs": 120000,   "QueueBufferingMaxMessages": 1048576,   
> "EnableIdempotence": true,   "MaxInFlight": 5,   "LingerMs": 0 }
> .
> I hope admin can help me figure out the issue.
> Thank you!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to