t; > > Hi Patrik,
> > >
> > > Sorry for the delay, I've been on PTO. LGTM! +1 (binding)
> > >
> > > Cheers,
> > >
> > > Chris
> > >
> > > On Tue, Sep 3, 2024 at 5:10 AM Viktor Somogyi-Vass
> > > wrote:
>
Ok, sorry for the noise. It seems like my setup was incorrectly configured,
one controller had an incorrect voters config and that caused the issue.
Retested it and it works now.
But given this, I might as well just give a +1. :)
On Wed, Nov 6, 2024 at 2:53 PM Viktor Somogyi-Vass <
viktor.s
[
https://issues.apache.org/jira/browse/KAFKA-17950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viktor Somogyi-Vass resolved KAFKA-17950.
-
Resolution: Invalid
Ok, my mistake. It seems like an incorrect voter list
Viktor Somogyi-Vass created KAFKA-17950:
---
Summary: The leader requested truncation to below the current high
watermark
Key: KAFKA-17950
URL: https://issues.apache.org/jira/browse/KAFKA-17950
Hey All,
It seems like I ran into an issue. While trying to do the migration (3.9 ZK
-> 3.9 KRaft), at the very last step the whole cluster (except the
controller I just restarted) fails with a fatal error where a controller (I
think) requests a truncation that is below the HWM.
I tried to capture
Hi all,
I think it's a great idea to use a different configuration method
as default. Personally I'd prefer YAML as well because it's the most
concise and easy to read format.
1. This would establish two different config formats in Kafka. Properties
for kafka configs and YAML/XML/JSON for log con
ithout an
> actual,
> >>> > opposite flow being active - I think only users can tell if the
> reverse
> >>> > checkpointing should be active, and they should be the one opting in
> >>> for
> >>> > the higher resource usage.
> >>> >
> &g
Hey Dan,
I think this is a very useful idea. Two questions:
SVV1: Do you think we need the feature flag at all? I know that not having
this flag may technically render the KIP unnecessary (however it may still
be useful to discuss this topic and create a concensus). As you wrote in
the KIP, we ma
+1 (binding)
Thanks for this improvement. If you have a PR, you can ping me for review.
On Fri, Sep 27, 2024 at 4:07 PM Dániel Urbán wrote:
> Hi everyone,
>
> I would like to start a vote on KIP-1089: Allow disabling heartbeats
> replication in MirrorSourceConnector (
>
> https://cwiki.apache.o
he
> >> heartbeats topics. It can be a workaround to the issue described in the
> >> motivation, but I consider it to be more like a hack than a proper
> >> workaround.
> >>
> >> Thanks,
> >> Daniel
> >>
> >> Viktor Somogy
Congrats Kamal! :)
On Mon, Sep 30, 2024, 19:21 Matthias J. Sax wrote:
> Congrats!
>
> On 9/30/24 6:59 AM, Yash Mayya wrote:
> > Congratulations Kamal!
> >
> > On Mon, 30 Sept, 2024, 18:07 Luke Chen, wrote:
> >
> >> Hi all,
> >>
> >> The PMC of Apache Kafka is pleased to announce a new Kafka com
Hi Daniel,
As you describe the case, I think it could be a good idea potentially to
add this, however we have to note that customers can achieve this behavior
today by subclassing the default policy. This is more cumbersome though
than flipping a boolean though, perhaps we could add this to the re
Viktor Somogyi-Vass created KAFKA-17523:
---
Summary: Connectors should be able to override
offset.flush.interval.ms
Key: KAFKA-17523
URL: https://issues.apache.org/jira/browse/KAFKA-17523
Project
Hi Patrik,
Thanks for working on this. +1 from me (binding).
Best,
Viktor
On Wed, Aug 28, 2024 at 1:34 PM Patrik Marton
wrote:
> Hi all,
>
> As the proposal is finalized, and there was no new feedback in the past
> week, I would like to open voting for KIP-1074
> <
> https://cwiki.apache.org/c
Congrats Lianet!
On Thu, Aug 29, 2024 at 7:27 AM Yash Mayya wrote:
> Congratulations Lianet!
>
> On Wed, Aug 28, 2024 at 9:05 PM David Jacot wrote:
>
> > Hi all,
> >
> > The PMC of Apache Kafka is pleased to announce a new Kafka committer,
> > Lianet Magrans.
> >
> > Lianet has been a Kafka con
completed yet.
>
> So the main difference between Level 1 and 2 is that in level 1 the feature
> can't be used. In level 2 let's say the common flows are. Level 3 all flows
> (common and corner cases) are implemented.
>
> Does that make sense?
>
>
> Best,
>
Hi all,
A couple of additional questions/suggestions regarding the KIP:
VS1. Testing: you wrote about testing only on level 4 but I think we should
add some testing criteria to each one to ensure that it meets
those requirements specified by the given level and it is gradually more
mature. For in
a Ibrahim
> wrote:
> >>>
> >>> Hi All,
> >>>
> >>> I have a couple of notes to add
> >>>
> >>> OI-1.Regarding the proposed default regex in the KIP,
> >> "__.*|\\..*|.*-internal|.*\\.internal", when users w
ne-tuning the heartbeat emission interval
> > based
> > >> on the eventual target of the replication flow that will be reading
> from
> > >> the heartbeats topic.
> > >>
> > >> I don't raise the above to cast doubt on the KIP, really I'
#x27;d eventually get a KIP where someone
> > states that it's too hard to add topics one-by-one and would like to
> > include them by regex, prefix match, or some other broader mechanism.
> >
> > Do you find this convincing? I'm also curious what Greg and Patrik think.
&
Hi all,
I think there are a couple of other alternatives to discuss.
1. We may just simply change the internal topic naming to something like
"mm2internal" and provide upgrade functionality as well. In this scenario
we wouldn't need to tinker with the prefixes or the naming patterns, we
just simp
ume
> directly from the topic if they'd like to know the history of the worker.
> Overall it seems like a decent idea and I'd be happy to review a KIP for
> it, but like you mention, it seems like a pretty drastic change in scope
> and I don't think it needs to be include
Hi Chris,
I also have 2 other comments:
1. One more thing I came across is that should we provide the Retry-After
header in the response in case of 503 response? Although I'm not sure how
many clients honor this, we could add it just in case some does and if you
also find it useful. (We could def
Congrats Igor!
On Thu, Apr 25, 2024, 07:01 Bruno Cadonna wrote:
> Congrats!
>
> Best,
> Bruno
>
> Am 25. April 2024 05:18:19 MESZ schrieb Yash Mayya :
> >Congratulations Igor!
> >
> >On Wed, 24 Apr, 2024, 23:36 Colin McCabe, wrote:
> >
> >> Hi all,
> >>
> >> The PMC of Apache Kafka is pleased t
[
https://issues.apache.org/jira/browse/KAFKA-16596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viktor Somogyi-Vass resolved KAFKA-16596.
-
Fix Version/s: 3.8.0
Assignee: Andras Katona
Resolution: Fixed
Congrats Greg! :)
On Sun, Apr 14, 2024, 00:35 Bill Bejeck wrote:
> Congrats Greg!
>
> -Bill
>
> On Sat, Apr 13, 2024 at 4:25 PM Boudjelda Mohamed Said
> wrote:
>
> > Congratulations Greg
> >
> > On Sat 13 Apr 2024 at 20:42, Chris Egerton wrote:
> >
> > > Hi all,
> > >
> > > Greg Harris has bee
Congrats Christo! Well deserved!
On Tue, Mar 26, 2024, 13:27 Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
> Congrats Christo!
>
> On Tue, Mar 26, 2024, 17:42 Bruno Cadonna wrote:
>
> > Congrats, Christo!
> >
> > Well deserved!
> >
> > Best,
> > Bruno
> >
> > On 3/26/24 1:04 PM,
folks,
> I would like to propose a new feature to extend the quota management in
> Kafka to support topic-partition based quotas. The following is the link to
> the KIP
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1010%3A+Topic+Partition+Quota
>
>
> Best,
> Af
;https://github.com/apache/kafka/pull/15200> as well.
>>
>> I appreciate all your feedbacks and comments.
>>
>> Special thanks to Viktor Somogyi-Vass and
>> Daniel
>> Urban for the original idea and help.
>> Thank you,
>> Berci
>>
>> --
>> *Bertalan Kondrat* | Founder, SWE
>> servy.hu <https://www.servy.hu/>
>>
>>
>>
>> <https://www.cloudera.com/>
>> --
>>
>
Hi all,
I think that making and updating such a list implies tricky questions that
we have to deal with. Good examples were given by Matthias, that was my
first thought as well before reading his response.
On the other hand I think it would be a good alternative to create a list
of companies that
Hi Mickael,
Reacting to your points:
1. I think it's somewhat unfortunate that we provide an appender tied to a
chosen logger implementation. I think that this shouldn't be part of the
project in its current form. However, there is the sl4fj2 Fluent API which
may solve our problem and turn KafkaLo
Hi Elxan,
+1 (binding).
Thanks,
Viktor
On Mon, Jan 8, 2024 at 5:57 PM Dániel Urbán wrote:
> Hi Elxan,
> +1 (non-binding)
> Thanks for the KIP, this will be a very useful metric for MM!
> Daniel
>
> Elxan Eminov ezt írta (időpont: 2024. jan. 7.,
> V,
> 2:17):
>
> > Hi all,
> > Bumping this for
f I need to add you as a collaborator but if so,
then I'll happily do it for this test).
Thanks,
Viktor
On Wed, May 3, 2023 at 9:41 AM Viktor Somogyi-Vass <
viktor.somo...@cloudera.com> wrote:
> Yes, perhaps this can be used in the github action too, I think this is a
> very usef
Hi Ismael,
I think it's important to make this change, the youtube video you posted on
the discussion thread makes very good arguments and so does the KIP. Java 8
is almost a liability and Java 11 already has smaller (and decreasing)
adoption than 17. It's a +1 (binding) from me.
Thanks,
Viktor
Congrats Divij, well deserved!
On Fri, Dec 29, 2023, 09:36 Lucas Brutschy
wrote:
> Congratulations, Divij!
>
> On Fri, Dec 29, 2023 at 1:32 AM Colin McCabe wrote:
> >
> > Congratulations, Divij!
> >
> > best,
> > Colin
> >
> > On Thu, Dec 28, 2023, at 11:38, Bruno Cadonna wrote:
> > > Congratul
Hey Stan,
I also experienced this, some of the tests indeed take a long time. As an
immediate workaround, do you think we can enforce a global timeout of let's
say 10 minutes?
I don't know if these are taking a long time because of some race condition
or because of the lack of resources and probab
Hi all,
I was wondering what people think about extending the code freeze date to
early January?
The reason I'm asking is that there are still a couple of testing gaps in
JBOD (https://issues.apache.org/jira/browse/KAFKA-14127) which I think is
very important to finish to ensure a high quality rel
Viktor Somogyi-Vass created KAFKA-15992:
---
Summary: Make MM2 heartbeats topic name configurable
Key: KAFKA-15992
URL: https://issues.apache.org/jira/browse/KAFKA-15992
Project: Kafka
Elkhan, do you want to propose a vote for this KIP or do you have any other
ideas to include?
On Tue, Oct 17, 2023 at 2:47 PM Viktor Somogyi-Vass <
viktor.somo...@cloudera.com> wrote:
> Hi hudeqi,
>
> Good thinking about the OOM and resource leaks.
> The "update.replicati
Hi Igor,
I'm just reading through your KIP and noticed that the new protocol you
created doesn't say anything about ACLs of the new AssignReplicasToDirs
API. Would it make sense to authorize these requests as other inter-broker
protocol calls are usually authorized, that is ClusterAction on Cluste
+1 (binding)
Thank you for working on this, feel free to add me to the code review too.
On Fri, Oct 27, 2023 at 2:54 PM Mickael Maison
wrote:
> Hi,
>
> +1 (binding)
> Thanks for the KIP
>
> Mickael
>
> On Wed, Oct 25, 2023 at 5:34 PM Federico Valeri
> wrote:
> >
> > Hi Jakub, thanks for this K
Congrats Satish!
On Fri, Oct 27, 2023, 18:48 Ivan Yurchenko wrote:
> Congrats Satish!
>
> Ivan
>
> On Fri, Oct 27, 2023, at 19:02, Kamal Chandraprakash wrote:
> > Congratulations Satish!
> >
> > On Fri, Oct 27, 2023, 21:10 Jorge Esteban Quilcate Otoya <
> > quilcate.jo...@gmail.com> wrote:
> >
>
Hi hudeqi,
Good thinking about the OOM and resource leaks.
The "update.replication.lag.interval.time" I think is almost good but we
should include that it is about a metric (like
"replication.lag.interval.metric.update.time") so it's obvious without the
docs too.
Thanks,
Viktor
On Sat, Oct 7, 20
Hi Jakub,
I think the KIP looks good overall, and I have one question for now.
Would it make sense to split the config you want to introduce
(ssl.allow.dn.and.san.changes) into two configs? Would users want to enable
one but not the other?
Thanks,
Viktor
On Wed, Sep 13, 2023 at 10:00 PM Jakub Sc
Hi Greg,
> I don't think I understand what you mean here. Are you suggesting an
alternative to the Admin API? An external project could certainly
build such a component with the Admin API.
So I was thinking of something more complex than the Admin API, an external
service that can instruct cluste
nd remote replication
> could also be desirable.
> I think we can explore the idea further, and make sure that CCR is
> extensible to tiered topics if it doesn't make it into the initial
> implementation.
>
> Thanks!
> Greg
>
> On Wed, Oct 4, 2023 at 6:13 AM Viktor Somo
. With a proxy between the client and
> Kafka, that proxy can be available while the original Kafka cluster is
> not. Failovers would happen between distinct sets of clients that are
> part of the same logical application.
>
> Thanks for taking a look at the rejected alternatives!
&g
Hi Greg,
Seems like finding the perfect replication solution is a never ending story
for Kafka :).
Some general thoughts:
GT-1. While as you say it would be good to have some kind of built-in
replication in Kafka, we definitely need to understand the problem better
to provide a better solution. R
Hi Elkhan,
I don't see the config you introduced on the KIP. Otherwise it looks
good to me. If no one has objections or anything to add then I think you
can start the vote after updating the KIP.
>I added the configurable poll interval as an optional - I believe it is
useful to let users to confi
Hi Krishna,
Thanks for the answer. I've seen multiple such images where environment
variables are used and I think they are generally good but it's unsafe for
passing around secrets, jaas configs and so on. Perhaps for secrets we
could recommend using the file config provider. Then users can creat
Hi Erik,
I'm still trying to wrap my head around the KIP, however I have a few
questions that weren't clear to me regarding offset commits:
1. Would auto-commits interfere with the behavior defined in your KIP or
would it work the same as manual commits?
2. As I see you don't separate offset commi
Congrats Justine!
On Sun, Sep 24, 2023, 17:45 Kirk True wrote:
> Congratulations Justine! Thanks for all your great work!
>
> > On Sep 24, 2023, at 8:37 AM, John Roesler wrote:
> >
> > Congratulations, Justine!
> > -John
> >
> > On Sun, Sep 24, 2023, at 05:05, Mickael Maison wrote:
> >> Congrat
Congrats Lucas!
On Thu, Sep 21, 2023 at 7:12 PM Alexander Sorokoumov
wrote:
> Congratulations, Lucas!
>
> On Thu, Sep 21, 2023 at 10:09 AM Walker Carlson
> wrote:
>
> > Congrats Lucas!
> >
> > On Thu, Sep 21, 2023 at 11:42 AM Kamal Chandraprakash <
> > kamal.chandraprak...@gmail.com> wrote:
> >
Congrats Yash!
On Thu, Sep 21, 2023 at 7:04 PM Josep Prat
wrote:
> Congrats Yash!
>
> ———
> Josep Prat
>
> Aiven Deutschland GmbH
>
> Alexanderufer 3-7, 10117 Berlin
>
> Amtsgericht Charlottenburg, HRB 209739 B
>
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>
> m: +491715557497
>
> w: ai
> Hi Viktor,
> >
> > I disagree. Docker is a very popular deployment tool and it's not only
> used
> > with Kubernetes.
> >
> > Ismael
> >
> > On Thu, Sep 14, 2023, 1:14 AM Viktor Somogyi-Vass
> > wrote:
> >
> > > Hi Kri
Hi Krishna,
I think you should merge this KIP and KIP-974 as there are overlaps as
Federico pointed out on KIP-974. I think you should keep that one as it
has well defined goals (improve tests) while I feel this one is too
generic. Docker is usually just a tool for either testing or Kubernetes, so
adjusted freely
> according to the load of the source cluster and the number of tasks.
>
> best,
> hudeqi
>
> "Viktor Somogyi-Vass" <viktor.somo...@cloudera.com.INVALID
> >写道：
> > Hey Elkhan and hudeqi,
> >
> > I'm reading your debate around the i
Hey Elkhan and hudeqi,
I'm reading your debate around the implementation. I also think a
scheduled task would be better in overall accuracy and performance
(compared to calling endOffsets with every poll).
Hudeqi, do you have any experience of what works best for you in terms of
time intervals? I
Hi Elkhan,
I think this is quite a useful improvement. A few questions, suggestions:
1. How do you calculate the min, max and avg variants? If I understand
correctly then the metric itself is partition based
(where replication-offset-lag is the lag of the replica that is being
consumed) and these
Viktor Somogyi-Vass created KAFKA-15219:
---
Summary: Support delegation tokens in KRaft
Key: KAFKA-15219
URL: https://issues.apache.org/jira/browse/KAFKA-15219
Project: Kafka
Issue Type
Mickael, have you had some time to review this by any chance?
On Tue, Jun 20, 2023 at 5:23 PM Viktor Somogyi-Vass <
viktor.somo...@cloudera.com> wrote:
> Hey all,
>
> I'd like to revive this discussion. I've created
> https://cwiki.apache.org/confluence/display/KAFKA
Congrats Greg!
On Mon, Jul 10, 2023, 17:54 Yash Mayya wrote:
> Congrats Greg!
>
> On Mon, Jul 10, 2023 at 9:15 PM Chris Egerton wrote:
>
> > Hi all,
> >
> > The PMC for Apache Kafka has invited Greg Harris to become a committer,
> and
> > we are happy to announce that he has accepted!
> >
> > G
Viktor Somogyi-Vass created KAFKA-15161:
---
Summary: InvalidReplicationFactorException at connect startup
Key: KAFKA-15161
URL: https://issues.apache.org/jira/browse/KAFKA-15161
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-15059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viktor Somogyi-Vass resolved KAFKA-15059.
-
Resolution: Fixed
[~ChrisEgerton] since the PR is merged, I resolve this ticket
Hey all,
I'd like to revive this discussion. I've created
https://cwiki.apache.org/confluence/display/KAFKA/KIP-879%3A+Multi-level+Rack+Awareness
last November and it seems to be that there is a nice overlap between the
two and would be good to merge. Should we revive KIP-660 and merge the two
KIP
Congrats Divij!
On Tue, Jun 13, 2023, 20:27 Philip Nee wrote:
> Congrats!
>
> On Tue, Jun 13, 2023 at 8:17 PM Randall Hauch wrote:
>
> > Congratulations!
> >
> > On Tue, Jun 13, 2023 at 12:48 PM Matthias J. Sax
> wrote:
> >
> > > Congrats!
> > >
> > > On 6/13/23 10:24 AM, Satish Duggana wrote:
[
https://issues.apache.org/jira/browse/KAFKA-12384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viktor Somogyi-Vass resolved KAFKA-12384.
-
Fix Version/s: 3.6.0
Resolution: Fixed
> Flaky T
for a reviewer in the commit
> > > > message?
> > > > > GitHub automatically marks the folks as "reviewers" who have used
> the
> > > > > "review-changes" button on the top left corner and left feedback.
> > > GitHub
> > > > > also has se
[
https://issues.apache.org/jira/browse/KAFKA-14929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viktor Somogyi-Vass resolved KAFKA-14929.
-
Resolution: Fixed
> Flaky KafkaStatusBackingStoreFormatT
Jun, thank you for all your hard work! Also, congrats Mickael, it is very
well deserved :)
Best,
Viktor
On Fri, Apr 21, 2023, 18:15 Adam Bellemare wrote:
> Thank you for all your hard work Jun - that's a decade-long legacy!
> And congratulations to you Mickael!
>
> On Fri, Apr 21, 2023 at 11:20
Hi Daniel,
I think this is a useful addition, it helps resolving issues and
escalations, and improves overall traceability.
Changing the logging context may imply the risk of making certain log
parsers unable to work on new logs. As I see we by default disable this
feature which solves this proble
Hi all,
A couple of comments:
1) Regarding the motivation: is the motivation simply monitoring related or
are there any other reasons to this?
2) Can we change monitoring to be identical to filters, so that what is
actively filtered, we monitor exactly those topics and groups? (So group
metrics ar
27;m missing something or if there are some nice hidden
> tricks in GitHub that I didn't know :)
>
> Best,
> On Tue, Apr 18, 2023 at 9:48 AM Viktor Somogyi-Vass
> wrote:
>
> > Hi all,
> >
> > Unfortunately I forgot to add myself as a reviewer *again *on a PR wh
Hi all,
Unfortunately I forgot to add myself as a reviewer *again *on a PR when
merging. Shame on me.
However I was thinking about looking into Github actions whether we can
automate this process or at least prevent PRs from merging that don't have
"reviewers" in the description.
Has anyone ever
Congrats David!
On Fri, Mar 10, 2023 at 9:12 AM Tom Bentley wrote:
> Congratulations!
>
> On Fri, 10 Mar 2023 at 03:36, John Roesler wrote:
>
> > Congratulations, David!
> > -John
> >
> > On Thu, Mar 9, 2023, at 20:18, ziming deng wrote:
> > > Congrats David!
> > >
> > > Ziming
> > >
> > >> On
Congrats Chris!
On Fri, Mar 10, 2023 at 12:12 PM Sagar wrote:
> Congrats Chris! Absolutely well deserved!
>
> Sagar.
>
> On Fri, Mar 10, 2023 at 1:42 PM Tom Bentley wrote:
>
> > Congratulations!
> >
> > On Fri, 10 Mar 2023 at 03:35, John Roesler wrote:
> >
> > > Congratulations, Chris!
> > > -
Congrats Stan! :)
On Fri, Jan 20, 2023 at 12:35 AM Colin McCabe wrote:
> Congratulations, Stan! Well deserved.
>
> best,
> Colin
>
> On Tue, Jan 17, 2023, at 07:50, Jun Rao wrote:
> > Hi, Everyone,
> >
> > The PMC of Apache Kafka is pleased to announce a new Kafka committer
> > Stanislav Kozlovs
Ok, then +1 (binding) :)
On Mon, Jan 9, 2023 at 3:44 PM John Roesler wrote:
> Yes, you are!
>
> Congrats again :)
> -John
>
> On Mon, Jan 9, 2023, at 08:25, Viktor Somogyi-Vass wrote:
> > Hey all,
> >
> > Now that I'm a committer am I allowed to change m
Hey all,
Now that I'm a committer am I allowed to change my non-binding vote to
binding to pass the KIP? :)
On Thu, Nov 10, 2022 at 6:13 PM Greg Harris
wrote:
> +1 (non-binding)
>
> Thanks for the KIP, this is an important improvement.
>
> Greg
>
> On Thu, Nov 10, 2022 at 7:21 AM John Roesler
Congrats Edoardo!
On Sat, Jan 7, 2023, 18:15 Bill Bejeck wrote:
> Congratulations, Edoardo!
>
> -Bill
>
> On Sat, Jan 7, 2023 at 12:11 PM John Roesler wrote:
>
> > Congrats, Edoardo!
> > -John
> >
> > On Fri, Jan 6, 2023, at 20:47, Matthias J. Sax wrote:
> > > Congrats!
> > >
> > > On 1/6/23 5:
Hi Ismael,
I think this is a good idea, it can also simplify the code quite a bit.
I was gonna ask about whether you think it would be useful to automate
protocol deprecation but I see you'll have a separate KIP for that so I'll
just wait :).
I see that in multiple places clients have older than
Congrats Justine!
On Thu, Dec 29, 2022, 22:05 Chris Egerton wrote:
> Congrats, Justine!
>
> On Thu, Dec 29, 2022, 15:58 David Jacot wrote:
>
> > Hi all,
> >
> > The PMC of Apache Kafka is pleased to announce a new Kafka committer
> > Justine
> > Olshan.
> >
> > Justine has been contributing to
Congrats Satish!
On Fri, Dec 23, 2022, 19:38 Mickael Maison wrote:
> Congratulations Satish!
>
> On Fri, Dec 23, 2022 at 7:36 PM Divij Vaidya
> wrote:
> >
> > Congratulations Satish! 🎉
> >
> > On Fri 23. Dec 2022 at 19:32, Josep Prat
> > wrote:
> >
> > > Congrats Satish!
> > >
> > > ———
> > >
Congrats Josep!
On Tue, Dec 20, 2022, 21:56 Matthias J. Sax wrote:
> Congrats!
>
> On 12/20/22 12:01 PM, Josep Prat wrote:
> > Thank you all!
> >
> > ———
> > Josep Prat
> >
> > Aiven Deutschland GmbH
> >
> > Immanuelkirchstraße 26, 10405 Berlin
> >
> > Amtsgericht Charlottenburg, HRB 209739 B
>
Congratulations, Viktor!
> > >
> > > Regards,
> > >
> > > Rajini
> > >
> > >
> > > On Thu, Dec 15, 2022 at 11:41 AM Ron Dagostino
> > wrote:
> > >
> > >> Congrats to you too, Victor!
> > >>
> > >&g
Congrats Luke! :)
On Fri, Dec 16, 2022, 21:26 Randall Hauch wrote:
> Congratulations, Luke!
>
> On Fri, Dec 16, 2022 at 2:08 PM Josep Prat
> wrote:
>
> > Congrats Luke!
> >
> > On Fri, Dec 16, 2022 at 8:55 PM Bill Bejeck wrote:
> >
> > > Congratulations Luke!
> > >
> > > -Bill
> > >
> > > On F
Thank you everyone! :)
On Thu, Dec 15, 2022 at 10:22 AM Mickael Maison
wrote:
> Congratulations Viktor!
>
> On Thu, Dec 15, 2022 at 10:06 AM Tamas Barnabas Egyed
> wrote:
> >
> > Congratulations, Viktor!
>
Congrats Ron! :)
On Thu, Dec 15, 2022 at 10:22 AM Mickael Maison
wrote:
> Congratulations Ron!
>
> On Thu, Dec 15, 2022 at 9:41 AM Eslam Farag wrote:
> >
> > Congratulations, Ron ☺️
> >
> > On Thu, 15 Dec 2022 at 10:40 AM Tom Bentley wrote:
> >
> > > Congratulations!
> > >
> > > On Thu, 15 Dec
eate a JIRA ticket directly without KIP if you have ideas on improving
> > it, right?
> >
> > --
> > Best,
> > Ziming
> >
> > > On Nov 29, 2022, at 21:52, Viktor Somogyi-Vass <
> > viktor.somo...@cloudera.com.INVALID> wrote:
> > >
>
i, Oct 28, 2022 at 4:14 PM Viktor Somogyi-Vass <
viktor.somo...@cloudera.com> wrote:
> Hey all,
>
> I'd like to propose a new broker side replica assignment strategy and an
> interface that generalizes replica assignment on brokers and makes them
> pluggable.
>
> Br
Hi Rajini,
If I understand correctly, the client.rack config would stay supported
after KIP-848 but does it expand the scope of that KIP too with this
config? I mean that currently you propose ConsumerProtocolSubscription to
be used but this protocol won't be available and we need to transfer the
Hey all,
I'd like to propose a new broker side replica assignment strategy and an
interface that generalizes replica assignment on brokers and makes them
pluggable.
Briefly, the motivation for the new replica assignment strategy is that
more and more of our customers would want to run their clust
+1 (non-binding). Thanks for the KIP!
On Mon, Oct 24, 2022 at 3:23 PM Chris Egerton
wrote:
> +1 (binding). Thanks for the KIP!
>
> On Sat, Oct 22, 2022 at 3:38 AM Urbán Dániel
> wrote:
>
> > Hi everyone,
> >
> > I would like to start a vote on KIP-710 which aims to support running a
> > dedicat
[
https://issues.apache.org/jira/browse/KAFKA-14331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viktor Somogyi-Vass resolved KAFKA-14331.
-
Resolution: Duplicate
> Upgrade to Scala 2.13
Viktor Somogyi-Vass created KAFKA-14331:
---
Summary: Upgrade to Scala 2.13.10
Key: KAFKA-14331
URL: https://issues.apache.org/jira/browse/KAFKA-14331
Project: Kafka
Issue Type
Viktor Somogyi-Vass created KAFKA-14281:
---
Summary: Multi-level rack awareness
Key: KAFKA-14281
URL: https://issues.apache.org/jira/browse/KAFKA-14281
Project: Kafka
Issue Type
Viktor Somogyi-Vass created KAFKA-14250:
---
Summary: Exception during normal operation in MirrorSourceTask
causes the task to fail instead of shutting down gracefully
Key: KAFKA-14250
URL: https
Congrats Chris!
On Mon, Jul 25, 2022, 18:33 Matthew Benedict de Detrich
wrote:
> Congratulations!
>
> --
> Matthew de Detrich
> Aiven Deutschland GmbH
> Immanuelkirchstraße 26, 10405 Berlin
> Amtsgericht Charlottenburg, HRB 209739 B
>
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> m: +49
Hi Luke & Artem,
We prepared the fix, would you please help in getting a committer-reviewer
to get this issue resolved?
Thanks,
Viktor
On Fri, Jul 8, 2022 at 12:57 PM Dániel Urbán wrote:
> Submitted a PR with the fix: https://github.com/apache/kafka/pull/12392
> In the PR I tried keeping the p
timing on your part :)
> I'll merge this PR shortly and start a new RC build.
>
> -David
>
> On Thu, Jul 21, 2022 at 11:42 AM Viktor Somogyi-Vass
> wrote:
>
> > Hi David,
> >
> > Found an issue (tight loop in the consumer), fixed it on trunk and
> > bac
1 - 100 of 309 matches
Mail list logo
