Kafka

Sorry, I just meant mesh in the generic sense. A topology where every node is directly connected to every other node is sometimes called a "fully-connected mesh topology". In this context, I mean that you can set up a replication topology where every cluster is replicated directly to every other cluster, which is what you're after, I think. Ryanne On Mon, Jan 31, 2022, 2:18 PM Doug Whitfield < dwhitfield@perforce.com > wrote: > Hi Ryanne, > > I think you are probably correct, but just for clarity, you are talking > about a data mesh, not a service mesh, correct? > > Best Regards, > -- > > Doug Whitfield | Enterprise Architect, OpenLogic< > https://www.openlogic.com/?utm_leadsource=email-signature&utm_source=outlook-direct-email&utm_medium=email&utm_campaign=2019-common&utm_content=email-signature-link > > > Perforce Software< > http://www.perforce.com/?utm_leadsource=email-s...

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 < andreas.gillmann@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 < showuon@gmail.com > > Gesendet: Sonntag, 30. Januar 2022 10:04 > An: Kafka Users < users@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 ...

On Monday, January 31, 2022, Chad Preisler < chad.preisler@gmail.com > wrote: > Hello, > > I got this from the JavaDocs for KafkaConsumer. > > * If a consumer is assigned multiple partitions to fetch data from, it > will try to consume from all of them at the same time, > * effectively giving these partitions the same priority for consumption. > However in some cases consumers may want to > * first focus on fetching from some subset of the assigned partitions at > full speed, and only start fetching other partitions > * when these partitions have few or no data to consume. > > * One of such cases is stream processing, where processor fetches from two > topics and performs the join on these two streams. > * When one of the topics is long lagging behind the other, the processor > would like to pause fetching from the ahead topic > * in order to get the lagging stream to catch up. Another example is > b...

Hello, I got this from the JavaDocs for KafkaConsumer. * If a consumer is assigned multiple partitions to fetch data from, it will try to consume from all of them at the same time, * effectively giving these partitions the same priority for consumption. However in some cases consumers may want to * first focus on fetching from some subset of the assigned partitions at full speed, and only start fetching other partitions * when these partitions have few or no data to consume. * One of such cases is stream processing, where processor fetches from two topics and performs the join on these two streams. * When one of the topics is long lagging behind the other, the processor would like to pause fetching from the ahead topic * in order to get the lagging stream to catch up. Another example is bootstraping upon consumer starting up where there are * a lot of history data to catch up, the applications usually want to get the latest data on some of the topics befor...

just want to understand that you are talking about below scenario Mirroring data between A <----->B and B<---->C correct ? ________________________________ From: Doug Whitfield < dwhitfield@perforce.com > Sent: Monday, January 31, 2022 2:18 PM To: users@kafka.apache.org < users@kafka.apache.org > Subject: Re: Is it possible to run MirrorMaker in active/active/active? [External] Hi Ryanne, I think you are probably correct, but just for clarity, you are talking about a data mesh, not a service mesh, correct? Best Regards, -- Doug Whitfield | Enterprise Architect, OpenLogic< https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.openlogic.com%2F%3Futm_leadsource%3Demail-signature%26utm_source%3Doutlook-direct-email%26utm_medium%3Demail%26utm_campaign%3D2019-common%26utm_content%3Demail-signature-link&amp;data=04%7C01%7CManoj.Agrawal2%40cognizant.com%7Ca2b9fb3597504e0fcecf08d9e4f6d453%7Cde08c40719b9427d9fe8edf25430...

Hi Ryanne, I think you are probably correct, but just for clarity, you are talking about a data mesh, not a service mesh, correct? Best Regards, -- Doug Whitfield | Enterprise Architect, OpenLogic< https://www.openlogic.com/?utm_leadsource=email-signature&utm_source=outlook-direct-email&utm_medium=email&utm_campaign=2019-common&utm_content=email-signature-link > Perforce Software< http://www.perforce.com/?utm_leadsource=email-signature&utm_source=outlook-direct-email&utm_medium=email&utm_campaign=2019-common&utm_content=email-signature-link > Visit us on: LinkedIn< https://www.linkedin.com/company/perforce?utm_leadsource=email-signature&utm_source=outlook-direct-email&utm_medium=email&utm_campaign=2019-common&utm_content=email-signature-link > | Twitter< https://twitter.com/perforce?utm_leadsource=email-signature&utm_source=outlook-direct-email&utm_medium=email&utm_campaign=2019-common&utm_...

Doug, you can have any number of clusters with a fully-connected mesh topology, which I think is what you are looking for. Ryanne On Mon, Jan 31, 2022, 12:44 PM Doug Whitfield < dwhitfield@perforce.com > wrote: > Hi folks, > > Every example I have seen uses two clusters in active/active and testing > suggests I can only get two clusters to run active/active. > > I think we will need to use a fan-in pattern if we want more than two > clusters. Is that correct? > > Best Regards, > -- > > Doug Whitfield | Enterprise Architect, OpenLogic< > https://www.openlogic.com/?utm_leadsource=email-signature&utm_source=outlook-direct-email&utm_medium=email&utm_campaign=2019-common&utm_content=email-signature-link > > > Perforce Software< > http://www.perforce.com/?utm_leadsource=email-signature&utm_source=outlook-direct-email&utm_medium=email&utm_campaign=2019-common&utm_content=e...

Hi folks, Every example I have seen uses two clusters in active/active and testing suggests I can only get two clusters to run active/active. I think we will need to use a fan-in pattern if we want more than two clusters. Is that correct? Best Regards, -- Doug Whitfield | Enterprise Architect, OpenLogic< https://www.openlogic.com/?utm_leadsource=email-signature&utm_source=outlook-direct-email&utm_medium=email&utm_campaign=2019-common&utm_content=email-signature-link > Perforce Software< http://www.perforce.com/?utm_leadsource=email-signature&utm_source=outlook-direct-email&utm_medium=email&utm_campaign=2019-common&utm_content=email-signature-link > Visit us on: LinkedIn< https://www.linkedin.com/company/perforce?utm_leadsource=email-signature&utm_source=outlook-direct-email&utm_medium=email&utm_campaign=2019-common&utm_content=email-signature-link > | Twitter< https://twitter.com/perforce?utm_leadsource...

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 < andreas.gillmann@gls-itservices.com > Date: Monday, January 31, 2022 at 4:34 AM To: users@kafka.apache.org < users@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 < showuon@gmail.com > Gesendet: Sonntag, 30. Januar 2022 10:04 An: Kafka Users < users@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...

Hello Luke, yes I will do so, but please tell me, what is a PR? Regards, Andreas -----Ursprüngliche Nachricht----- Von: Luke Chen < showuon@gmail.com > Gesendet: Sonntag, 30. Januar 2022 10:04 An: Kafka Users < users@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.topi...

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-net...

Excellent Luke I will take a look shortly On Fri, Jan 28, 2022 at 11:12 PM Luke Chen < showuon@gmail.com > wrote: > Hi Israel and all, > > The PR to add CVE-2022-23302 > < https://github.com/advisories/GHSA-w9p3-5cr8-m3jj > and CVE-2022-23305 > < https://github.com/advisories/GHSA-65fg-84f6-3jq3 > is here: > https://github.com/apache/kafka-site/pull/396 > > Welcome to review. > > Thank you. > Luke > > On Sat, Jan 29, 2022 at 11:22 AM Israel Ekpo < israelekpo@gmail.com > wrote: > > > Thanks Luke for the prompt response > > > > +1 on the PR for the CVE page update > > > > You can cc me on the PR when it's ready and I will take a look at it > > > > Thanks > > > > On Fri, Jan 28, 2022 at 9:44 PM Luke Chen < showuon@gmail.com > wrote: > > > > > Hi Karupasamy, > > > > > > Thanks for your aski...

Hi Israel and all, The PR to add CVE-2022-23302 < https://github.com/advisories/GHSA-w9p3-5cr8-m3jj > and CVE-2022-23305 < https://github.com/advisories/GHSA-65fg-84f6-3jq3 > is here: https://github.com/apache/kafka-site/pull/396 Welcome to review. Thank you. Luke On Sat, Jan 29, 2022 at 11:22 AM Israel Ekpo < israelekpo@gmail.com > wrote: > Thanks Luke for the prompt response > > +1 on the PR for the CVE page update > > You can cc me on the PR when it's ready and I will take a look at it > > Thanks > > On Fri, Jan 28, 2022 at 9:44 PM Luke Chen < showuon@gmail.com > wrote: > > > Hi Karupasamy, > > > > Thanks for your asking. Answering your question below: > > > > > 1. Are the CVEs *CVE-2022-23302, CVE-2022-23305* applicable to the > Apache > > Kafka? > > > > Unfortunately, yes, these 2 CVEs: *CVE-2022-23302, CVE-2022-23305* are > also...