Thanks Giuseppe for the explanation! It make sense to me.
Best regards,
Yuxia
- 原始邮件 -
发件人: "Giuseppe Lillo"
收件人: "dev"
发送时间: 星期二, 2025年 4 月 29日 上午 12:14:14
主题: Re: [SPAM][DISCUSS] KIP-1164: Topic Based Batch Coordinator
Hello Yuxia, thanks for your question
r1 is down, then client recieve A,B fail and retry to send
> A,B to broker2
> Then, how Batch Coordinator can choose total order to be A,B,C ?
>
>
> Best regards,
> Yuxia
>
> - 原始邮件 -
> 发件人: "Ivan Yurchenko"
> 收件人: "dev"
> 发送时间: 星期三, 2025年 4
-
发件人: "Ivan Yurchenko"
收件人: "dev"
发送时间: 星期三, 2025年 4 月 23日 下午 5:46:46
主题: [SPAM][DISCUSS] KIP-1164: Topic Based Batch Coordinator
Hi all!
We want to start the discussion thread for KIP-1164: Topic Based Batch
Coordinator [1], which is a sub-KIP for KIP-1150 [2].
Let&#x
gt; Then, how Batch Coordinator can choose totol order to be A,B,C ?
>
>
> Best regards,
> Yuxia
>
> ----- 原始邮件 -
> 发件人: "Christo Lolov"
> 收件人: dev@kafka.apache.org
> 发送时间: 星期二, 2025年 4 月 22日 下午 9:04:06
> 主题: [SPAM]Re: [DISCUSS] KIP-1150 Diskless Topics
&
.apache.org
发送时间: 星期二, 2025年 4 月 22日 下午 9:04:06
主题: [SPAM]Re: [DISCUSS] KIP-1150 Diskless Topics
Hello!
I want to start with saying that this is a big and impressive undertaking
and I am really excited to see its progression! I am posting my initial
comments in this thread, but they span a few
e about
> that but feels like the result would be a response similar to as if kafka
> had the info stored in-memory (as redis do) but that would still make me
> question how is that Kafka can handle a higher throughput if the "design"
> is so similar.
>
>
> ___
-memory (as redis do) but that would still make me question how is
that Kafka can handle a higher throughput if the "design" is so similar.
De: Andrew Grant
Enviado: quinta-feira, 14 de outubro de 2021 15:55
Para: dev@kafka.apache.org
Assunto: [SPAM] Re:
rowse/KAFKA-13262
> [2]: https://kafka.apache.org/30/documentation.html
>
> From: Ron Dagostino
> Sent: Thursday, September 2, 2021 9:16 PM
> To: dev@kafka.apache.org
> Cc: Users ; kafka-clients <
> kafka-clie...@googlegroups.com>
> Subject: [Susp
@kafka.apache.org
Cc: Users ; kafka-clients
Subject: [Suspected Spam] Re: [VOTE] 3.0.0 RC1
Hi Konstantine. I have opened a probable blocker ticket
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FKAFKA-13270&data=04%7C01%7Cgrussell%40vmware
John Gray created KAFKA-13037:
-
Summary: "Thread state is already PENDING_SHUTDOWN" log spam
Key: KAFKA-13037
URL: https://issues.apache.org/jira/browse/KAFKA-13037
Project: Kafka
Thanks!
Brandon Brown
> On Jan 5, 2021, at 6:07 PM, Justine Olshan wrote:
>
> The user has been blocked. https://issues.apache.org/jira/browse/INFRA-21268
>
>> On Tue, Jan 5, 2021 at 2:52 PM Brandon Brown
>> wrote:
>>
>> Is there any way to block Tim van der Kooi from making issues? I’m get
The user has been blocked. https://issues.apache.org/jira/browse/INFRA-21268
On Tue, Jan 5, 2021 at 2:52 PM Brandon Brown
wrote:
> Is there any way to block Tim van der Kooi from making issues? I’m getting
> about 10 new email issues created a minute.
>
> Brandon Brown
>
>
Is there any way to block Tim van der Kooi from making issues? I’m getting
about 10 new email issues created a minute.
Brandon Brown
[
https://issues.apache.org/jira/browse/KAFKA-9574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mickael Maison resolved KAFKA-9574.
---
Resolution: Fixed
> Contact page links to spam/ads site on search-hadoop[.]com dom
Gert van Dijk created KAFKA-9574:
Summary: Contact page links to spam/ads site on
search-hadoop[.]com domain
Key: KAFKA-9574
URL: https://issues.apache.org/jira/browse/KAFKA-9574
Project: Kafka
+1 agree with Jeff,
Michał
On 31/05/17 06:25, Jeff Widman wrote:
I'm hugely in favor of this change as well...
Although I actually find the Github pull request emails less useful than
the jirabot ones since Jira typically has more info when I'm trying to
figure out if the issue is relevant to
I'm hugely in favor of this change as well...
Although I actually find the Github pull request emails less useful than
the jirabot ones since Jira typically has more info when I'm trying to
figure out if the issue is relevant to me or not...
On Tue, May 30, 2017 at 2:28 PM, Guozhang Wang wrote:
I actually do not know.. Maybe Jun knows better than me?
Guozhang
On Mon, May 29, 2017 at 12:58 PM, Gwen Shapira wrote:
> I agree.
>
> Guozhang, do you know how to implement the suggestion? JIRA to Apache
> Infra? Or is this something we can do ourselves somehow?
>
> On Mon, May 29, 2017 at 9:
I agree.
Guozhang, do you know how to implement the suggestion? JIRA to Apache
Infra? Or is this something we can do ourselves somehow?
On Mon, May 29, 2017 at 9:33 PM Guozhang Wang wrote:
> I share your pains. Right now I use filters on my email accounts and it has
> been down to about 25 per
I share your pains. Right now I use filters on my email accounts and it has
been down to about 25 per day.
I think setup a separate mailing list for jirabot and jenkins auto
generated emails is a good idea.
Guozhang
On Mon, May 29, 2017 at 12:58 AM, wrote:
> Hello everyone
>
> I find it hard
Hello everyone
I find it hard to follow this mailinglist due to all the mails generated
by Jira. Just over this weekend there are 240 new mails.
Would it be possible to setup something like j...@kafka.apache.org where
everyone can subscribe interested in those Jira mails?
Right now I am going t
Hi,
Any comments on this?
Ciprian.
Lähettäjä: Pascu, Ciprian (Nokia - FI/Espoo)
Lähetetty: 9. elokuuta 2016 15:34:10
Vastaanottaja: dev@kafka.apache.org
Aihe: ISR issues
Hi,
We are testing Kafka cluster with high traffic loads (2+ messages/second)
and
pull request:
https://github.com/apache/kafka/pull/1473
KAFKA-3792: Fix log spam in clients for unknown topics
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rajinisivaram/kafka KAFKA-3792
Alternatively you can review and apply t
GitHub user rajinisivaram opened a pull request:
https://github.com/apache/kafka/pull/1473
KAFKA-3792: Fix log spam in clients for unknown topics
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rajinisivaram/kafka KAFKA-3792
Rajini Sivaram created KAFKA-3792:
-
Summary: Fix log spam in clients when topic doesn't exist
Key: KAFKA-3792
URL: https://issues.apache.org/jira/browse/KAFKA-3792
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Stein resolved KAFKA-1478.
--
Resolution: Fixed
I took care of this just now.
> Remove spam comment from w
Jon Bringhurst created KAFKA-1478:
-
Summary: Remove spam comment from wiki
Key: KAFKA-1478
URL: https://issues.apache.org/jira/browse/KAFKA-1478
Project: Kafka
Issue Type: Bug
27 matches
Mail list logo
