Re: [VOTE] KIP-927: Improve the kafka-metadata-quorum output

[John Roesler]

I’m +1 (binding)

Thanks, Federico!

It looks like a nice improvement to me. 

-John


On Sat, May 20, 2023, at 09:16, Kamal Chandraprakash wrote:
> +1 (non binding)
>
> On Wed, May 17, 2023 at 3:22 AM Divij Vaidya 
> wrote:
>
>> +1 (non binding)
>>
>> Divij Vaidya
>>
>>
>>
>> On Tue, May 16, 2023 at 4:35 AM ziming deng 
>> wrote:
>>
>> > Thanks for this improvement, +1 from me(binging)
>> >
>> > —
>> > Best,
>> > Ziming
>> >
>> > > On May 16, 2023, at 00:43, Federico Valeri 
>> wrote:
>> > >
>> > > Hi all,
>> > >
>> > > I'd like to start a vote on KIP-927: Improve the kafka-metadata-quorum
>> > output.
>> > >
>> > >
>> >
>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-927%3A+Improve+the+kafka-metadata-quorum+output
>> > >
>> > > Discussion thread:
>> > > https://lists.apache.org/thread/pph59hxvz5jkk709x53p44xrpdqwv8qc
>> > >
>> > > Thanks
>> > > Fede
>> >
>> >
>>

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #1856

[Apache Jenkins Server]

See 


Changes:


--
[...truncated 569407 lines...]
[2023-05-20T19:36:10.576Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 182 > RestoreIntegrationTest > 
shouldProcessDataFromStoresWithLoggingDisabled(boolean) > [2] false STARTED
[2023-05-20T19:36:10.576Z] 
[2023-05-20T19:36:10.576Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 182 > RestoreIntegrationTest > 
shouldProcessDataFromStoresWithLoggingDisabled(boolean) > [2] false PASSED
[2023-05-20T19:36:10.576Z] 
[2023-05-20T19:36:10.576Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 182 > RestoreIntegrationTest > shouldRestoreNullRecord() STARTED
[2023-05-20T19:36:35.739Z] 
[2023-05-20T19:36:35.739Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 179 > RestoreIntegrationTest > shouldRestoreNullRecord() PASSED
[2023-05-20T19:36:35.739Z] 
[2023-05-20T19:36:35.739Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 179 > RestoreIntegrationTest > 
shouldRestoreStateFromSourceTopic(boolean) > [1] true STARTED
[2023-05-20T19:36:35.739Z] 
[2023-05-20T19:36:35.739Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 179 > RestoreIntegrationTest > 
shouldRestoreStateFromSourceTopic(boolean) > [1] true PASSED
[2023-05-20T19:36:35.739Z] 
[2023-05-20T19:36:35.739Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 179 > RestoreIntegrationTest > 
shouldRestoreStateFromSourceTopic(boolean) > [2] false STARTED
[2023-05-20T19:36:37.718Z] 
[2023-05-20T19:36:37.718Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 179 > RestoreIntegrationTest > 
shouldRestoreStateFromSourceTopic(boolean) > [2] false PASSED
[2023-05-20T19:36:37.718Z] 
[2023-05-20T19:36:37.718Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 179 > RestoreIntegrationTest > 
shouldSuccessfullyStartWhenLoggingDisabled(boolean) > [1] true STARTED
[2023-05-20T19:36:39.480Z] 
[2023-05-20T19:36:39.480Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 179 > RestoreIntegrationTest > 
shouldSuccessfullyStartWhenLoggingDisabled(boolean) > [1] true PASSED
[2023-05-20T19:36:39.480Z] 
[2023-05-20T19:36:39.480Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 179 > RestoreIntegrationTest > 
shouldSuccessfullyStartWhenLoggingDisabled(boolean) > [2] false STARTED
[2023-05-20T19:36:41.243Z] 
[2023-05-20T19:36:41.243Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 179 > RestoreIntegrationTest > 
shouldSuccessfullyStartWhenLoggingDisabled(boolean) > [2] false PASSED
[2023-05-20T19:36:41.243Z] 
[2023-05-20T19:36:41.243Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 179 > RestoreIntegrationTest > 
shouldRestoreStateFromChangelogTopic(boolean) > [1] true STARTED
[2023-05-20T19:36:43.983Z] 
[2023-05-20T19:36:43.983Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 179 > RestoreIntegrationTest > 
shouldRestoreStateFromChangelogTopic(boolean) > [1] true PASSED
[2023-05-20T19:36:43.983Z] 
[2023-05-20T19:36:43.983Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 179 > RestoreIntegrationTest > 
shouldRestoreStateFromChangelogTopic(boolean) > [2] false STARTED
[2023-05-20T19:36:47.750Z] 
[2023-05-20T19:36:47.750Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 179 > RestoreIntegrationTest > 
shouldRestoreStateFromChangelogTopic(boolean) > [2] false PASSED
[2023-05-20T19:36:51.348Z] 
[2023-05-20T19:36:51.348Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 179 > SmokeTestDriverIntegrationTest > 
shouldWorkWithRebalance(boolean) > [1] true STARTED
[2023-05-20T19:37:00.840Z] 
[2023-05-20T19:37:00.840Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 182 > RestoreIntegrationTest > shouldRestoreNullRecord() PASSED
[2023-05-20T19:37:00.840Z] 
[2023-05-20T19:37:00.840Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 182 > RestoreIntegrationTest > 
shouldRestoreStateFromSourceTopic(boolean) > [1] true STARTED
[2023-05-20T19:37:03.827Z] 
[2023-05-20T19:37:03.827Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 182 > RestoreIntegrationTest > 
shouldRestoreStateFromSourceTopic(boolean) > [1] true PASSED
[2023-05-20T19:37:03.827Z] 
[2023-05-20T19:37:03.827Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 182 > RestoreIntegrationTest > 
shouldRestoreStateFromSourceTopic(boolean) > [2] false STARTED
[2023-05-20T19:37:08.915Z] 
[2023-05-20T19:37:08.915Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 182 > RestoreIntegrationTest > 
shouldRestoreStateFromSourceTopic(boolean) > [2] false PASSED
[2023-05-20T19:37:08.915Z] 
[2023-05-20T19:37:08.915Z] Gradle Test Run :streams:integrationTest > Gradle 
Test Executor 182 > RestoreIntegrationTest > 

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.4 #134

[Apache Jenkins Server]

See 

Re: [DISCUSS] Apache Kafka 3.5.0 release

[Ismael Juma]

Hi Mickael,

What's the plan for the first RC? In my opinion, we should really tighten
the criteria for what's considered a blocker and release RC0 soon (given
where we are timeline wise).

Ismael

On Sat, May 20, 2023, 8:15 AM Mickael Maison 
wrote:

> Hi Matthias,
>
> Yes feel free to backport to 3.5.
>
> Thanks,
> Mickael
>
> On Sat, May 20, 2023 at 12:53 AM Akhilesh Chaganti
>  wrote:
> >
> > Hi Mickael,
> >
> > I raised the blockers for AK 3.5 and raised PRs for them. All of them are
> > in the Zk -> KRaft migration path and critical for the Zk -> KRaft
> > migration to be successful.
> > KAFKA-15003  -- Topic
> > metadata is not correctly synced with Zookeeper while handling snapshot
> > during migration (dual write). --
> > KAFKA-15004  --
> Config
> > changes are not correctly synced with Zookeeper whale handling snapshot
> > during migration (dual write). --
> > KAFKA-15007  --
> > MigrationPropagator may have wrong IBP while sending UMR, LISR requests
> to
> > the Zk Brokers during migration. --
> >
> >
> > Thanks
> > Akhilesh
> >
> >
> > On Fri, May 19, 2023 at 9:28 AM Matthias J. Sax 
> wrote:
> >
> > > Mickael,
> > >
> > > we included a bug-fix into 3.5, and just discovered a critical bug in
> > > the fix itself, that would introduce a regression into 3.5.
> > >
> > > We have already a PR to fix-forward:
> > > https://github.com/apache/kafka/pull/13734
> > >
> > > As we don't have an RC yet, I would like to cherry-pick this back to
> 3.5.
> > >
> > >
> > > -Matthias
> > >
> > > On 5/10/23 1:47 PM, Sophie Blee-Goldman wrote:
> > > > Thanks Mickael -- the fix has been merged to 3.5 now
> > > >
> > > > On Wed, May 10, 2023 at 1:12 AM Mickael Maison <
> mickael.mai...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > >> Hi Sophie,
> > > >>
> > > >> Yes that's fine, thanks for letting me know!
> > > >>
> > > >> Mickael
> > > >>
> > > >> On Tue, May 9, 2023 at 10:54 PM Sophie Blee-Goldman
> > > >>  wrote:
> > > >>>
> > > >>> Hey Mickael, I noticed a bug in the new versioned key-value byte
> store
> > > >>> where it's delegating to the wrong API
> > > >>> (copy/paste error I assume). I extracted this into its own PR
> which I
> > > >> think
> > > >>> should be included in the 3.5 release.
> > > >>>
> > > >>> The tests are still running, but it's just a one-liner so I'll
> merge it
> > > >>> when they're done, and cherrypick to 3.5 if
> > > >>> that's ok with you. See https://github.com/apache/kafka/pull/13695
> > > >>>
> > > >>> Thanks for running the release!
> > > >>>
> > > >>> On Tue, May 9, 2023 at 1:28 PM Randall Hauch 
> wrote:
> > > >>>
> > >  Thanks, Mickael.
> > > 
> > >  I've cherry-picked that commit to the `3.5` branch (
> > >  https://issues.apache.org/jira/browse/KAFKA-14974).
> > > 
> > >  Best regards,
> > >  Randall
> > > 
> > >  On Tue, May 9, 2023 at 2:13 PM Mickael Maison <
> > > >> mickael.mai...@gmail.com>
> > >  wrote:
> > > 
> > > > Hi Randall/Luke,
> > > >
> > > > Yes you can go ahead and merge these into 3.5. I've not started
> > > >> making
> > > > a release yet because:
> > > > - I found a regression today in MirrorMaker:
> > > > https://issues.apache.org/jira/browse/KAFKA-14980
> > > > - The 3.5 branch builder job in Jenkins has been disabled:
> > > > https://issues.apache.org/jira/browse/INFRA-24577
> > > >
> > > > Thanks,
> > > > Mickael
> > > >
> > > > On Tue, May 9, 2023 at 8:40 PM Luke Chen 
> wrote:
> > > >>
> > > >> Hi Mickael,
> > > >>
> > > >> Since we haven't had the CR created yet, I'm thinking we should
> > >  backport
> > > >> this doc improvement to v3.5.0 to make the doc complete.
> > > >> https://github.com/apache/kafka/pull/13660
> > > >>
> > > >> What do you think?
> > > >>
> > > >> Luke
> > > >>
> > > >> On Sat, May 6, 2023 at 11:31 PM David Arthur 
> > > >> wrote:
> > > >>
> > > >>> I resolved these three:
> > > >>> * KAFKA-14840 is merged to trunk and 3.5. I removed the 3.4.1
> fix
> > > > version
> > > >>> * KAFKA-14805 is merged to trunk and 3.5
> > > >>> * KAFKA-14918 is merged to trunk and 3.5
> > > >>>
> > > >>> KAFKA-14692 (docs issue) is still a not done
> > > >>>
> > > >>> Looks like KAFKA-14084 is now resolved as well (it's in trunk
> and
> > >  3.5).
> > > >>>
> > > >>> I'll try to find out about KAFKA-14698, I think it's likely a
> > >  WONTFIX.
> > > >>>
> > > >>> -David
> > > >>>
> > > >>> On Fri, May 5, 2023 at 10:43 AM Mickael Maison <
> > > > mickael.mai...@gmail.com>
> > > >>> wrote:
> > > >>>
> > >  Hi David,
> > > 
> > >  Thanks for the update!
> > >  You still own 4 other tickets targeting 3.5: KAFKA-14840,
> > > > 

Re: [DISCUSS] Apache Kafka 3.5.0 release

[Mickael Maison]

Hi Matthias,

Yes feel free to backport to 3.5.

Thanks,
Mickael

On Sat, May 20, 2023 at 12:53 AM Akhilesh Chaganti
 wrote:
>
> Hi Mickael,
>
> I raised the blockers for AK 3.5 and raised PRs for them. All of them are
> in the Zk -> KRaft migration path and critical for the Zk -> KRaft
> migration to be successful.
> KAFKA-15003  -- Topic
> metadata is not correctly synced with Zookeeper while handling snapshot
> during migration (dual write). --
> KAFKA-15004  -- Config
> changes are not correctly synced with Zookeeper whale handling snapshot
> during migration (dual write). --
> KAFKA-15007  --
> MigrationPropagator may have wrong IBP while sending UMR, LISR requests to
> the Zk Brokers during migration. --
>
>
> Thanks
> Akhilesh
>
>
> On Fri, May 19, 2023 at 9:28 AM Matthias J. Sax  wrote:
>
> > Mickael,
> >
> > we included a bug-fix into 3.5, and just discovered a critical bug in
> > the fix itself, that would introduce a regression into 3.5.
> >
> > We have already a PR to fix-forward:
> > https://github.com/apache/kafka/pull/13734
> >
> > As we don't have an RC yet, I would like to cherry-pick this back to 3.5.
> >
> >
> > -Matthias
> >
> > On 5/10/23 1:47 PM, Sophie Blee-Goldman wrote:
> > > Thanks Mickael -- the fix has been merged to 3.5 now
> > >
> > > On Wed, May 10, 2023 at 1:12 AM Mickael Maison  > >
> > > wrote:
> > >
> > >> Hi Sophie,
> > >>
> > >> Yes that's fine, thanks for letting me know!
> > >>
> > >> Mickael
> > >>
> > >> On Tue, May 9, 2023 at 10:54 PM Sophie Blee-Goldman
> > >>  wrote:
> > >>>
> > >>> Hey Mickael, I noticed a bug in the new versioned key-value byte store
> > >>> where it's delegating to the wrong API
> > >>> (copy/paste error I assume). I extracted this into its own PR which I
> > >> think
> > >>> should be included in the 3.5 release.
> > >>>
> > >>> The tests are still running, but it's just a one-liner so I'll merge it
> > >>> when they're done, and cherrypick to 3.5 if
> > >>> that's ok with you. See https://github.com/apache/kafka/pull/13695
> > >>>
> > >>> Thanks for running the release!
> > >>>
> > >>> On Tue, May 9, 2023 at 1:28 PM Randall Hauch  wrote:
> > >>>
> >  Thanks, Mickael.
> > 
> >  I've cherry-picked that commit to the `3.5` branch (
> >  https://issues.apache.org/jira/browse/KAFKA-14974).
> > 
> >  Best regards,
> >  Randall
> > 
> >  On Tue, May 9, 2023 at 2:13 PM Mickael Maison <
> > >> mickael.mai...@gmail.com>
> >  wrote:
> > 
> > > Hi Randall/Luke,
> > >
> > > Yes you can go ahead and merge these into 3.5. I've not started
> > >> making
> > > a release yet because:
> > > - I found a regression today in MirrorMaker:
> > > https://issues.apache.org/jira/browse/KAFKA-14980
> > > - The 3.5 branch builder job in Jenkins has been disabled:
> > > https://issues.apache.org/jira/browse/INFRA-24577
> > >
> > > Thanks,
> > > Mickael
> > >
> > > On Tue, May 9, 2023 at 8:40 PM Luke Chen  wrote:
> > >>
> > >> Hi Mickael,
> > >>
> > >> Since we haven't had the CR created yet, I'm thinking we should
> >  backport
> > >> this doc improvement to v3.5.0 to make the doc complete.
> > >> https://github.com/apache/kafka/pull/13660
> > >>
> > >> What do you think?
> > >>
> > >> Luke
> > >>
> > >> On Sat, May 6, 2023 at 11:31 PM David Arthur 
> > >> wrote:
> > >>
> > >>> I resolved these three:
> > >>> * KAFKA-14840 is merged to trunk and 3.5. I removed the 3.4.1 fix
> > > version
> > >>> * KAFKA-14805 is merged to trunk and 3.5
> > >>> * KAFKA-14918 is merged to trunk and 3.5
> > >>>
> > >>> KAFKA-14692 (docs issue) is still a not done
> > >>>
> > >>> Looks like KAFKA-14084 is now resolved as well (it's in trunk and
> >  3.5).
> > >>>
> > >>> I'll try to find out about KAFKA-14698, I think it's likely a
> >  WONTFIX.
> > >>>
> > >>> -David
> > >>>
> > >>> On Fri, May 5, 2023 at 10:43 AM Mickael Maison <
> > > mickael.mai...@gmail.com>
> > >>> wrote:
> > >>>
> >  Hi David,
> > 
> >  Thanks for the update!
> >  You still own 4 other tickets targeting 3.5: KAFKA-14840,
> > > KAFKA-14805,
> >  KAFKA-14918, KAFKA-14692. Should I move all of them to the next
> >  release?
> >  Also KAFKA-14698 and KAFKA-14084 are somewhat related to the
> >  migration. Should I move them too?
> > 
> >  Thanks,
> >  Mickael
> > 
> >  On Fri, May 5, 2023 at 4:27 PM David Arthur
> >   wrote:
> > >
> > > Hey Mickael, my two ZK migration fixes are in 3.5 now.
> > >
> > > Cheers,
> > > David
> > >
> > > On Fri, May 5, 2023 at 9:37 AM Mickael 

Re: [VOTE] KIP-927: Improve the kafka-metadata-quorum output

[Kamal Chandraprakash]

+1 (non binding)

On Wed, May 17, 2023 at 3:22 AM Divij Vaidya 
wrote:

> +1 (non binding)
>
> Divij Vaidya
>
>
>
> On Tue, May 16, 2023 at 4:35 AM ziming deng 
> wrote:
>
> > Thanks for this improvement, +1 from me(binging)
> >
> > —
> > Best,
> > Ziming
> >
> > > On May 16, 2023, at 00:43, Federico Valeri 
> wrote:
> > >
> > > Hi all,
> > >
> > > I'd like to start a vote on KIP-927: Improve the kafka-metadata-quorum
> > output.
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-927%3A+Improve+the+kafka-metadata-quorum+output
> > >
> > > Discussion thread:
> > > https://lists.apache.org/thread/pph59hxvz5jkk709x53p44xrpdqwv8qc
> > >
> > > Thanks
> > > Fede
> >
> >
>

Re: Re: [DISCUSS] Cluster Linking / Cross-Cluster Replication - Call for Interest & Co-Authors

[hudeqi]

Hi, I am also very excited to see this discussion, because I also implemented 
the "federation model" based on the kafka-0.10.2.1 version before in company 
and got benefits from going online. It solves the problem of seamlessly 
migrating the bytesIn/bytesOut of a topic to another kafka cluster without the 
client being aware. Therefore, it includes the cross-cluster synchronous topic 
data mentioned in this discussion, and ensures the consistency of the offset. 
It also provides the global coordinator service to ensure the consistency of 
the group offset, and the metadata service to ensure that the client is visible 
of the real traffic cluster of the topic. So I am very excited to see that the 
community has finally discussed this feature, and I especially hope to 
participate in the development and reviewer of this feature as a co-author.


 -原始邮件-
 发件人: "Chia-Ping Tsai" 
 发送时间: 2023-05-20 18:57:31 (星期六)
 收件人: dev@kafka.apache.org
 抄送: t...@conduktor.io.invalid
 主题: Re: [DISCUSS] Cluster Linking / Cross-Cluster Replication - Call for 
Interest  Co-Authors
 

Re: [DISCUSS] Cluster Linking / Cross-Cluster Replication - Call for Interest & Co-Authors

[Chia-Ping Tsai]

Hi Greg

I do love this feature/discussion :)

I’d like to not only be a co-author/reviewer but also sponsor this feature by 
requesting our employees to be the contributors.

Thanks!

Chia-Ping

> Luke Chen  於 2023年5月20日 下午6:47 寫道：
> 
> Hi Greg,
> 
> Thanks for starting this discussion. Yes, this is definitely a valuable
> feature. I'd be willing to volunteer for co-author and reviewer or anything
> else I can help. Hope we can make it happen!
> 
> Thank you!
> Luke
> 
> 
> Thomas Scott  於 2023年5月20日 週六 上午6:34 寫道：
> 
>> Hi Greg,
>> 
>>  This sounds very interesting and I think it is a very valuable feature.
>> I'd like to volunteer in any way I can be useful and am more than happy to
>> help with co authoring KIPs and implementation.
>> 
>> 
>> Thanks
>> 
>>  Tom
>> 
>> 
>> 
>> 
>> On Fri, 19 May 2023, 23:15 Colt McNealy,  wrote:
>> 
>>> I'm highly interested in this feature. We are a startup right now so we
>>> can't commit resources to help *yet*, but once we are off the ground in
>> 1-2
>>> years it would be cool to contribute to this.
>>> 
>>> Colt McNealy
>>> *Founder, LittleHorse.dev*
>>> 
>>> 
>>> On Fri, May 19, 2023 at 10:14 AM hzh0425  wrote:
>>> 
 Hi, Grep Harris.
 When I saw this discussion, I was very excited.
 My team is a Kafka R team, currently planning research and
>> development
 on cluster linking. We believe that it is of great value in scenarios
>>> such
 as multi region disaster recovery and cross cloud synchronization.
 Therefore, I hope to join the subsequent design and development of this
 KIP as a co-author for deep participation.
 
 Thanks!
 hzh
 
 
 
 
 
  回复的原邮件 
 | 发件人 | Greg Harris |
 | 日期 | 2023年05月20日 00:56 |
 | 收件人 | dev@kafka.apache.org |
 | 抄送至 | |
 | 主题 | [DISCUSS] Cluster Linking / Cross-Cluster Replication - Call for
 Interest & Co-Authors |
 Hey all,
 
 I have heard some offline discussion around Cross-Cluster Replication,
 a feature which would enable data to be shared between Kafka clusters
 in a manner which preserves offsets.
 Other names for this feature may include "Cluster Linking", "Remote
 Topics", "Byte-for-Byte Mirroring", and similar.
 I believe that there may be an interest in this feature being added to
 Apache Kafka, but have not seen any mailing list activity to that
 effect yet.
 
 Due to the complexity of the feature, I think it is appropriate to
 gauge the interest in the feature before opening a KIP, and also
 gather a set of contributors which are interested in collaborating on
 and sponsoring its development.
 
 If you are a Kafka user, please:
 1. Let us know in this thread if you think Cross-Cluster Replication
 is a valuable feature and would like to see it in Apache Kafka.
 
 If you are or want to be an individual contributor, please:
 1. Discuss with your users and/or product organization if
 Cross-Cluster Replication is appealing, and summarize their level of
 interest in the below thread.
 2. Consider volunteering in this thread as a reviewer or co-author of
 the KIP and subsequent implementation. Co-authors would share the
 design and implementation workload as their time and interest permits.
 3. If you have an employer, request that they sponsor this feature
 through your full- or part-time contributions as a reviewer or
 co-author. In exchange for their sponsorship, they can help ensure
 that the feature is delivered with a more predictable timeline.
 
 Please save your technical expectations and details of this feature
 for a subsequent KIP and DISCUSS thread, where that discussion is more
 appropriate.
 
 Thanks Everyone!
 
 Greg Harris
 Aiven, Inc
 
>>> 
>> 

Re: [DISCUSS] Cluster Linking / Cross-Cluster Replication - Call for Interest & Co-Authors

[Luke Chen]

Hi Greg,

Thanks for starting this discussion. Yes, this is definitely a valuable
feature. I'd be willing to volunteer for co-author and reviewer or anything
else I can help. Hope we can make it happen!

Thank you!
Luke


Thomas Scott  於 2023年5月20日 週六 上午6:34 寫道：

> Hi Greg,
>
>   This sounds very interesting and I think it is a very valuable feature.
> I'd like to volunteer in any way I can be useful and am more than happy to
> help with co authoring KIPs and implementation.
>
>
> Thanks
>
>   Tom
>
>
>
>
> On Fri, 19 May 2023, 23:15 Colt McNealy,  wrote:
>
> > I'm highly interested in this feature. We are a startup right now so we
> > can't commit resources to help *yet*, but once we are off the ground in
> 1-2
> > years it would be cool to contribute to this.
> >
> > Colt McNealy
> > *Founder, LittleHorse.dev*
> >
> >
> > On Fri, May 19, 2023 at 10:14 AM hzh0425  wrote:
> >
> > > Hi, Grep Harris.
> > > When I saw this discussion, I was very excited.
> > > My team is a Kafka R team, currently planning research and
> development
> > > on cluster linking. We believe that it is of great value in scenarios
> > such
> > > as multi region disaster recovery and cross cloud synchronization.
> > > Therefore, I hope to join the subsequent design and development of this
> > > KIP as a co-author for deep participation.
> > >
> > > Thanks!
> > > hzh
> > >
> > >
> > >
> > >
> > >
> > >  回复的原邮件 
> > > | 发件人 | Greg Harris |
> > > | 日期 | 2023年05月20日 00:56 |
> > > | 收件人 | dev@kafka.apache.org |
> > > | 抄送至 | |
> > > | 主题 | [DISCUSS] Cluster Linking / Cross-Cluster Replication - Call for
> > > Interest & Co-Authors |
> > > Hey all,
> > >
> > > I have heard some offline discussion around Cross-Cluster Replication,
> > > a feature which would enable data to be shared between Kafka clusters
> > > in a manner which preserves offsets.
> > > Other names for this feature may include "Cluster Linking", "Remote
> > > Topics", "Byte-for-Byte Mirroring", and similar.
> > > I believe that there may be an interest in this feature being added to
> > > Apache Kafka, but have not seen any mailing list activity to that
> > > effect yet.
> > >
> > > Due to the complexity of the feature, I think it is appropriate to
> > > gauge the interest in the feature before opening a KIP, and also
> > > gather a set of contributors which are interested in collaborating on
> > > and sponsoring its development.
> > >
> > > If you are a Kafka user, please:
> > > 1. Let us know in this thread if you think Cross-Cluster Replication
> > > is a valuable feature and would like to see it in Apache Kafka.
> > >
> > > If you are or want to be an individual contributor, please:
> > > 1. Discuss with your users and/or product organization if
> > > Cross-Cluster Replication is appealing, and summarize their level of
> > > interest in the below thread.
> > > 2. Consider volunteering in this thread as a reviewer or co-author of
> > > the KIP and subsequent implementation. Co-authors would share the
> > > design and implementation workload as their time and interest permits.
> > > 3. If you have an employer, request that they sponsor this feature
> > > through your full- or part-time contributions as a reviewer or
> > > co-author. In exchange for their sponsorship, they can help ensure
> > > that the feature is delivered with a more predictable timeline.
> > >
> > > Please save your technical expectations and details of this feature
> > > for a subsequent KIP and DISCUSS thread, where that discussion is more
> > > appropriate.
> > >
> > > Thanks Everyone!
> > >
> > > Greg Harris
> > > Aiven, Inc
> > >
> >
>

[GitHub] [kafka-site] omkreddy merged pull request #512: MINOR: Add System Properties to config documentation section

[via GitHub]

omkreddy merged PR #512:
URL: https://github.com/apache/kafka-site/pull/512


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org