You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@kafka.apache.org by Andreas Gillmann <an...@gls-itservices.com> on 2022/01/26 13:09:56 UTC
Connector is still in 'RUNNING' status even though the heartbeat failed
Hello,
I have noticed a problem which I have also discussed with RedHat (https://issues.redhat.com/browse/DBZ-4521):
Prerequisites:
* Debezium connector with heartbeat configuration ( "heartbeat.topics.prefix" is set)
* Heartbeat topic on Kafka side does NOT exists
* Parameter auto.create.topics is disabled (=false)
Execution:
* Connector was created
* Connector starts the heartbeat
* Connector logs the following entry: [WARN] 2022-01-06 13:25:30,094 [kafka-producer-network-thread | connector-producer-itgermany.pmops.dispoapp.gateway.DE-350.debeziumconnector-0] org.apache.kafka.clients.NetworkClient handleSuccessfulResponse - [Producer clientId=connector-producer-itgermany.pmops.dispoapp.gateway.DE-350.debeziumconnector-0] Error while fetching metadata with correlation id 38409 : {itgermany.pmops.dispoapp.gateway.heartbeat.GatewayDepot35=UNKNOWN_TOPIC_OR_PARTITION}
* Connector status remains 'RUNNING'
* NO Data comes to Kafka via the Connector
Troubleshooting:
* Re-creating the connector caused data to be sent to Kafka for a short time (until the heartbeat was repeated).
People from RedHat told me that they are just passing the topic name and the message to Kafka and they do not receive a correct response
Kind Regards / Mit freundlichen Grüßen
Andreas Gillmann
Product Management Operations
IT GLS Germany/International
GLS IT Services GmbH
GLS Germany-Straße 1-7
36286 Neuenstein
Germany
LinkedIn<https://www.linkedin.com/company/gls-germany>[cid:image013.png@01D812BE.62B70F40]
[cid:image014.png@01D812BE.62B70F40] Twitter<http://www.twitter.com/GLS_Germany>
[cid:image015.png@01D812BE.62B70F40]Facebook<http://facebook.com/GLSGermany>
[cid:image016.png@01D812BE.62B70F40]Instagram<https://www.instagram.com/glsgermany/>
[cid:image017.jpg@01D812BE.62B70F40]
t
+49 (0) 66 77 17 437
m
+49 (0) 172 1781 437
e
andreas.gillmann@gls-itservices.com
w
www.gls-group.com<http://www.gls-group.com/>
[cid:image018.jpg@01D812BE.62B70F40]
________________________________
GLS IT Services GmbH
Sitz: Neuenstein, Amtsgericht Bad Hersfeld HRB 388, Geschäftsführer: Thorsten Pruin
________________________________
Re: Connector is still in 'RUNNING' status even though the heartbeat failed
Posted by "Tauzell, Dave" <Da...@surescripts.com>.
PR means “Pull Request”. It is a way to have others review your code changes and, when ready, they can merge them in.
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
From: Andreas Gillmann <an...@gls-itservices.com>
Date: Monday, January 31, 2022 at 4:34 AM
To: users@kafka.apache.org <us...@kafka.apache.org>
Subject: [EXTERNAL] AW: Connector is still in 'RUNNING' status even though the heartbeat failed
Hello Luke,
yes I will do so, but please tell me, what is a PR?
Regards,
Andreas
-----Ursprüngliche Nachricht-----
Von: Luke Chen <sh...@gmail.com>
Gesendet: Sonntag, 30. Januar 2022 10:04
An: Kafka Users <us...@kafka.apache.org>
Betreff: Re: Connector is still in 'RUNNING' status even though the heartbeat failed
Hi Andreas,
Could you open a bug in Kafka JIRA
<https://urldefense.com/v3/__https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13523?filter=allopenissues__;!!K_cMf-SQz-o!Mr9VUaF9RU_toqC-97zwMGdqWJbghllJ7tBAyErJJXMFDJ2S5YRXch4sb4LX2JudC__Xgg$ >
?
And you're welcome to create a PR for this issue.
Let me know if you need any help.
Thank you.
Luke
On Wed, Jan 26, 2022 at 9:10 PM Andreas Gillmann < andreas.gillmann@gls-itservices.com> wrote:
> Hello,
>
>
>
> I have noticed a problem which I have also discussed with RedHat (
> https://urldefense.com/v3/__https://issues.redhat.com/browse/DBZ-4521__;!!K_cMf-SQz-o!Mr9VUaF9RU_toqC-97zwMGdqWJbghllJ7tBAyErJJXMFDJ2S5YRXch4sb4LX2JufwHayYQ$<https://urldefense.com/v3/__https:/issues.redhat.com/browse/DBZ-4521__;!!K_cMf-SQz-o!Mr9VUaF9RU_toqC-97zwMGdqWJbghllJ7tBAyErJJXMFDJ2S5YRXch4sb4LX2JufwHayYQ$> ):
>
> Prerequisites:
>
> - Debezium connector with heartbeat configuration ( "heartbeat.topics.prefix"
> is set)
> - Heartbeat topic on Kafka side does NOT exists
> - Parameter auto.create.topics is disabled (=false)
>
> Execution:
>
> - Connector was created
> - Connector starts the heartbeat
> - Connector logs the following entry: [WARN] 2022-01-06 13:25:30,094
> [kafka-producer-network-thread |
> connector-producer-itgermany.pmops.dispoapp.gateway.DE-350.debeziumconnector-0]
> org.apache.kafka.clients.NetworkClient handleSuccessfulResponse - [Producer
> clientId=connector-producer-itgermany.pmops.dispoapp.gateway.DE-350.debeziumconnector-0]
> Error while fetching metadata with correlation id 38409 :
> {itgermany.pmops.dispoapp.gateway.heartbeat.GatewayDepot35=UNKNOWN_TOPIC_OR_PARTITION}
> - Connector status remains 'RUNNING'
> - NO Data comes to Kafka via the Connector
>
> Troubleshooting:
>
> - Re-creating the connector caused data to be sent to Kafka for a
> short time (until the heartbeat was repeated).
>
>
>
> People from RedHat told me that they are just passing the topic name
> and the message to Kafka and they do not receive a correct response
>
>
>
>
>
> Kind Regards / Mit freundlichen Grüßen
>
> Andreas Gillmann
> Product Management Operations
> IT GLS Germany/International
>
> GLS IT Services GmbH
> GLS Germany-Straße 1-7
> 36286 Neuenstein
> Germany
>
> LinkedIn <https://urldefense.com/v3/__https://www.linkedin.com/company/gls-germany__;!!K_cMf-SQz-o!Mr9VUaF9RU_toqC-97zwMGdqWJbghllJ7tBAyErJJXMFDJ2S5YRXch4sb4LX2Jup3x06Nw$ >
>
> Twitter <https://urldefense.com/v3/__http://www.twitter.com/GLS_Germany__;!!K_cMf-SQz-o!Mr9VUaF9RU_toqC-97zwMGdqWJbghllJ7tBAyErJJXMFDJ2S5YRXch4sb4LX2JtmatymwQ$ >
>
> Facebook <https://urldefense.com/v3/__http://facebook.com/GLSGermany__;!!K_cMf-SQz-o!Mr9VUaF9RU_toqC-97zwMGdqWJbghllJ7tBAyErJJXMFDJ2S5YRXch4sb4LX2JvnleEFXQ$ >
>
> Instagram <https://urldefense.com/v3/__https://www.instagram.com/glsgermany/__;!!K_cMf-SQz-o!Mr9VUaF9RU_toqC-97zwMGdqWJbghllJ7tBAyErJJXMFDJ2S5YRXch4sb4LX2Js6X9X06A$ >
>
>
>
>
>
>
>
>
>
> *t*
>
> +49 (0) 66 77 17 437
>
>
>
> *m*
>
> +49 (0) 172 1781 437
>
>
>
> *e*
>
> andreas.gillmann@gls-itservices.com
>
>
>
> *w*
>
> https://urldefense.com/v3/__http://www.gls-group.com__;!!K_cMf-SQz-o!Mr9VUaF9RU_toqC-97zwMGdqWJbghllJ7tBAyErJJXMFDJ2S5YRXch4sb4LX2JuM7D4sjQ$<https://urldefense.com/v3/__http:/www.gls-group.com__;!!K_cMf-SQz-o!Mr9VUaF9RU_toqC-97zwMGdqWJbghllJ7tBAyErJJXMFDJ2S5YRXch4sb4LX2JuM7D4sjQ$>
>
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------
> GLS IT Services GmbH
> Sitz: Neuenstein, Amtsgericht Bad Hersfeld HRB 388, Geschäftsführer:
> Thorsten Pruin
> ------------------------------
>
________________________________
GLS IT Services GmbH
Sitz: Neuenstein, Amtsgericht Bad Hersfeld HRB 388, Geschäftsführer: Thorsten Pruin
________________________________
This e-mail and any files transmitted with it are confidential, may contain sensitive information, and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender by reply e-mail immediately and destroy all copies of the e-mail and any attachments.
Re: Connector is still in 'RUNNING' status even though the heartbeat failed
Posted by Luke Chen <sh...@gmail.com>.
I mean " pull request".
Ref:
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
Thanks.
Luke
Andreas Gillmann <an...@gls-itservices.com> 於 2022年1月31日 週一
下午6:34 寫道：
> Hello Luke,
>
> yes I will do so, but please tell me, what is a PR?
>
> Regards,
> Andreas
>
> -----Ursprüngliche Nachricht-----
> Von: Luke Chen <sh...@gmail.com>
> Gesendet: Sonntag, 30. Januar 2022 10:04
> An: Kafka Users <us...@kafka.apache.org>
> Betreff: Re: Connector is still in 'RUNNING' status even though the
> heartbeat failed
>
> Hi Andreas,
>
> Could you open a bug in Kafka JIRA
> <
> https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13523?filter=allopenissues
> >
> ?
> And you're welcome to create a PR for this issue.
>
> Let me know if you need any help.
>
> Thank you.
> Luke
>
> On Wed, Jan 26, 2022 at 9:10 PM Andreas Gillmann <
> andreas.gillmann@gls-itservices.com> wrote:
>
> > Hello,
> >
> >
> >
> > I have noticed a problem which I have also discussed with RedHat (
> > https://issues.redhat.com/browse/DBZ-4521):
> >
> > Prerequisites:
> >
> > - Debezium connector with heartbeat configuration (
> "heartbeat.topics.prefix"
> > is set)
> > - Heartbeat topic on Kafka side does NOT exists
> > - Parameter auto.create.topics is disabled (=false)
> >
> > Execution:
> >
> > - Connector was created
> > - Connector starts the heartbeat
> > - Connector logs the following entry: [WARN] 2022-01-06 13:25:30,094
> > [kafka-producer-network-thread |
> >
> connector-producer-itgermany.pmops.dispoapp.gateway.DE-350.debeziumconnector-0]
> > org.apache.kafka.clients.NetworkClient handleSuccessfulResponse -
> [Producer
> >
> clientId=connector-producer-itgermany.pmops.dispoapp.gateway.DE-350.debeziumconnector-0]
> > Error while fetching metadata with correlation id 38409 :
> >
> {itgermany.pmops.dispoapp.gateway.heartbeat.GatewayDepot35=UNKNOWN_TOPIC_OR_PARTITION}
> > - Connector status remains 'RUNNING'
> > - NO Data comes to Kafka via the Connector
> >
> > Troubleshooting:
> >
> > - Re-creating the connector caused data to be sent to Kafka for a
> > short time (until the heartbeat was repeated).
> >
> >
> >
> > People from RedHat told me that they are just passing the topic name
> > and the message to Kafka and they do not receive a correct response
> >
> >
> >
> >
> >
> > Kind Regards / Mit freundlichen Grüßen
> >
> > Andreas Gillmann
> > Product Management Operations
> > IT GLS Germany/International
> >
> > GLS IT Services GmbH
> > GLS Germany-Straße 1-7
> > 36286 Neuenstein
> > Germany
> >
> > LinkedIn <https://www.linkedin.com/company/gls-germany>
> >
> > Twitter <http://www.twitter.com/GLS_Germany>
> >
> > Facebook <http://facebook.com/GLSGermany>
> >
> > Instagram <https://www.instagram.com/glsgermany/>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > *t*
> >
> > +49 (0) 66 77 17 437
> >
> >
> >
> > *m*
> >
> > +49 (0) 172 1781 437
> >
> >
> >
> > *e*
> >
> > andreas.gillmann@gls-itservices.com
> >
> >
> >
> > *w*
> >
> > www.gls-group.com
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ------------------------------
> > GLS IT Services GmbH
> > Sitz: Neuenstein, Amtsgericht Bad Hersfeld HRB 388, Geschäftsführer:
> > Thorsten Pruin
> > ------------------------------
> >
> ________________________________
> GLS IT Services GmbH
> Sitz: Neuenstein, Amtsgericht Bad Hersfeld HRB 388, Geschäftsführer:
> Thorsten Pruin
> ________________________________
>
AW: Connector is still in 'RUNNING' status even though the heartbeat failed
Posted by Andreas Gillmann <an...@gls-itservices.com>.
Hello Luke,
yes I will do so, but please tell me, what is a PR?
Regards,
Andreas
-----Ursprüngliche Nachricht-----
Von: Luke Chen <sh...@gmail.com>
Gesendet: Sonntag, 30. Januar 2022 10:04
An: Kafka Users <us...@kafka.apache.org>
Betreff: Re: Connector is still in 'RUNNING' status even though the heartbeat failed
Hi Andreas,
Could you open a bug in Kafka JIRA
<https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13523?filter=allopenissues>
?
And you're welcome to create a PR for this issue.
Let me know if you need any help.
Thank you.
Luke
On Wed, Jan 26, 2022 at 9:10 PM Andreas Gillmann < andreas.gillmann@gls-itservices.com> wrote:
> Hello,
>
>
>
> I have noticed a problem which I have also discussed with RedHat (
> https://issues.redhat.com/browse/DBZ-4521):
>
> Prerequisites:
>
> - Debezium connector with heartbeat configuration ( "heartbeat.topics.prefix"
> is set)
> - Heartbeat topic on Kafka side does NOT exists
> - Parameter auto.create.topics is disabled (=false)
>
> Execution:
>
> - Connector was created
> - Connector starts the heartbeat
> - Connector logs the following entry: [WARN] 2022-01-06 13:25:30,094
> [kafka-producer-network-thread |
> connector-producer-itgermany.pmops.dispoapp.gateway.DE-350.debeziumconnector-0]
> org.apache.kafka.clients.NetworkClient handleSuccessfulResponse - [Producer
> clientId=connector-producer-itgermany.pmops.dispoapp.gateway.DE-350.debeziumconnector-0]
> Error while fetching metadata with correlation id 38409 :
> {itgermany.pmops.dispoapp.gateway.heartbeat.GatewayDepot35=UNKNOWN_TOPIC_OR_PARTITION}
> - Connector status remains 'RUNNING'
> - NO Data comes to Kafka via the Connector
>
> Troubleshooting:
>
> - Re-creating the connector caused data to be sent to Kafka for a
> short time (until the heartbeat was repeated).
>
>
>
> People from RedHat told me that they are just passing the topic name
> and the message to Kafka and they do not receive a correct response
>
>
>
>
>
> Kind Regards / Mit freundlichen Grüßen
>
> Andreas Gillmann
> Product Management Operations
> IT GLS Germany/International
>
> GLS IT Services GmbH
> GLS Germany-Straße 1-7
> 36286 Neuenstein
> Germany
>
> LinkedIn <https://www.linkedin.com/company/gls-germany>
>
> Twitter <http://www.twitter.com/GLS_Germany>
>
> Facebook <http://facebook.com/GLSGermany>
>
> Instagram <https://www.instagram.com/glsgermany/>
>
>
>
>
>
>
>
>
>
> *t*
>
> +49 (0) 66 77 17 437
>
>
>
> *m*
>
> +49 (0) 172 1781 437
>
>
>
> *e*
>
> andreas.gillmann@gls-itservices.com
>
>
>
> *w*
>
> www.gls-group.com
>
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------
> GLS IT Services GmbH
> Sitz: Neuenstein, Amtsgericht Bad Hersfeld HRB 388, Geschäftsführer:
> Thorsten Pruin
> ------------------------------
>
________________________________
GLS IT Services GmbH
Sitz: Neuenstein, Amtsgericht Bad Hersfeld HRB 388, Geschäftsführer: Thorsten Pruin
________________________________
Re: Connector is still in 'RUNNING' status even though the heartbeat failed
Posted by Luke Chen <sh...@gmail.com>.
Hi Andreas,
Could you open a bug in Kafka JIRA
<https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13523?filter=allopenissues>
?
And you're welcome to create a PR for this issue.
Let me know if you need any help.
Thank you.
Luke
On Wed, Jan 26, 2022 at 9:10 PM Andreas Gillmann <
andreas.gillmann@gls-itservices.com> wrote:
> Hello,
>
>
>
> I have noticed a problem which I have also discussed with RedHat (
> https://issues.redhat.com/browse/DBZ-4521):
>
> Prerequisites:
>
> - Debezium connector with heartbeat configuration ( "heartbeat.topics.prefix"
> is set)
> - Heartbeat topic on Kafka side does NOT exists
> - Parameter auto.create.topics is disabled (=false)
>
> Execution:
>
> - Connector was created
> - Connector starts the heartbeat
> - Connector logs the following entry: [WARN] 2022-01-06 13:25:30,094
> [kafka-producer-network-thread |
> connector-producer-itgermany.pmops.dispoapp.gateway.DE-350.debeziumconnector-0]
> org.apache.kafka.clients.NetworkClient handleSuccessfulResponse - [Producer
> clientId=connector-producer-itgermany.pmops.dispoapp.gateway.DE-350.debeziumconnector-0]
> Error while fetching metadata with correlation id 38409 :
> {itgermany.pmops.dispoapp.gateway.heartbeat.GatewayDepot35=UNKNOWN_TOPIC_OR_PARTITION}
> - Connector status remains 'RUNNING'
> - NO Data comes to Kafka via the Connector
>
> Troubleshooting:
>
> - Re-creating the connector caused data to be sent to Kafka for a
> short time (until the heartbeat was repeated).
>
>
>
> People from RedHat told me that they are just passing the topic name and
> the message to Kafka and they do not receive a correct response
>
>
>
>
>
> Kind Regards / Mit freundlichen Grüßen
>
> Andreas Gillmann
> Product Management Operations
> IT GLS Germany/International
>
> GLS IT Services GmbH
> GLS Germany-Straße 1-7
> 36286 Neuenstein
> Germany
>
> LinkedIn <https://www.linkedin.com/company/gls-germany>
>
> Twitter <http://www.twitter.com/GLS_Germany>
>
> Facebook <http://facebook.com/GLSGermany>
>
> Instagram <https://www.instagram.com/glsgermany/>
>
>
>
>
>
>
>
>
>
> *t*
>
> +49 (0) 66 77 17 437
>
>
>
> *m*
>
> +49 (0) 172 1781 437
>
>
>
> *e*
>
> andreas.gillmann@gls-itservices.com
>
>
>
> *w*
>
> www.gls-group.com
>
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------
> GLS IT Services GmbH
> Sitz: Neuenstein, Amtsgericht Bad Hersfeld HRB 388, Geschäftsführer:
> Thorsten Pruin
> ------------------------------
>