Build failed in Jenkins: kafka-trunk-jdk11 #1641

See Changes: [github] KAFKA-10002; Improve performances of StopReplicaRequest with large -- [...truncated 3.20 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

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

See Changes: [github] KAFKA-10044 Deprecate ConsumerConfig#addDeserializerToConfig and Prod… [github] KAFKA-10002; Improve performances of StopReplicaRequest with large

Re: [VOTE] KIP-614: Add Prefix Scan support for State Stores

Thanks for the KIP, Sagar! I’m +1 (binding) -John On Sun, Jul 12, 2020, at 02:05, Sagar wrote: > Hi All, > > I would like to start a new voting thread for the below KIP to add prefix > scan support to state stores: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 614%3A+Add+Prefix+

[jira] [Resolved] (KAFKA-10192) Flaky test BlockingConnectorTest#testBlockInConnectorStop

[ https://issues.apache.org/jira/browse/KAFKA-10192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantine Karantasis resolved KAFKA-10192. Resolution: Fixed > Flaky test BlockingConnectorTest#testBlockInConnectorS

[jira] [Resolved] (KAFKA-10240) Sink tasks should not throw WakeupException on shutdown

[ https://issues.apache.org/jira/browse/KAFKA-10240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantine Karantasis resolved KAFKA-10240. Resolution: Fixed > Sink tasks should not throw WakeupException on shutdow

Build failed in Jenkins: kafka-trunk-jdk14 #289

See Changes: [github] KAFKA-10002; Improve performances of StopReplicaRequest with large -- [...truncated 3.20 MB...] org.apache.kafka.streams.TopologyTestDriverTest > s

Build failed in Jenkins: kafka-trunk-jdk14 #288

See Changes: [github] KAFKA-10044 Deprecate ConsumerConfig#addDeserializerToConfig and Prod… -- [...truncated 3.20 MB...] org.apache.kafka.streams.scala.kstream.KTableTe

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

See Changes: [github] KAFKA-6453: Document how timestamps are computed for aggregations and -- [...truncated 6.35 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

[jira] [Resolved] (KAFKA-10002) Improve performances of StopReplicaRequest with large number of partitions to be deleted

[ https://issues.apache.org/jira/browse/KAFKA-10002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-10002. - Fix Version/s: 2.7.0 Resolution: Fixed merged the PR to trunk > Improve performances of StopRepl

Build failed in Jenkins: kafka-trunk-jdk14 #287

See Changes: [github] KAFKA-6453: Document how timestamps are computed for aggregations and -- [...truncated 3.20 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Re: Permissions to create and assign JIRA issues

Added. Happy contributing! On Mon, Jul 13, 2020 at 2:48 PM Sankalp Bhatia wrote: > Hi devs, > > I would like to contribute and will be grateful if someone can grant me the > permissions to create and assign JIRA issues. > > my id is : sankalpbhatia > > Thanks in advance! >

Permissions to create and assign JIRA issues

Hi devs, I would like to contribute and will be grateful if someone can grant me the permissions to create and assign JIRA issues. my id is : sankalpbhatia Thanks in advance!

Re: [VOTE] KIP-554: Add Broker-side SCRAM Config API

Hi Colin. I wanted to explicitly identify a side-effect that I think derives from having deletions separated out from the AlterScramUsersRequest and put in their own DeleteScramUsersRequest. The command line invocation of kafka-configs can specify alterations and deletions simultaneously: it is en

Re: [DISCUSS] KIP-631: The Quorum-based Kafka Controller

Let me add a little more color to my question about the controller.id. I have been assuming that each process would run a single Raft replication thread for the metadata quorum, just that its role might be different. Some would be voters and some would be observers. To me, that suggests that broker

Re: [VOTE] KIP-554: Add Broker-side SCRAM Config API

Thanks for the clarification, Colin. +1 binding from me -David On Mon, Jul 13, 2020 at 3:40 PM Colin McCabe wrote: > Thanks, Boyang. Fixed. > > best, > Colin > > On Mon, Jul 13, 2020, at 08:43, Boyang Chen wrote: > > Thanks for the update Colin. One nit comment to fix the RPC type > > for Alte

Re: [VOTE] KIP-554: Add Broker-side SCRAM Config API

Thanks, Boyang. Fixed. best, Colin On Mon, Jul 13, 2020, at 08:43, Boyang Chen wrote: > Thanks for the update Colin. One nit comment to fix the RPC type > for AlterScramUsersRequest as: > "apiKey": 51, > "type": "request", > "name": "AlterScramUsersRequest", > Other than that, +1 (binding) from

[jira] [Reopened] (KAFKA-5722) Refactor ConfigCommand to use the AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reopened KAFKA-5722: -- > Refactor ConfigCommand to use the AdminClient > - > >

[jira] [Resolved] (KAFKA-5722) Refactor ConfigCommand to use the AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-5722. -- Resolution: Duplicate > Refactor ConfigCommand to use the AdminClient > ---

Jenkins build is back to normal : kafka-trunk-jdk11 #1638

See

[jira] [Resolved] (KAFKA-5722) Refactor ConfigCommand to use the AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-5722. -- Resolution: Fixed > Refactor ConfigCommand to use the AdminClient > ---

[jira] [Reopened] (KAFKA-5722) Refactor ConfigCommand to use the AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reopened KAFKA-5722: -- > Refactor ConfigCommand to use the AdminClient > - > >

Jenkins build is back to normal : kafka-trunk-jdk14 #286

See

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

See

Re: [DISCUSS] KIP-631: The Quorum-based Kafka Controller

Hey Colin, some quick questions, 1. I looked around and didn't find a config for broker heartbeat interval, are we piggy-back on some existing configs? 2. We only mentioned that the lease time is 10X of the heartbeat interval, could we also include why we chose this value? On Mon, Jul 13, 2020 at

[jira] [Created] (KAFKA-10270) Add a broker to controller channel manager to redirect AlterConfig

Boyang Chen created KAFKA-10270: --- Summary: Add a broker to controller channel manager to redirect AlterConfig Key: KAFKA-10270 URL: https://issues.apache.org/jira/browse/KAFKA-10270 Project: Kafka

Re: [DISCUSS] KIP-631: The Quorum-based Kafka Controller

Hi Colin, Thanks for the proposal. A few initial comments comments/questions below: 1. I don't follow why we need a separate configuration for `controller.listeners`. The current listener configuration already allows users to specify multiple listeners, which allows them to define internal endpoi

Re: [DISCUSS] KIP-595: A Raft Protocol for the Metadata Quorum

Hi All, Just a quick update on the proposal. We have decided to move quorum reassignment to a separate KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-642%3A+Dynamic+quorum+reassignment. The way this ties into cluster bootstrapping is complicated, so we felt we needed a bit more time fo

Re: [VOTE] KIP-554: Add Broker-side SCRAM Config API

Thanks for the update Colin. One nit comment to fix the RPC type for AlterScramUsersRequest as: "apiKey": 51, "type": "request", "name": "AlterScramUsersRequest", Other than that, +1 (binding) from me. On Mon, Jul 13, 2020 at 8:38 AM Colin McCabe wrote: > Hi David, > > The API is for clients.

Re: [VOTE] KIP-554: Add Broker-side SCRAM Config API

Hi David, The API is for clients. Brokers will still listen to ZooKeeper to load the SCRAM information. best, Colin On Mon, Jul 13, 2020, at 08:30, David Arthur wrote: > Thanks for the KIP, Colin. The new RPCs look good to me, just one question: > since we don't return the password info throu

Re: [VOTE] KIP-554: Add Broker-side SCRAM Config API

Thanks for the KIP, Colin. The new RPCs look good to me, just one question: since we don't return the password info through the RPC, how will brokers load this info? (I'm presuming that they need it to configure authentication) -David On Mon, Jul 13, 2020 at 10:57 AM Colin McCabe wrote: > On Fr

Re: [VOTE] KIP-554: Add Broker-side SCRAM Config API

On Fri, Jul 10, 2020, at 10:55, Boyang Chen wrote: > Hey Colin, thanks for the KIP. One question I have about AlterScramUsers > RPC is whether we could consolidate the deletion list and alteration list, > since in response we only have a single list of results. The further > benefit is to reduce un

[jira] [Created] (KAFKA-10269) AdminClient ListOffsetsResultInfo/timestamp is always -1

Derek Troy-West created KAFKA-10269: --- Summary: AdminClient ListOffsetsResultInfo/timestamp is always -1 Key: KAFKA-10269 URL: https://issues.apache.org/jira/browse/KAFKA-10269 Project: Kafka

Re: NotEnoughReplicasException: The size of the current ISR Set(2) is insufficient to satisfy the min.isr requirement of 3

Thanks Liam, so the phrase " current ISR set " in the warning refers to ISR set that is being shown as kafka-topics describe command ? And also, should the "maximum" value of " min.insync.replicas" be (replication factor - 1 ) - I mean min.insync.replicas should not be same as " replication factor

Re: [DISCUSS] KIP-363

Hi Magnus, Sorry for the late reply. In the specific case you mentioned of an OffsetCommitResponse with 100 partitions across 10 topics we end up with -200bytes (no error) and +200bytes (any error) in absolute terms. Precise numbers depend on topic names too, of course but I did a little test usin

Re: [VOTE] KIP-554: Add Broker-side SCRAM Config API

+1 (non-binding), thanks for the KIP. On Fri, Jul 10, 2020 at 7:02 PM Boyang Chen wrote: > Hey Colin, thanks for the KIP. One question I have about AlterScramUsers > RPC is whether we could consolidate the deletion list and alteration list, > since in response we only have a single list of resul

[jira] [Created] (KAFKA-10268) dynamic config like "--delete-config log.retention.ms" not work

zhifeng.peng created KAFKA-10268: Summary: dynamic config like "--delete-config log.retention.ms" not work Key: KAFKA-10268 URL: https://issues.apache.org/jira/browse/KAFKA-10268 Project: Kafka