Re: Kafka replication throttling on broker level

Hi, My Jira Id is rahul.mnit Please add me to the contributors list. Thanks, Rahul On Sat, Apr 6, 2019 at 2:58 AM Jun Rao wrote: > Hi, Rahul, > > If the ticket is unassigned, feel free to assign it to yourself. If you > can't do that, let us know your jira id and we can add you to the >

[DISCUSS] KIP-450: Sliding Window Aggregations in the DSL

Hello all, I would like to kick off discussion of this KIP aimed at providing sliding window semantics to DSL aggregations. https://cwiki.apache.org/confluence/display/KAFKA/KIP-450%3A+Sliding+Window+Aggregations+in+the+DSL Please take a look and share any thoughts you have regarding the API,

Re: [DISCUSS] KIP-435: Incremental Partition Reassignment

Hi Jason / Viktor, For the URP during a reassignment,  if the "original_replicas" is kept for the current pending reassignment. I think it will be very easy to compare that with the topic/partition's ISR.  If all "original_replicas" are in ISR, then URP should be 0 for that topic/partition. 

Re: [DISCUSS] KIP-236 Interruptible Partition Reassignment

Hi Jun, Thanks for the feedback!  for 40,  I agree.  It makes sense to do it via RPC request to the controller.  Maybe for KIP-236,  I will just implement RPC for reassignment cancellation only?  otherwise if KIP-236 includes other previous Reassignment related operations such as Submitting

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

See

Re: [DISCUSS] KIP-435: Incremental Partition Reassignment

Hi Viktor, Thanks for writing this up. As far as questions about overlap with KIP-236, I agree it seems mostly orthogonal. I think KIP-236 may have had a larger initial scope, but now it focuses on cancellation and batching is left for future work. With that said, I think we may not actually

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

See Changes: [github] KAFKA-8190; Don't update keystore modification time during validation [github] MINOR: Tighten up metadata upgrade test (#6531) [jason] KAFKA-7893; Refactor ConsumerBounceTest to reuse

Build failed in Jenkins: kafka-2.2-jdk8 #76

See Changes: [rajinisivaram] KAFKA-8190; Don't update keystore modification time during validation -- [...truncated 2.73 MB...] kafka.coordinator.group.GroupCoordinatorTest

Build failed in Jenkins: kafka-2.1-jdk8 #157

See Changes: [rajinisivaram] KAFKA-8190; Don't update keystore modification time during validation -- [...truncated 918.78 KB...] kafka.server.KafkaConfigTest >

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

See

[jira] [Resolved] (KAFKA-8168) Add a generated ApiMessageType class

[ https://issues.apache.org/jira/browse/KAFKA-8168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-8168. - Resolution: Fixed Reviewer: Gwen Shapira Fix Version/s: 2.3.0 > Add a generated

Re: [DISCUSSION] KIP-422: Add support for user/client configuration in the Kafka Admin Client

Hi, Yaodong, Yes, what you proposed makes sense. A couple of more comments. 21. Could you add those examples to the KIP wiki? It would also be useful to know how to set the ConfigEntry value for quotas at DefaultClientInUser, DefaultClientDefaultUser and DefaultUser level. 22. To support

Re: [DISCUSS] KIP-448: Add State Stores Unit Test Support to Kafka Streams Test Utils

Hi, bumping this up again. Thanks! On Tue, Apr 2, 2019, 13:07 Yishun Guan wrote: > Hi All, > > I like to start a discussion on KIP-448 > (https://cwiki.apache.org/confluence/x/SAeZBg). It is about adding > Mock state stores and relevant components for testing purposes. > > Here is the JIRA:

Re: Kafka replication throttling on broker level

Hi, Rahul, If the ticket is unassigned, feel free to assign it to yourself. If you can't do that, let us know your jira id and we can add you to the contributors list. Thanks, Jun On Fri, Apr 5, 2019 at 11:45 AM Rahul Agarwal (Flipkart Data Group) wrote: > Hi, > > We actually need this

Re: [DISCUSSION] KIP-422: Add support for user/client configuration in the Kafka Admin Client

Hi Jun, The proposal we have right now is to directly set the quota through existing admin client APIs. See following examples: Example 1: set a user quota AdminClient adminClient = mock(AdminClient.class); Map configs = new HashMap(); Config config = new Config(Arrays.asList(new

[jira] [Created] (KAFKA-8198) KStreams testing docs use non-existent method "pipe"

Michael Drogalis created KAFKA-8198: --- Summary: KStreams testing docs use non-existent method "pipe" Key: KAFKA-8198 URL: https://issues.apache.org/jira/browse/KAFKA-8198 Project: Kafka

[jira] [Resolved] (KAFKA-7893) Refactor ConsumerBounceTest.scala

[ https://issues.apache.org/jira/browse/KAFKA-7893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7893. Resolution: Fixed > Refactor ConsumerBounceTest.scala > -

[jira] [Created] (KAFKA-8197) Flaky Test kafka.server.DynamicBrokerConfigTest > testPasswordConfigEncoderSecretChange

Guozhang Wang created KAFKA-8197: Summary: Flaky Test kafka.server.DynamicBrokerConfigTest > testPasswordConfigEncoderSecretChange Key: KAFKA-8197 URL: https://issues.apache.org/jira/browse/KAFKA-8197

[jira] [Resolved] (KAFKA-8190) Keystore update without file change doesn't update SSLContext

[ https://issues.apache.org/jira/browse/KAFKA-8190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-8190. --- Resolution: Fixed Reviewer: Manikumar Fix Version/s: 2.3.0 > Keystore update

Re: Kafka replication throttling on broker level

Hi, We actually need this feature for our system. This ticket is currently unassigned. Can this ticket be assigned to me? I will send a pull request for the feature. Thanks, Rahul On Fri, Apr 5, 2019 at 9:59 PM Jun Rao wrote: > Hi, Rahul, > > Those 2 configs are not supported at the broker

Re: Request to add to contributor list

Hi, Thanks you for your interest. Just added you to the contributors list. Thanks,

Request to add to contributor list

Hello team, I would love to contribute to the open source Kafka tool. So, please add me to the contributors list. My Apache Jira Id is : ArunJijo Regards, Arun JIjo

[jira] [Created] (KAFKA-8196) Replace InitProducerId request/response with automated protocol

Mickael Maison created KAFKA-8196: - Summary: Replace InitProducerId request/response with automated protocol Key: KAFKA-8196 URL: https://issues.apache.org/jira/browse/KAFKA-8196 Project: Kafka

[jira] [Created] (KAFKA-8195) Unstable Producer After Send Failure in Transaction

Gary Russell created KAFKA-8195: --- Summary: Unstable Producer After Send Failure in Transaction Key: KAFKA-8195 URL: https://issues.apache.org/jira/browse/KAFKA-8195 Project: Kafka Issue Type:

Re: Kafka replication throttling on broker level

Hi, Rahul, Those 2 configs are not supported at the broker level right now. This is being tracked at https://issues.apache.org/jira/browse/KAFKA-7983. Thanks, Jun On Fri, Apr 5, 2019 at 9:17 AM Rahul Agarwal (Flipkart Data Group) wrote: > Hi, > > We are using Kafka 1.0.2 and wanted to rate

Kafka replication throttling on broker level

Hi, We are using Kafka 1.0.2 and wanted to rate limit when a broker is replaced and it syncs up with other brokers in the cluster. I followed the below doc for the same: https://kafka.apache.org/10/documentation.html#rep-throttle According to this document, leader.replication.throttled.rate,

[VOTE] KIP-411: Make default Kafka Connect worker task client IDs distinct

Hi all, Since we seem to have agreement in the discussion I would like to start the vote on KIP-411. See: https://cwiki.apache.org/confluence/display/KAFKA/KIP-411%3A+Make+default+Kafka+Connect+worker+task+client+IDs+distinct Also see the related PR: https://github.com/apache/kafka/pull/6097

[jira] [Created] (KAFKA-8194) MessagesInPerSec incorrect value when Stream produce messages

Odyldzhon Toshbekov created KAFKA-8194: -- Summary: MessagesInPerSec incorrect value when Stream produce messages Key: KAFKA-8194 URL: https://issues.apache.org/jira/browse/KAFKA-8194 Project:

Kafka replication throttling on broker level

Hi, We are using Kafka 1.0.2 and wanted to rate limit when a broker is replaced and it syncs up with other brokers in the cluster. I followed the below doc for the same: https://kafka.apache.org/10/documentation.html#rep-throttle According to this document, leader.replication.throttled.rate,

Re: [DISCUSS] KIP-252: Extend ACLs to allow filtering based on ip ranges and subnets

On Thu, Apr 4, 2019, at 01:52, Sönke Liebau wrote: > Hi Colin, > > I agree, we need to have a way of failing incorrect ranges server-side, > I'll amend the KIP and look into that. I think INVALID_REQUEST should fit > fine, afaik we can send a message along with that code, so that could > explain