回复: [ANNOUNCE] New committer: David Jacot

Congrats, David! Well deserved! 发件人: Vahid Hashemian 发送时间: 2020年10月19日 11:17 收件人: dev 主题: Re: [ANNOUNCE] New committer: David Jacot Congrats David! --Vahid On Sun, Oct 18, 2020 at 4:23 PM Satish Duggana wrote: > Congratulations David! > > On Sat, Oct 17,

回复: [VOTE] KIP-431: Support of printing additional ConsumerRecord fields in DefaultMessageFormatter

Hi Badai, Thanks for the KIP. A quick question from me: "CreateTime:1592475472398|key1|3|0|h1=v1,h2=v2|value1<-- offset 3, partition 0" Seems the partition follows the offset. My question is, does the property order matter? The partition is always printed following the offset no matter

回复: [DISCUSS] KIP-308: GetOffsetShell: new KafkaConsumer API, support for multiple topics, minimize the number of requests to server

That's a great KIP for GetOffsetShell tool. I have a question about the multiple-topic lookup situation. In a secured environment, what does the tool output if it has DESCRIBE privileges for some topics but hasn't for others? 发件人: Dániel Urbán 发送时间: 2020年6月30日

回复: Re:Re: [ANNOUNCE] New committer: Xi Hu

Thank you, everyone. It is my great honor to be a part of the community. Will make a greater contribution in the coming days. 发件人: Roc Marshal 发送时间: 2020年6月25日 10:20 收件人: us...@kafka.apache.org 主题: Re:Re: [ANNOUNCE] New committer: Xi Hu Congratulations ! Xi

回复: [ANNOUNCE] New committer: Boyang Chen

Congrats, Boyang  发件人: Boyang Chen 发送时间: 2020年6月23日 7:59 收件人: dev 抄送: users 主题: Re: [ANNOUNCE] New committer: Boyang Chen Thanks a lot everyone, I really appreciate the recognition, and hope to make more solid contributions to the community in the future!

[DISCUSS] KIP-563: Add 'tail -n' feature for ConsoleConsumer

Hi All, I'd like to start a discussion on KIP-563 which is to add "tail -n" capability for ConsumerConsole tool. Please check https://cwiki.apache.org/confluence/display/KAFKA/KIP-563%3A+Add+%27tail+-n%27+feature+for+ConsoleConsumer for more details. Any feedbacks or comments are welcomed.

答复: [VOTE] KIP-347: Enable batching in FindCoordinatorRequest

+1 (non-binding) 发件人: Yishun Guan 发送时间: 2018年8月17日 8:14 收件人: dev@kafka.apache.org 主题: [VOTE] KIP-347: Enable batching in FindCoordinatorRequest Hi all, I want to start a vote on this KIP:

答复: [ANNOUNCE] New Committer: Dong Lin

Congrats, Dong Lin! 发件人: Matthias J. Sax 发送时间: 2018年3月29日 6:37 收件人: us...@kafka.apache.org; dev@kafka.apache.org 主题: Re: [ANNOUNCE] New Committer: Dong Lin Congrats! On 3/28/18 1:16 PM, James Cheng wrote: > Congrats, Dong! > > -James >

答复: [VOTE] KIP-265: Make Windowed Serde to public APIs

+1 (non-binding) 发件人: Matthias J. Sax 发送时间: 2018年3月6日 8:19 收件人: dev@kafka.apache.org 主题: Re: [VOTE] KIP-265: Make Windowed Serde to public APIs +1 (binding) Thanks for the KIP Guozhang! -Matthias On 3/5/18 2:41 PM, Bill Bejeck wrote: >

答复: [DISCUSS] KIP-265: Make Windowed Serde to public APIs

Guozhang, Thanks for this KIP. Please help confirm questions below: 1. Do we also need to retrofit `SimpleConsumerShell` to have it support these newly-added serdes? 2. Does this KIP cover the changes for ConsoleConsumer as well? 发件人: Guozhang Wang

答复: KIP-250 Add Support for Quorum-based Producer Acknowledgment

Currently, with holding the assigned replicas(AR) for all partitions, controller is now able to elect new leaders by selecting the first replica of AR which occurs in both live replica set and ISR. If switching to the LEO-based strategy, controller context might need to be enriched or

答复: [ANNOUNCE] New Kafka PMC Member: Rajini Sivaram

Congratulations, Rajini Sivaram. Very well deserved! 发件人: Konstantine Karantasis 发送时间: 2018年1月18日 6:23 收件人: dev@kafka.apache.org 抄送: us...@kafka.apache.org 主题: Re: [ANNOUNCE] New Kafka PMC Member: Rajini Sivaram Congrats Rajini!

[VOTE] KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

voting now. Please conclude by a summary of the voting status including non-binding and binding votes, thanks. Guozhang On Sun, Dec 10, 2017 at 8:10 PM, Hu Xi <huxi...@hotmail.com> wrote: > Hi all, Would we safely accept this KIP since three binding votes have > already been c

答复: 答复: [VOTE] KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

hree binding votes you can close this voting now. > > Please conclude by a summary of the voting status including non-binding and > binding votes, thanks. > > > Guozhang > > On Sun, Dec 10, 2017 at 8:10 PM, Hu Xi <huxi...@hotmail.com> wrote: > >> Hi all, Would

答复: [VOTE] KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

ic min lead and per-partition lead metrics to KafkaConsumer Hi Hu Xi, As I said before, it is only a clarification question for its internal implementation; it is not related to the public interfaces. Guozhang On Wed, Dec 6, 2017 at 12:34 AM, Hu Xi <huxi...@hotmail.com> wrote: &

[VOTE] KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

e? Guozhang On Mon, Dec 4, 2017 at 11:26 PM, Hu Xi <huxi...@hotmail.com> wrote: > Guozhang, > > > Thanks for the vote and comments. I am not sure if I fully understand the > parent metrics here. This KIP will introduce a client-level metric named > 'records-lead-min' and

答复: [VOTE] KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

? 发件人: Guozhang Wang <wangg...@gmail.com> 发送时间: 2017年12月5日 15:16 收件人: dev@kafka.apache.org 主题: Re: [VOTE] KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer Thanks Hu Xi, I made a pass over the KIP and it lgtm. +1. Just a clarification qu

[VOTE] KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

Hi all, As I didn't see any further discussion around this KIP, I'd like to start voting. KIP documentation: https://cwiki.apache.org/confluence/display/KAFKA/KIP-223+-+Add+per-topic+min+lead+and+per-partition+lead+metrics+to+KafkaConsumer Cheers, huxihx

答复: REPLY: [DISCUSS]KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

On Mon, Nov 20, 2017 at 10:14 PM, Hu Xi <huxi...@hotmail.com> wrote: > Hi Jun, > > > Seems the prefix that is used to be the unique Sensor name cannot be > removed, so should we keep the prefix? > > > > 发件人: Jun Rao <j...@conflue

答复: REPLY: [DISCUSS]KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

fix. KIP-225 tries to change the metric name to use topic/partition as the tag. We can just do the same thing for lead by using tags in the metric name. Thanks, Jun On Mon, Nov 20, 2017 at 10:14 PM, Hu Xi <huxi...@hotmail.com> wrote: > Hi Jun, > > > Seems the prefix that is used

REPLY: [DISCUSS]KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

Nov 19, 2017 at 10:31 PM, Hu Xi <huxi...@hotmail.com> wrote: > Jun, > > > Thanks for the comments. Do you think it'd better to add topic/partition > tags for those metrics as well as keep the prefix? If those prefixes should > really be removed, does this KIP need to do

答复: 答复: 答复: [DISCUSS]KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

; > > > I have a patch more or less ready so I could probably get the fix > checked > > > in (after the vote) and you could build on top of it. Otherwise we > could > > > merge both KIPs if you want but they do sound different to me. > > > > >

Reply: [DISCUSS]KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

; > > I have a patch more or less ready so I could probably get the fix checked > > in (after the vote) and you could build on top of it. Otherwise we could > > merge both KIPs if you want but they do sound different to me. > > > > Thanks! > > Charly > >

[DISCUSS] Hide internal topics' directories

Hi all, Many new Kafka users are confused about the fact there are a lot of sub-directories named '__consumer_offsets-***' or '__transaction_state-***' under the broker data directory and ask if they can be removed. Do you guys think it can be beneficial to hide those internal topics'

答复: 答复: [DISCUSS]KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

nsumer. I am not sure what the per partition level records-lead-min and records-lead-avg are. Are they the min/avg of the lead since the consumer is started? I am not sure we need those since an external monitoring system can always derive them from records-lead. Thanks, Jun On Mon, Nov 13, 20

答复: [DISCUSS]KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

nstead of as a prefix in the metric name. Jun On Thu, Nov 9, 2017 at 1:03 AM, Hu Xi <huxi...@hotmail.com> wrote: > Hi all, > > > As per Jun Rao's suggestion, I opened up the KIP-223(https://cwiki.apache. > org/confluence/display/KAFKA/KIP-223+-+Add+per-topic+min+ >

答复: [DISCUSS]KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

tition lead metrics to KafkaConsumer Can you fill out JIRA number ? "TOPIC-PARTITION_ID.record-lead" In the code sample, "records-" is used. Please make them consistent. On Thu, Nov 9, 2017 at 1:03 AM, Hu Xi <huxi...@hotmail.com> wrote: > Hi all, > > > As p

[DISCUSS]KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

Hi all, As per Jun Rao's suggestion, I opened up the KIP-223(https://cwiki.apache.org/confluence/display/KAFKA/KIP-223+-+Add+per-topic+min+lead+and+per-partition+lead+metrics+to+KafkaConsumer) concerning adding new kinds of lag metrics for KafkaConsumer. Be free to leave your comments here.

答复: A quick question on StickyAssignor

Thanks Hashemian. It's clear to me now  发件人: Vahid S Hashemian <vahidhashem...@us.ibm.com> 发送时间: 2017年9月7日 12:41 收件人: dev@kafka.apache.org 主题: Re: A quick question on StickyAssignor Hi Hu Xi, This is a typo. It should read if a consumer A has 2+ fewer

A quick question on StickyAssignor

Hello Dev, I am a little confused about the statement below in KIP-54 (StickyAssignor things): * if a consumer A has 2+ fewer topic partitions assigned to it compared to another consumer B, none of the topic partitions assigned to B can be assigned to A. Is it a typo or do I

答复: [ANNOUNCE] New Kafka PMC member: Jiangjie (Becket) Qin

Congrats Becket! 发件人: Guozhang Wang 发送时间: 2017年8月24日 13:32 收件人: dev@kafka.apache.org 主题: Re: [ANNOUNCE] New Kafka PMC member: Jiangjie (Becket) Qin Congrats Jiangjie! Guozhang On Wed, Aug 23, 2017 at 10:20 PM, Joel Koshy

答复: 答复: [VOTE] KIP-177: Consumer perf tool should count rebalance time

space. -Ewen On Sun, Aug 6, 2017 at 5:16 AM, Mickael Maison <mickael.mai...@gmail.com> wrote: > +1 > > On Sun, Aug 6, 2017 at 4:15 AM, Hu Xi <huxi...@hotmail.com> wrote: > > Hi all, a naive question please. Since this KIP already collects four > binding +1 votes, c

答复: [DISCUSS] KIP-178: Size-based log directory selection strategy

Request. Do you think this is a problem? Dong On Thu, Aug 3, 2017 at 7:36 PM, Hu Xi <huxi...@hotmail.com> wrote: > Hi Dong, some thoughts on your second mail. Since currently logs for > multiple partitions are created sequentially not in parallel, it's probably > okay for us

答复: [VOTE] KIP-177: Consumer perf tool should count rebalance time

[VOTE] KIP-177: Consumer perf tool should count rebalance time +1 On Fri, Aug 4, 2017 at 11:02 AM, Ismael Juma <ism...@juma.me.uk> wrote: > Thanks for the KIP, +1 (binding) > > Ismael > > On Fri, Aug 4, 2017 at 3:13 AM, Hu Xi <huxi...@hotmail.com> wrote: > > >

[DISCUSS] KIP-178: Size-based log directory selection strategy

skew. Does it make any senses? 发件人: Hu Xi <huxi...@hotmail.com> 发送时间: 2017年8月3日 16:51 收件人: dev@kafka.apache.org 主题: 答复: 答复: [DISCUSS] KIP-178: Size-based log directory selection strategy Dong, yes, many thanks for the comments from the second mail. Wil

[VOTE] KIP-177: Consumer perf tool should count rebalance time

Hi all, I'd like to kick off the vote for KIP-177: https://cwiki.apache.org/confluence/display/ARIES/KIP-177%3A+Consumer+perf+tool+should+count+rebalance+time. A PR for this KIP can be found at https://github.com/apache/kafka/pull/3188

答复: 答复: [DISCUSS] KIP-178: Size-based log directory selection strategy

主题: Re: 答复: [DISCUSS] KIP-178: Size-based log directory selection strategy Hu, I think this is worth discussion even if it doesn't require new config. Could you also read my second email? On Wed, Aug 2, 2017 at 6:17 PM, Hu Xi <huxi...@hotmail.com> wrote: > Thanks Dong, do you mean

答复: [DISCUSS] KIP-178: Size-based log directory selection strategy

ct log directory with the least partition number instead of the one with the most free disk space? Thanks, Dong On Wed, Aug 2, 2017 at 6:03 PM, Hu Xi <huxi...@hotmail.com> wrote: > Hi all, how do you think of this KIP? Any comments are welcomed. > > > _______

转发: [DISCUSS] KIP-178: Size-based log directory selection strategy

Hi all, how do you think of this KIP? Any comments are welcomed. 发件人: Hu Xi <huxi...@hotmail.com> 发送时间: 2017年7月18日 15:21 收件人: dev@kafka.apache.org 主题: [DISCUSS] KIP-178: Size-based log directory selection strategy Hi all, KIP-178 is c

[DISCUSS] KIP-177 Consumer perf tool should count rebalance time

Hi all, I opened up a new KIP (KIP-177) concerning consumer perf tool counting and showing rebalance time in the output. Be free to leave your comments here. Thanks in advance.

Apply for access for Kafka KIP creation permission

Apply for access for KIP creation permission. WikiID: huxi_2b Email: huxi...@hotmail.com

答复: [ANNOUNCE] New Kafka PMC member Ismael Juma

Congrats, Ismael  发件人: Molnár Bálint 发送时间: 2017年7月6日 15:51 收件人: dev@kafka.apache.org 主题: Re: [ANNOUNCE] New Kafka PMC member Ismael Juma Congrats, Ismael:) 2017-07-06 2:57 GMT+02:00 Matthias J. Sax : > Congrats!

答复: Kafka 0.9.0.1 Direct Memory OOM

Could you set -XX:MaxDirectMemorySize to a larger value and retry? 发件人: JsonTu 发送时间: 2017年5月9日 14:38 收件人: us...@kafka.apache.org; dev@kafka.apache.org; wangg...@gmail.com; becket@gmail.com 主题: Kafka 0.9.0.1 Direct Memory OOM Hi All, We

答复: Invoking KafkaConsumer#seek for the same partition

to me the comment is imprecisely phrased but was meant to indicate the behaviour you are describing. Perhaps instead of "the latest offset", it should say, "the offset used in the latest seek" to make it super-clear. Cheers, Michal On 13/04/17 08:28, Hu Xi wrote: >

Invoking KafkaConsumer#seek for the same partition

Hi guys, The comments for KafkaConsumer#seek says “If this API is invoked for the same partition more than once, the latest offset will be used on the next poll()”. However, I tried a couple of times, and it turned out that the next poll could always read records from the offset which was

[DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

Two things I want to confirm. Please advise. 1. Seems the KIP only cares about topic management things. Is there any plan for this KIP to merge the feature of what `GetOffsetShell` script offers? Since a lot of people really want to know/monitor how many committed records have been created

When does Produce response get sent back to client if acks is set to -1?

Hello guys, Due to the laziness of updating high watermark and async replicating, please guide me when the Produce response will be sent back to client if I set to acks to -1? Before all the followers have updated their LEOs or after ? Thanks.