Mateusz
This KIP would be very useful for debugging. But the last discussion
is in Feb 2019.
Are you ok if I take over this KIP?
--
Thanks,
Badai
and
give me some feedback?
This feature will be very helpful for people supporting Kafka in operations.
If it is ready for a vote, please let me know.
Thanks
Badai
On Sat, Jun 13, 2020 at 10:59 PM Badai Aqrandista wrote:
>
> Mateusz
>
> This KIP would be very useful for debugging.
to the user? For instance, we print out NO_TIMESTAMP
> where there is no timestamp.
>
> Best,
> David
>
> On Wed, Jun 17, 2020 at 4:53 PM Badai Aqrandista wrote:
>
> > Hi all,
> >
> > I have contacted Mateusz separately and he is ok for me to take
Excellent.
Would like to hear more feedback from others.
On Sat, Jun 20, 2020 at 1:27 AM David Jacot wrote:
>
> Hi Badai,
>
> Thanks for your reply.
>
> 2. Yes, that makes sense.
>
> Best,
> David
>
> On Thu, Jun 18, 2020 at 2:08 PM Badai Aqrandista wrote:
Hi all
After resurrecting the discussion thread [1] for KIP-431 and have not
received any further feedback for 2 weeks, I would like to resurrect
the voting thread [2] for KIP-431.
I have updated KIP-431 wiki page
(https://cwiki.apache.org/confluence/display/KAFKA/KIP-431%3A+Support+of+printing+a
hanks for picking this up. I've reviewed the KIP document and
> > > > the threads you linked. I think we may want to make more
> > > > improvements in the future to the printing of headers in particular,
> > > > but this KIP seems like a clear benefit already. I
3, partition 0" is your comment not the
> printed words:-) Am I correct?
>
>
>
> 发件人: Badai Aqrandista
> 发送时间: 2020年7月9日 17:29
> 收件人: dev
> 主题: Re: [VOTE] KIP-431: Support of printing additional ConsumerRecord fields
> in DefaultMessageFormatter
>
>
uld be accomplished by a complementary usage
> description. What do you think?
>
> On 2020/06/21 13:39:36, Badai Aqrandista wrote:
> > Excellent.>
> >
> > Would like to hear more feedback from others.>
> >
> > On Sat, Jun 20, 2020 at 1:27 AM David Jacot
Hi all
The vote for KIP-431 has passed with 3 binding and 1 non-binding +1s, and
no objections.
Thanks everyone for reviews and feedback.
Regards,
Badai
On Fri, Jul 10, 2020 at 5:22 PM Badai Aqrandista wrote:
>
> Hu
>
> I would make it more readable and move the key next to th
|value2
Regards
Badai
On Sun, Jun 21, 2020 at 11:39 PM Badai Aqrandista wrote:
>
> Excellent.
>
> Would like to hear more feedback from others.
>
> On Sat, Jun 20, 2020 at 1:27 AM David Jacot wrote:
> >
> > Hi Badai,
> >
> > Thanks for your reply.
> >
Hi all
I have created a PR for KIP-431 against the latest trunk:
https://github.com/apache/kafka/pull/9099
Please review.
Regards
Badai
On Tue, Jul 21, 2020 at 2:13 AM Matthias J. Sax wrote:
>
> Thanks Badai. LGTM.
>
> On 7/19/20 4:26 PM, Badai Aqrandista wrote:
> > Hi all
&
Hi all
I have made additional changes to the PR as per review from David Jacot.
Please review.
Regards
Badai
On Wed, Jul 29, 2020 at 11:17 PM Badai Aqrandista
wrote:
> Hi all
>
> I have created a PR for KIP-431 against the latest trunk:
> https://github.com/apache/kafka/pull/909
not exist
before. Apart from "print.partition=true", if a user does not use any
new parameters, then the output of console consumer will look the same
as before.
-
What do you think?
Regards
Badai
On Wed, Aug 5, 2020 at 12:49 AM Badai Aqrandista wrote:
>
> Hi all
>
>
into my head:
>
> 1. CreateTime:1592475472398|key1|3|<0>|h1=v1,h2=v2|value1
> 2. CreateTime:1592475472398|key1|3|offset=0|h1=v1,h2=v2|value1
>
> I prefer the option #1 which could be accomplished by a complementary usage
> description. What do you think?
>
> On 20
Hi everyone
I have opened this KIP to have client.dns.lookup default value changed to
"use_all_dns_ips".
https://cwiki.apache.org/confluence/display/KAFKA/KIP-602%3A+Change+default+value+for+client.dns.lookup
Feedback appreciated.
PS: I'm new here so please let me know if I miss anything.
--
IP-235? That was the reason why we did not do it previously.
>
> Ismael
>
> On Mon, Apr 27, 2020 at 5:46 PM Badai Aqrandista
> wrote:
>
>> Hi everyone
>>
>> I have opened this KIP to have client.dns.lookup default value changed to
>> "use_all_dns_ips&q
Ismael
PR created: https://github.com/apache/kafka/pull/8644/files
Also, as this is my first PR, please let me know if I missed anything.
Thanks
Badai
On Mon, May 11, 2020 at 8:19 AM Badai Aqrandista wrote:
> Ismael
>
> Thank you for responding.
>
> KIP-235 modif
Ismael
What do you think of the PR and the explanation regarding the issue raised
in KIP-235?
Should I go ahead and build a proper PR?
Thanks
Badai
On Mon, May 11, 2020 at 8:53 AM Badai Aqrandista wrote:
> Ismael
>
> PR created: https://github.com/apache/kafka/pull/8644/files
>
Hi All,
I would like to start the vote on KIP-602: Change default value for
client.dns.lookup
For reference, here is the KIP wiki:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-602%3A+Change+default+value+for+client.dns.lookup
And discussion thread:
https://lists.apache.org/thread.html
used - that is the current behaviour
> > for
> > > > `use_all_dns_ips`. Since we are changing `default` to be exactly the
> > > same
> > > > as `use_all_dns_ips`, it will be good to mention that explicitly
> under
> > > > Public Interfaces.
>
The vote for KIP-602 has passed with 5 binding and 1 non-binding +1s, and
no objections.
Thanks everyone for reviews and feedback,
Badai
On Mon, May 25, 2020 at 12:21 PM Gwen Shapira wrote:
> +1 (binding)
>
> Thank you!
>
> On Fri, May 22, 2020 at 1:40 AM Badai Aqrandista
&g
tests.
What do you think?
Thanks
Badai
On Fri, May 22, 2020 at 6:45 PM Badai Aqrandista wrote:
> Voting thread has been posted.
>
> KIP-602 page has been updated with suggestions from Rajini.
>
> Thanks
> Badai
>
> On Fri, May 22, 2020 at 6:00 AM Ismael Juma wrote:
>
> config default and avoiding the temporary `use_first_dns_ip` option makes
> > sense.
> >
> > Regards,
> >
> > Rajini
> >
> >
> > On Thu, May 28, 2020 at 4:49 PM Badai Aqrandista
> > wrote:
> >
> > > Ismael/Rajini
Hi all
I have just created KIP-760
(https://cwiki.apache.org/confluence/display/KAFKA/KIP-760%3A+Increase+minimum+value+of+segment.ms+and+segment.bytes).
I created this KIP because I have seen so many Kafka brokers crash due
to small segment.ms and/or segment.bytes.
Please let me know what you t
so this KIP would not have impact on that particular
> use case.
>
> -James
>
> > On Jul 6, 2021, at 2:23 PM, Badai Aqrandista
> > wrote:
> >
> > Hi all
> >
> > I have just created KIP-760
> > (https://cwiki.apache.org/confluence/display/KA
e, but could you maybe add some evidence to
> support your proposed values? I'm sure they come from experience but I
> don't think they are obvious and so may appear arbitrary.
>
> Ryanne
>
>
> On Tue, Jul 6, 2021, 4:23 PM Badai Aqrandista
> wrote:
>
> >
Hi all
I would like to start a vote on KIP-760
(https://cwiki.apache.org/confluence/display/KAFKA/KIP-760%3A+Minimum+value+for+segment.ms+and+segment.bytes).
I created this KIP because I have seen so many Kafka brokers crash due
to small segment.ms and/or segment.bytes.
--
Thanks,
Badai
Hi all
Just trying to bump this thread.
Thanks
Badai
On Sat, Sep 11, 2021 at 1:07 AM Badai Aqrandista wrote:
>
> Hi all
>
> I would like to start a vote on KIP-760
> (https://cwiki.apache.org/confluence/display/KAFKA/KIP-760%3A+Minimum+value+for+segment.ms+and+segment.bytes)
Badai Aqrandista created KAFKA-7754:
---
Summary: zookeeper-security-migration.sh sets the root ZNode as
world-readable
Key: KAFKA-7754
URL: https://issues.apache.org/jira/browse/KAFKA-7754
Project
Badai Aqrandista created KAFKA-7760:
---
Summary: Add broker configuration to set minimum value for
segment.bytes and segment.ms
Key: KAFKA-7760
URL: https://issues.apache.org/jira/browse/KAFKA-7760
Badai Aqrandista created KAFKA-6939:
---
Summary: Change the default of
log.message.timestamp.difference.max.ms to 500 years
Key: KAFKA-6939
URL: https://issues.apache.org/jira/browse/KAFKA-6939
Badai Aqrandista created KAFKA-6756:
---
Summary: client.id and group.id validation in the old vs new
consumer
Key: KAFKA-6756
URL: https://issues.apache.org/jira/browse/KAFKA-6756
Project: Kafka
Badai Aqrandista created KAFKA-7379:
---
Summary: send.buffer.bytes should be allowed to set -1 in
KafkaStreams
Key: KAFKA-7379
URL: https://issues.apache.org/jira/browse/KAFKA-7379
Project: Kafka
Badai Aqrandista created KAFKA-7467:
---
Summary: NoSuchElementException is raised because controlBatch is
empty
Key: KAFKA-7467
URL: https://issues.apache.org/jira/browse/KAFKA-7467
Project: Kafka
Badai Aqrandista created KAFKA-8501:
---
Summary: Remove key and value from exception message
Key: KAFKA-8501
URL: https://issues.apache.org/jira/browse/KAFKA-8501
Project: Kafka
Issue Type
Badai Aqrandista created KAFKA-8546:
---
Summary: Call System#runFinalization to avoid memory leak caused
by JDK-6293787
Key: KAFKA-8546
URL: https://issues.apache.org/jira/browse/KAFKA-8546
Project
Badai Aqrandista created KAFKA-8562:
---
Summary: SASL_SSL still performs reverse DNS lookup despite
KAFKA-5051
Key: KAFKA-8562
URL: https://issues.apache.org/jira/browse/KAFKA-8562
Project: Kafka
Badai Aqrandista created KAFKA-10529:
Summary: Controller should throttle partition reassignment
Key: KAFKA-10529
URL: https://issues.apache.org/jira/browse/KAFKA-10529
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-10872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Badai Aqrandista resolved KAFKA-10872.
--
Resolution: Fixed
> Log broker configuration prefixed with "liste
Badai Aqrandista created KAFKA-9275:
---
Summary: Print assignment and IP address in the log message when
consumer leaves/removed from the group
Key: KAFKA-9275
URL: https://issues.apache.org/jira/browse/KAFKA
Badai Aqrandista created KAFKA-9459:
---
Summary: MM2 sync topic config does work
Key: KAFKA-9459
URL: https://issues.apache.org/jira/browse/KAFKA-9459
Project: Kafka
Issue Type: Bug
Badai Aqrandista created KAFKA-9540:
---
Summary: Application getting "Could not find the standby task 0_4
while closing it" error
Key: KAFKA-9540
URL: https://issues.apache.org/jira/browse/
Badai Aqrandista created KAFKA-9684:
---
Summary: Add support for SNI names in SSL request
Key: KAFKA-9684
URL: https://issues.apache.org/jira/browse/KAFKA-9684
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-9684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Badai Aqrandista resolved KAFKA-9684.
-
Resolution: Not A Problem
Java 7 should include SNI names by default.
> Add support
Badai Aqrandista created KAFKA-13040:
Summary: Increase minimum value of segment.ms and segment.bytes
Key: KAFKA-13040
URL: https://issues.apache.org/jira/browse/KAFKA-13040
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-7760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Badai Aqrandista resolved KAFKA-7760.
-
Resolution: Duplicate
> Add broker configuration to set minimum value for segment.by
[
https://issues.apache.org/jira/browse/KAFKA-7760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Badai Aqrandista reopened KAFKA-7760:
-
Reopening issue and making this the main ticket for KIP-760
> Add broker configuration
[
https://issues.apache.org/jira/browse/KAFKA-13040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Badai Aqrandista resolved KAFKA-13040.
--
Resolution: Duplicate
> Increase minimum value of segment.ms and segment.by
Badai Aqrandista created KAFKA-10776:
Summary: JMX metric RequestsPerSec requires API version to access
Key: KAFKA-10776
URL: https://issues.apache.org/jira/browse/KAFKA-10776
Project: Kafka
Badai Aqrandista created KAFKA-10872:
Summary: Log broker configuration prefixed with "listener.name.*"
Key: KAFKA-10872
URL: https://issues.apache.org/jira/browse/KAFKA-10872
Proj
Badai Aqrandista created KAFKA-12162:
Summary: Kafka broker continued to run after failing to create
"/brokers/ids/X" znode.
Key: KAFKA-12162
URL: https://issues.apache.org/jira/browse/K
Badai Aqrandista created KAFKA-12163:
Summary: Controller should ensure zkVersion is monotonically
increasing when sending UpdateMetadata requests.
Key: KAFKA-12163
URL: https://issues.apache.org/jira/browse
52 matches
Mail list logo
