Re: [DISCUSS] KIP-371: Add a configuration to build custom SSL principal name

Thanks. I am also leaning towards option 2, as it will help the consistency of expressing such mapping between sasl and ssl. -Harsha On Tue, Sep 18, 2018, at 8:27 PM, Manikumar wrote: > Hi Harsha, > > Thanks for the review. Yes, As mentioned on the motivation section, this is > to simply

Request for contributor permissions

as title JIRA ID: doniel0...@gmail.com Cwiki ID: DANIEL HUANG Thanks!

confirm subscribe to dev@kafka.apache.org

JIRA ID: doniel0...@gmail.com Cwiki ID: DANIEL HUANG

Re: [DISCUSS] KIP-371: Add a configuration to build custom SSL principal name

Hi Harsha, Thanks for the review. Yes, As mentioned on the motivation section, this is to simply extracting fields from the certificates for the common use cases. Yes, we are not supporting extracting SubjectAltName using this KIP. Thanks, On Wed, Sep 19, 2018 at 8:29 AM Harsha wrote: > Hi

Re: A question about kafka streams API

Hey Yui, Sorry, I haven't had a chance to respond. I've got a pretty busy couple of weeks coming up, so I don't know when I'll look at this, but I find this puzzling. I'll save your email and try what you said to see if I can figure it out. Thanks for the repro code. Let me know if you figure it

Re: [DISCUSS] KIP-371: Add a configuration to build custom SSL principal name

Hi Manikumar, I am interested to know the reason for exposing this config, given a user has access to PrincipalBuilder interface to build their interpretation of an identity from the X509 certificates. Is this to simplify extraction of identity? and also there are other use cases where

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

See

Re: Accessing Topology Builder

Jorge: I have a crazy idea off the top of my head. Would something as low-tech using KSteam.peek calls on either side of certain processors to record start and end times work? Thanks, Bill On Tue, Sep 18, 2018 at 4:38 PM Guozhang Wang wrote: > Jorge: > > My suggestion was to let your users

[jira] [Created] (KAFKA-7420) Global stores should be guarded as read-only for regular tasks

Matthias J. Sax created KAFKA-7420: -- Summary: Global stores should be guarded as read-only for regular tasks Key: KAFKA-7420 URL: https://issues.apache.org/jira/browse/KAFKA-7420 Project: Kafka

Re: [VOTE] KIP-291: Have separate queues for control requests and data requests

Hi, Lucas, When upgrading to a minor release, I think the expectation is that a user wouldn't need to make any config changes, other than the usual inter.broker.protocol. If we require other config changes during an upgrade, then it's probably better to do that in a major release. Regarding your

Re: Accessing Topology Builder

Jorge: My suggestion was to let your users to implement on the TracingProcessorSupplier / TracingProcessor directly instead of the base-line ProcessorSupplier / Processor. Would that work for you? Guozhang On Tue, Sep 18, 2018 at 8:02 AM, Jorge Esteban Quilcate Otoya <

Re: Accessing Topology Builder

Hi Jorge, Thanks for the clarifications. Yes, I'm also not sure what "built-in tracing" would look like, and it may not be a good idea. FWIW, though, I was not thinking of something like "rich functions". Rather, I was imagining that Streams could just always record spans in headers as it

Semi Proposal: Unclean Leadership Elections and Out of Sync Brokers

Hey! I’m seeing behaviour I didn’t expect, and I’d like some expert opinions on it. (TL;DR min.insync.replicas=2 and acks=all isn’t enough to tolerate losing a leader transparently and safely, but maybe it could be) Lets say we have a topic with one partition, replication factor 3. Leader 0,

RE: kafka dev

Hi, Are you interested in the Kafka position I have. Erica Parker | Senior Technical Recruiter INT Technologies – A Nationally Recognized Veteran Owned Business C: (720) 483-7059 W: (720)735-4829 Stay connected with us: Ask your INT representative about our H1B transfer program. Please visit

Re: [VOTE] KIP 368: Allow SASL Connections to Periodically Re-Authenticate

+1 (non binding) > On Sep 18, 2018, at 1:18 PM, michael.kamin...@nytimes.com wrote: > > > > On 2018/09/18 14:59:09, Ron Dagostino wrote: >> Hi everyone. I would like to start the vote for KIP-368: >>

Re: [VOTE] KIP 368: Allow SASL Connections to Periodically Re-Authenticate

On 2018/09/18 14:59:09, Ron Dagostino wrote: > Hi everyone. I would like to start the vote for KIP-368: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-368%3A+Allow+SASL+Connections+to+Periodically+Re-Authenticate > > This KIP proposes adding the ability for SASL clients (and

Re: [VOTE] KIP 368: Allow SASL Connections to Periodically Re-Authenticate

On 2018/09/18 14:59:09, Ron Dagostino wrote: > Hi everyone. I would like to start the vote for KIP-368: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-368%3A+Allow+SASL+Connections+to+Periodically+Re-Authenticate > > This KIP proposes adding the ability for SASL clients (and

Re: [VOTE] KIP 368: Allow SASL Connections to Periodically Re-Authenticate

+1 (non-bonding) We would very much like to see this merged. Thanks, Boerge. > On Sep 18, 2018, at 11:51, Edoardo Comar wrote: > > +1 (non binding) > > Thanks Ron & Rajini ! > -- > > Edoardo Comar > > IBM Message Hub > > IBM UK Ltd,

Re: [VOTE] KIP 368: Allow SASL Connections to Periodically Re-Authenticate

+1 (non binding) Thanks Ron & Rajini ! -- Edoardo Comar IBM Message Hub IBM UK Ltd, Hursley Park, SO21 2JN From: Ron Dagostino To: dev@kafka.apache.org Date: 18/09/2018 16:09 Subject:[VOTE] KIP 368: Allow SASL Connections to

Re: [VOTE] KIP-372: Naming Repartition Topics for Joins and Grouping

All, In starting work on the PR for KIP-372, the Grouped interface needed some method renaming to be more consistent with the other configuration classes (Joined, Produced, etc.). As such I've updated the Grouped code section of the KIP. As these changes address a comment from Matthias on the

Re: [DISCUSS] KIP-371: Add a configuration to build custom SSL principal name

Hi Rajini, I don't have strong reasons for rejecting Option 2. I just felt Option 1 is sufficient for the common use-cases (extracting single field, like CN etc..). We are open to go with Option 2, for more flexible mapping mechanism. Let us know, your preference. Thanks, On Tue, Sep 18, 2018

Re: Accessing Topology Builder

final StreamsBuilder builder = kafkaStreamsTracing.builder();Thanks Guozhang and John. @Guozhang: > I'd suggest to provide a > WrapperProcessorSupplier for the users than modifying > InternalStreamsTopology: more specifically, you can provide an > `abstract WrapperProcessorSupplier > implements

[VOTE] KIP 368: Allow SASL Connections to Periodically Re-Authenticate

Hi everyone. I would like to start the vote for KIP-368: https://cwiki.apache.org/confluence/display/KAFKA/KIP-368%3A+Allow+SASL+Connections+to+Periodically+Re-Authenticate This KIP proposes adding the ability for SASL clients (and brokers when a SASL mechanism is the inter-broker protocol) to

Re: [DISCUSS] KIP 368: Allow SASL Connections to Periodically Re-Authenticate

HI Rajini. The KIP is updated as summarized below, and I will start a vote immediately. << wrote: > Hi Ron, > > Thanks for the updates. The KIP looks good. A few comments and minor points > below, but feel free to start vote to try and get it into 2.1.0. More > community feedback will be really

Re: [DISCUSS] KIP-302 - Enable Kafka clients to use all DNS resolved IP addresses

Yes I should, should't I ? :-) -- Edoardo Comar IBM Message Hub IBM UK Ltd, Hursley Park, SO21 2JN From: Rajini Sivaram To: dev Date: 18/09/2018 15:33 Subject:Re: [DISCUSS] KIP-302 - Enable Kafka clients to use all DNS

[VOTE] KIP-302 - Enable Kafka clients to use all DNS resolved IP addresses

Hi All, I'd like to start the vote on KIP-302: https://cwiki.apache.org/confluence/display/KAFKA/KIP-302+-+Enable+Kafka+clients+to+use+all+DNS+resolved+IP+addresses We'd love to get this in 2.1.0 Kip freeze is just a few days away ... please cast your votes :-):-) Thanks!! Edo

Re: [DISCUSS] KIP-371: Add a configuration to build custom SSL principal name

Hi Manikumar, It wasn't entirely clear to me why Option 2 was rejected. On Tue, Sep 18, 2018 at 7:47 AM, Manikumar wrote: > Hi All, > > We would like to go with Option 1, which adds a new configuration parameter > pair of the form: > ssl.principal.mapping.pattern, ssl.principal.mapping.value.

Jenkins build is back to normal : kafka-trunk-jdk10 #500

See

Re: [DISCUSS] KIP-302 - Enable Kafka clients to use all DNS resolved IP addresses

Hi Edo, The KIP looks good, perhaps you can start vote on this to get it in time for 2.1.0? Regards, Rajini On Tue, Sep 18, 2018 at 1:58 PM, Eno Thereska wrote: > Got it, thanks! > > Eno > > On Tue, Sep 18, 2018 at 1:41 PM, Edoardo Comar wrote: > > > Hi Eno, > > > > we implement network

Re: [VOTE] KIP-372: Naming Repartition Topics for Joins and Grouping

+1 (non-binding) Thanks! On Mon, Sep 17, 2018 at 7:29 PM Dongjin Lee wrote: > Great improvements. +1. (Non-binding) > > On Tue, Sep 18, 2018 at 5:14 AM Matthias J. Sax > wrote: > > > +1 (binding) > > > > -Matthias > > > > On 9/17/18 1:12 PM, Guozhang Wang wrote: > > > +1 from me, thanks Bill

Build failed in Jenkins: kafka-trunk-jdk8 #2973

See Changes: [lindong28] KAFKA-7332; Update CORRUPT_MESSAGE exception message description [rajinisivaram] KAFKA-7388 equal sign in property value for password (#5630) --

Re: [DISCUSS] KIP-302 - Enable Kafka clients to use all DNS resolved IP addresses

Got it, thanks! Eno On Tue, Sep 18, 2018 at 1:41 PM, Edoardo Comar wrote: > Hi Eno, > > we implement network separation and the machines fronting the brokers > (call them LBs for simplicity) will route the connection to the correct > broker based on the TLS SNI. We register in the DNS multiple

Re: [DISCUSS] KIP-302 - Enable Kafka clients to use all DNS resolved IP addresses

Hi Eno, we implement network separation and the machines fronting the brokers (call them LBs for simplicity) will route the connection to the correct broker based on the TLS SNI. We register in the DNS multiple A records (the IPs of all LBs) for each the brokers' hostnames. As long as all the

Build failed in Jenkins: kafka-trunk-jdk10 #499

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H23 (ubuntu xenial) in workspace

Build failed in Jenkins: kafka-trunk-jdk10 #498

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H23 (ubuntu xenial) in workspace

Re: [DISCUSS] KIP 368: Allow SASL Connections to Periodically Re-Authenticate

Hi Ron, Thanks for the updates. The KIP looks good. A few comments and minor points below, but feel free to start vote to try and get it into 2.1.0. More community feedback will be really useful. 1) It may be useful to have a metric of expired connections killed by the broker. There could be a

[jira] [Created] (KAFKA-7419) Rolling sum for high frequency sream

Stanislav Bausov created KAFKA-7419: --- Summary: Rolling sum for high frequency sream Key: KAFKA-7419 URL: https://issues.apache.org/jira/browse/KAFKA-7419 Project: Kafka Issue Type: Wish

Build failed in Jenkins: kafka-trunk-jdk10 #497

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H23 (ubuntu xenial) in workspace

[jira] [Resolved] (KAFKA-7388) An equal sign in a property value causes the broker to fail

[ https://issues.apache.org/jira/browse/KAFKA-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7388. -- Resolution: Fixed Fix Version/s: 2.1.0 > An equal sign in a property value causes the broker to

Re: [DISCUSS] KIP-302 - Enable Kafka clients to use all DNS resolved IP addresses

Hi folks, Could you expand the motivation a bit? When would it make sense to use an LB in front of Kafka brokers? A client needs to access each broker directly to consume the data in that broker and cannot be redirected to another broker. What exact scenario are you seeing that needs this KIP?

kafka dev

hi, kafka

Build failed in Jenkins: kafka-trunk-jdk10 #496

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H23 (ubuntu xenial) in workspace

Re: [DISCUSS] KIP-302 - Enable Kafka clients to use all DNS resolved IP addresses

Bumping this thread It's a relatively small change that would help cloud environments with load balancers fronting brokers On Tue, Sep 11, 2018 at 3:01 PM Edoardo Comar wrote: > > Hi all, > after some time we updated KIP-302 to reuse the config key introduced by > KIP-235, with a different value

[jira] [Created] (KAFKA-7418) Add '--help' option to all available Kafka CLI commands

Attila Sasvari created KAFKA-7418: - Summary: Add '--help' option to all available Kafka CLI commands Key: KAFKA-7418 URL: https://issues.apache.org/jira/browse/KAFKA-7418 Project: Kafka

Build failed in Jenkins: kafka-trunk-jdk10 #495

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H23 (ubuntu xenial) in workspace

[jira] [Resolved] (KAFKA-7332) Improve error message when trying to produce message without key for compacted topic

[ https://issues.apache.org/jira/browse/KAFKA-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-7332. - Resolution: Fixed > Improve error message when trying to produce message without key for > compacted

Re: [DISCUSS] KIP-371: Add a configuration to build custom SSL principal name

Hi All, We would like to go with Option 1, which adds a new configuration parameter pair of the form: ssl.principal.mapping.pattern, ssl.principal.mapping.value. This will fulfill the requirement for most of the common use cases. We would like to include the KIP in the upcoming release. If there

[jira] [Resolved] (KAFKA-7322) Fix race condition between log cleaner thread and log retention thread when topic cleanup policy is updated

[ https://issues.apache.org/jira/browse/KAFKA-7322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-7322. - Resolution: Fixed > Fix race condition between log cleaner thread and log retention thread when > topic