[
https://issues.apache.org/jira/browse/KAFKA-18102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
George Yang updated KAFKA-18102:
--------------------------------
Description:
Due to some network issue, the network connection between data center `mcsa`
and data center `mcsb` was disconnected around 10:43 on November 25th and
lasted for a while. From the logs, it can be seen that the local data center
and the remote data center with the following bootstrap servers:
{code:java}
mcsa.bootstrap.servers =
10.161.70.98:13399,10.161.70.150:13399,10.161.70.126:13399{code}
{{did not report any network disconnection until 10:54:32. After this,
MirrorMaker reported: {{}}
{code:java}
Got error produce response with correlation id 406 on topic-partition *****,
retrying (2147483646 attempts left). Error: UNKNOWN_TOPIC_OR_PARTITION
(org.apache.kafka.clients.producer.internals.Sender:687)[kafka-producer-network-thread
| connector-producer-MirrorSourceConnector-3]{code}
and
{code:java}
Received unknown topic or partition error in produce request on partition
errors.{code}
Please refer to the attached log file for details. The configuration
information for both data centers is as follows.
clusters = mcsb, mcsa
mcsb.bootstrap.servers = 10.161.70.119:13399, 10.161.70.129:13399,
10.161.70.125:13399
mcsa.bootstrap.servers = 10.161.70.98:13399, 10.161.70.150:13399,
10.161.70.126:13399
What could have caused this error report, and how can it be resolved?
PS: other non sync data topics which does not start with the prefix 'mcsa.' or
'mcsb.' can receive message normally.
was:
Due to some network issue, the network connection between data center `mcsa`
and data center `mcsb` was disconnected around 10:43 on November 25th and
lasted for a while. From the logs, it can be seen that the local data center
and the remote data center with the following bootstrap servers:
{code:java}
mcsa.bootstrap.servers =
10.161.70.98:13399,10.161.70.150:13399,10.161.70.126:13399{code}
{{did not report any network disconnection until 10:54:32. After this,
MirrorMaker reported: {{}}
{code:java}
Got error produce response with correlation id 406 on topic-partition *****,
retrying (2147483646 attempts left). Error: UNKNOWN_TOPIC_OR_PARTITION
(org.apache.kafka.clients.producer.internals.Sender:687)[kafka-producer-network-thread
| connector-producer-MirrorSourceConnector-3]{code}
and
{code:java}
Received unknown topic or partition error in produce request on partition
errors.{code}
Please refer to the attached log file for details. The configuration
information for both data centers is as follows.
clusters = mcsb, mcsa
mcsb.bootstrap.servers = 10.161.70.119:13399, 10.161.70.129:13399,
10.161.70.125:13399
mcsa.bootstrap.servers = 10.161.70.98:13399, 10.161.70.150:13399,
10.161.70.126:13399
What could have caused this error report, and how can it be resolved?
> All consumer groups stop to receive message
> -------------------------------------------
>
> Key: KAFKA-18102
> URL: https://issues.apache.org/jira/browse/KAFKA-18102
> Project: Kafka
> Issue Type: Bug
> Components: mirrormaker
> Affects Versions: 3.7.1
> Reporter: George Yang
> Priority: Major
> Attachments: connect.log.2024-11-25-10
>
>
> Due to some network issue, the network connection between data center `mcsa`
> and data center `mcsb` was disconnected around 10:43 on November 25th and
> lasted for a while. From the logs, it can be seen that the local data center
> and the remote data center with the following bootstrap servers:
> {code:java}
> mcsa.bootstrap.servers =
> 10.161.70.98:13399,10.161.70.150:13399,10.161.70.126:13399{code}
> {{did not report any network disconnection until 10:54:32. After this,
> MirrorMaker reported: {{}}
> {code:java}
> Got error produce response with correlation id 406 on topic-partition *****,
> retrying (2147483646 attempts left). Error: UNKNOWN_TOPIC_OR_PARTITION
> (org.apache.kafka.clients.producer.internals.Sender:687)[kafka-producer-network-thread
> | connector-producer-MirrorSourceConnector-3]{code}
> and
> {code:java}
> Received unknown topic or partition error in produce request on partition
> errors.{code}
> Please refer to the attached log file for details. The configuration
> information for both data centers is as follows.
> clusters = mcsb, mcsa
> mcsb.bootstrap.servers = 10.161.70.119:13399, 10.161.70.129:13399,
> 10.161.70.125:13399
> mcsa.bootstrap.servers = 10.161.70.98:13399, 10.161.70.150:13399,
> 10.161.70.126:13399
> What could have caused this error report, and how can it be resolved?
>
> PS: other non sync data topics which does not start with the prefix 'mcsa.'
> or 'mcsb.' can receive message normally.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
