Re: add as contributor

Hi Brad, What's your user id? --Vahid On Fri, Mar 29, 2019, 04:36 Brad Ellis wrote: > Hi, > > I'd like to contribute to the kafka project. Can you add me as a > contributor? > In particular, I'm planning on picking up this JIRA as a first issue: > > https://issues.apache.org/jira/browse/KAFKA

Re: [VOTE] KIP-443: Return to default segment.ms and segment.index.bytes in Streams repartition topics

+1 (nonbinding) from me. On Thu, Mar 28, 2019 at 7:08 PM Guozhang Wang wrote: > Hello folks, > > I'd like to directly start a voting thread on this simple KIP to change the > default override values for repartition topics: > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-443%3A+Return

[jira] [Created] (KAFKA-8174) Can't call arbitrary SimpleBenchmarks tests from streams_simple_benchmark_test.py

Sophie Blee-Goldman created KAFKA-8174: -- Summary: Can't call arbitrary SimpleBenchmarks tests from streams_simple_benchmark_test.py Key: KAFKA-8174 URL: https://issues.apache.org/jira/browse/KAFKA-8174

Re: [DISCUSS] KIP-433: Provide client API version to authorizer

@Colin McCabe I did think about that option. Yes, for most users, it's much easier to understand Kafka version, rather than API version. However, the existing Kafka clients only report API versions in the Kafka requests. So, the brokers can only block clients by API versions rather than the real

[VOTE] KIP-443: Return to default segment.ms and segment.index.bytes in Streams repartition topics

Hello folks, I'd like to directly start a voting thread on this simple KIP to change the default override values for repartition topics: https://cwiki.apache.org/confluence/display/KAFKA/KIP-443%3A+Return+to+default+segment.ms+and+segment.index.bytes+in+Streams+repartition+topics The related PR

add as contributor

Hi, I'd like to contribute to the kafka project. Can you add me as a contributor? In particular, I'm planning on picking up this JIRA as a first issue: https://issues.apache.org/jira/browse/KAFKA-8157 Best regards, Brad Ellis https://github.com/tbradellis

[jira] [Created] (KAFKA-8173) Kafka Errors after version upgrade from 0.10.2.2 to 2.1.1

Amit Anand created KAFKA-8173: - Summary: Kafka Errors after version upgrade from 0.10.2.2 to 2.1.1 Key: KAFKA-8173 URL: https://issues.apache.org/jira/browse/KAFKA-8173 Project: Kafka Issue Type

Jenkins build is back to normal : kafka-trunk-jdk8 #3498

See

Re: [VOTE] KIP-434: Dead replica fetcher and log cleaner metrics

Sorry, the end of the message cut off. So I tried to be consistent with the convention in LogManager, hence the hyphens and in AbstractFetcherManager, hence the camel case. It would be nice though to decide with one convention across the whole project, however it requires a major refactor (especia

Re: [VOTE] KIP-434: Dead replica fetcher and log cleaner metrics

Hi Dhruvil, Thanks for the feedback and the vote. I fixed the typo in the KIP. The naming is interesting though. Unfortunately kafka overall is not consistent in metric naming but at least I tried to be consistent among the other metrics used in LogManager On Thu, Mar 28, 2019 at 7:32 PM Dhruvil

[jira] [Created] (KAFKA-8172) FileSystemException: The process cannot access the file because it is being used by another process

Bharat Kondeti created KAFKA-8172: - Summary: FileSystemException: The process cannot access the file because it is being used by another process Key: KAFKA-8172 URL: https://issues.apache.org/jira/browse/KAFKA-817

Re: MirrorMaker 2.0 and Streams interplay (topic naming control)

Hi Paul, No problem! And please let us know how it goes. Thanks, -John On Wed, Mar 27, 2019 at 9:13 PM Paul Whalen wrote: > John, > > You make a good case for it already being a public API, so my nerves are > definitely eased on that front. I do think we have a path to move forward > with the

Re: [VOTE] KIP-434: Dead replica fetcher and log cleaner metrics

Thanks for the KIP, Viktor! This is a useful addition. +1 overall. Minor nits: > I propose to add three gauge: DeadFetcherThreadCount for the fetcher threads, log-cleaner-dead-thread-count for the log cleaner. I think you meant two instead of three. Also, would it make sense to name these metrics

[VOTE] KIP-434: Dead replica fetcher and log cleaner metrics

Hi All, I'd like to start a vote on KIP-434. This basically would add a metrics to count dead threads in ReplicaFetcherManager and LogCleaner to allow monitoring systems to alert based on this. The KIP link: https://cwiki.apache.org/confluence/display/KAFKA/KIP-434%3A+Add+Replica+Fetcher+and+Log+

Re: [VOTE] KIP-434: Add Replica Fetcher and Log Cleaner Count Metrics

Thanks for the heads-up Gwen, I'll resend it with a different title. On Thu, Mar 28, 2019 at 6:26 PM Gwen Shapira wrote: > Gmail automatically folded the vote into the old discussion thread. I > suggest resending with a sufficiently different title so no one will miss > it. > > On Thu, Mar 28, 2

Re: [VOTE] KIP-434: Add Replica Fetcher and Log Cleaner Count Metrics

Gmail automatically folded the vote into the old discussion thread. I suggest resending with a sufficiently different title so no one will miss it. On Thu, Mar 28, 2019 at 8:05 AM Viktor Somogyi-Vass wrote: > Hi All, > > I'd like to start a vote on KIP-434. > This basically would add a metrics t

[jira] [Created] (KAFKA-8171) callback needs to be null when addStopReplicaRequestForBrokers when replica state transits to offline

kehu created KAFKA-8171: --- Summary: callback needs to be null when addStopReplicaRequestForBrokers when replica state transits to offline Key: KAFKA-8171 URL: https://issues.apache.org/jira/browse/KAFKA-8171 Pro

RE: Unsubscribe request

Hello Admin Please also remove my email from the list. Thanks Raymond -Original Message- From: Biswajit Ghosh Sent: Thursday, March 28, 2019 11:09 AM To: dev@kafka.apache.org Subject: Unsubscribe request Hi Admin, Can you please unsubscribe my email address (biswaji...@aqbsolutions.

Re: Unsubscribe request

Hello Biswajit, It's self-service :) https://kafka.apache.org/contact See you in a few months. Guozhang On Thu, Mar 28, 2019 at 8:09 AM Biswajit Ghosh wrote: > Hi Admin, > > Can you please unsubscribe my email address (biswaji...@aqbsolutions.com) > from Kafka dev group, currently I have no t

Unsubscribe request

Hi Admin, Can you please unsubscribe my email address (biswaji...@aqbsolutions.com) from Kafka dev group, currently I have no time to develop Kafka, I'll be with you guys in a few months I hope. Thanks. -- Regards, biswajitGhosh

[VOTE] KIP-434: Add Replica Fetcher and Log Cleaner Count Metrics

Hi All, I'd like to start a vote on KIP-434. This basically would add a metrics to count dead threads in ReplicaFetcherManager and LogCleaner to allow monitoring systems to alert based on this. The KIP link: https://cwiki.apache.org/confluence/display/KAFKA/KIP-434%3A+Add+Replica+Fetcher+and+Log+

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

Hi Harsha. I'm excited about this potential feature. Did you consider storing the information about the remote segments in a Kafka topic as opposed to in the remote storage itself? The topic would need infinite retention (or it would need to be compacted) so as not to itself be sent to cold stor

Re: [DISCUSSION] KIP-418: A method-chaining way to branch KStream

Ivan, Maybe I’m missing the point, but I believe the stream.branch() solution supports this. The couponIssuer::set* consumers will be invoked as they’re added, not during streamsBuilder.build(). So the user still ought to be able to call couponIssuer.coupons() afterward and depend on the branch

Re: [DISCUSS] KIP-437: Custom replacement for MaskField SMT

вт, 19 мар. 2019 г. в 17:59, Valeria Vasylieva : > Hi Adam, > > Thank you for your response! > Dear community members, do you have any other thoughts on this KIP? Would > be great if you share them! > > Regards, > > Valeria > > сб, 16 мар. 2019 г. в 18:16, Adam Bellemare : > >> Hi Valeria >> >> I

Re: [DISCUSS] KIP-434: Add Replica Fetcher and Log Cleaner Count Metrics

Hey Folks, Since there were no discussions on this in the past two weeks I'll create a VOTE thread soon. Thanks, Viktor On Thu, Mar 14, 2019 at 7:05 PM Viktor Somogyi-Vass wrote: > Hey Stanislav, > > Sorry for the delay on this. In the meantime I realized that the dead > fetchers won't be remo

[jira] [Created] (KAFKA-8170) To add kafka data at rest encryption

Akash created KAFKA-8170: Summary: To add kafka data at rest encryption Key: KAFKA-8170 URL: https://issues.apache.org/jira/browse/KAFKA-8170 Project: Kafka Issue Type: New Feature Componen

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

Thanks Harsha, A couple of comments: Performance & durability -- - would be good to have more discussion on performance implications of tiering. Copying the data from the local storage to the remote storage is going to be expensive in terms of network bandwidth and

Re: [DISCUSSION] KIP-418: A method-chaining way to branch KStream

Hi Paul! The idea to postpone the wiring of branches to the streamsBuilder.build() also looked great for me at first glance, but --- > the newly branched streams are not available in the same scope as each other. That is, if we wanted to merge them back together again I don't see a way to d

[jira] [Created] (KAFKA-8169) Wrong topic on streams quick start documentation

Tcheutchoua Steve created KAFKA-8169: Summary: Wrong topic on streams quick start documentation Key: KAFKA-8169 URL: https://issues.apache.org/jira/browse/KAFKA-8169 Project: Kafka Issue