[jira] [Created] (KAFKA-7004) Support configurable restore consumer poll timeout

Shawn Nguyen created KAFKA-7004: --- Summary: Support configurable restore consumer poll timeout Key: KAFKA-7004 URL: https://issues.apache.org/jira/browse/KAFKA-7004 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-7003) Add headers with error context in messages written to the Connect DeadLetterQueue topic

Arjun Satish created KAFKA-7003: --- Summary: Add headers with error context in messages written to the Connect DeadLetterQueue topic Key: KAFKA-7003 URL: https://issues.apache.org/jira/browse/KAFKA-7003

[jira] [Created] (KAFKA-7002) Allow replication factor to be set via a configuration property for the Connect DLQ topic

Arjun Satish created KAFKA-7002: --- Summary: Allow replication factor to be set via a configuration property for the Connect DLQ topic Key: KAFKA-7002 URL: https://issues.apache.org/jira/browse/KAFKA-7002

[jira] [Created] (KAFKA-7001) Rename `errors.allowed.max` in Connect to `errors.tolerance`

Arjun Satish created KAFKA-7001: --- Summary: Rename `errors.allowed.max` in Connect to `errors.tolerance` Key: KAFKA-7001 URL: https://issues.apache.org/jira/browse/KAFKA-7001 Project: Kafka

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

See Changes: [github] MINOR: Rename package `internal` to `internals` for consistency (#5137) [mjsax] [KAFKA-6730] Simplify State Store Recovery (#5013) [me] KAFKA-6981: Move the error handling configuration

Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position

I see where the 0.5 in your previous response came about. The reason I wrote 'request.timeout.ms + 15000' was that I treat this value in place of the default.block.ms According to your earlier description: bq. request.timeout.ms controls something different: the amount of time we're willing to

Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position

On Tue, Jun 5, 2018, at 16:35, Ted Yu wrote: > bq. could probably come up with a good default > > That's the difficult part. > > bq. max(1000, 0.5 * request.timeout.ms) > > Looking at some existing samples: > In tests/kafkatest/tests/connect/templates/connect-distributed.properties , > we have:

Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position

bq. could probably come up with a good default That's the difficult part. bq. max(1000, 0.5 * request.timeout.ms) Looking at some existing samples: In tests/kafkatest/tests/connect/templates/connect-distributed.properties , we have: request.timeout.ms=3 Isn't the above formula putting an

Re: Someone to review KAFKA-6919, one line change for faulty documentation

Thanks, Koen. I was on vacation, so I missed this originally. But I'll review it now. cheers, Colin On Fri, Jun 1, 2018, at 13:02, Koen De Groote wrote: > Greetings, > > Poking for someone to have a quick look at this, It's a one-line change. I > noticed the documentation about trogdor was

[jira] [Resolved] (KAFKA-6997) Kafka run class doesn't exclude test-sources jar

[ https://issues.apache.org/jira/browse/KAFKA-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-6997. -- Resolution: Fixed Issue resolved by pull request 5139

Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position

I don't think it can be fixed. The RPC duration is something that you might reasonably want to tune. For example, if it's too low, you might not be able to make progress at all on a heavily loaded server. We could probably come up with a good default, however. rpc.timeout.ms could be set to

Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position

bq. we must make the API timeout longer than the RPC timeout I agree with the above. How about adding a fixed duration on top of request.timeout.ms ? Thanks On Tue, Jun 5, 2018 at 4:18 PM, Colin McCabe wrote: > As Jason noted earlier, request.timeout.ms controls something different: > the

Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position

As Jason noted earlier, request.timeout.ms controls something different: the amount of time we're willing to wait for an RPC to complete. Empirically, RPCs sometimes hang for a long time. If the API timeout is the same as the RPC timeout, we are not robust against this failure condition. The

[jira] [Created] (KAFKA-7000) KafkaConsumer.position should wait for assignment metadata

John Roesler created KAFKA-7000: --- Summary: KafkaConsumer.position should wait for assignment metadata Key: KAFKA-7000 URL: https://issues.apache.org/jira/browse/KAFKA-7000 Project: Kafka Issue

[jira] [Created] (KAFKA-6999) Document read-write lock usage of caching enabled stores

Matthias J. Sax created KAFKA-6999: -- Summary: Document read-write lock usage of caching enabled stores Key: KAFKA-6999 URL: https://issues.apache.org/jira/browse/KAFKA-6999 Project: Kafka

[jira] [Created] (KAFKA-6998) Remove caching wrapper stores if cache-size is configured to zero bytes

Matthias J. Sax created KAFKA-6998: -- Summary: Remove caching wrapper stores if cache-size is configured to zero bytes Key: KAFKA-6998 URL: https://issues.apache.org/jira/browse/KAFKA-6998 Project:

Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position

bq. we were already doing with request.timeout.ms I would vote for using existing config. Any new config parameter needs to go thru long process of digestion: documentation, etc in order for users to understand and familiarize. The existing config would have lower mismatch of impedance. Cheers

Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position

Thanks for the comments. I'm not sure I understand why we want to avoid the term "timeout." Semantically, that's what it is. If we don't want another timeout config, we could avoid it and hard-code a reasonable default or try to wrap the behavior into one of the other timeouts (which is sort of

Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position

I agree that using `default.timeout.ms` could cause confusion since we already have other timeout configurations in the consumer. +1 for using `default.block.ms`. Thanks, Dhruvil On Tue, Jun 5, 2018 at 11:48 AM, Bill Bejeck wrote: > Hi Jason, > > At first, I thought the same name between the

[jira] [Resolved] (KAFKA-6981) Missing Connector Config (errors.deadletterqueue.topic.name) kills Connect Clusters

[ https://issues.apache.org/jira/browse/KAFKA-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-6981. -- Resolution: Fixed Issue resolved by pull request 5125

Build failed in Jenkins: kafka-1.1-jdk7 #140

See Changes: [matthias] MINOR: Add missing configs for resilience settings -- [...truncated 419.30 KB...] kafka.admin.ResetConsumerGroupOffsetTest >

[jira] [Resolved] (KAFKA-6730) Simplify state store recovery

[ https://issues.apache.org/jira/browse/KAFKA-6730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6730. Resolution: Fixed > Simplify state store recovery > - > >

[jira] [Created] (KAFKA-6997) Kafka run class doesn't exclude test-sources jar

Magesh kumar Nandakumar created KAFKA-6997: -- Summary: Kafka run class doesn't exclude test-sources jar Key: KAFKA-6997 URL: https://issues.apache.org/jira/browse/KAFKA-6997 Project: Kafka

Discount code for kafka summit SF 2018

Hi folks, Was wondering if this list has a discount code for kafka summit -San francisco 2018. I know there was one last year, so just wanted to check! Thanks! aarti

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

See

Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position

Hi Jason, At first, I thought the same name between the producer and the consumer was ideal. But your comment makes me realize consistent names with different semantics is even more confusing. I'm +1 for not using `max.block.ms`. I like Guozhang's suggestion of ` default.block.ms` for the

Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position

Hi Jason, Yeah I agree that "max.block.ms" makes people thinking of the producer's config with the same name, but their semantics are different. On the other hand, I'm a bit concerned with the reusing of the term `timeout` as we already have `session.timeout.ms` and `request.timeout.ms` in

Re: I'd like permission to create a KIP

Hello Richard, Done, cheers. Guozhang On Tue, Jun 5, 2018 at 10:09 AM, Richard Tjerngren wrote: > my username on the wiki is richodemus > > thanks > -- -- Guozhang

Re: How to initiate a KIP?

Hello Virgil, I have granted you the permission, if you refresh your browser you should see the link now. Guozhang On Tue, Jun 5, 2018 at 1:54 AM, Virgil Palanciuc wrote: > Hi all, > > Here >

I'd like permission to create a KIP

my username on the wiki is richodemus thanks

Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position

Hey All, One more minor follow-up. As I was reviewing the change mentioned above, I felt the name `max.block.ms` was a little bit misleading since it only applies to methods which do not have an explicit timeout. A clearer name given its usage might be `default.timeout.ms`. It is the default

[jira] [Resolved] (KAFKA-6996) ConsumerGroupCommand.scala uses deprecated components

[ https://issues.apache.org/jira/browse/KAFKA-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6996. Resolution: Duplicate Duplicate of KAFKA-6884, > ConsumerGroupCommand.scala uses deprecated

KIP-176 and related PR : today deadline for merging in 2.0.0

Hi, because today, as far as I understood, should be the deadline for having the PRs related to KIPs merged for the 2.0.0, maybe any committers can take a look (review and maybe merge) the PR : https://github.com/apache/kafka/pull/5097 related to the KIP-176 :

[jira] [Created] (KAFKA-6996) ConsumerGroupCommand.scala uses deprecated components

Zeynep Arikoglu created KAFKA-6996: -- Summary: ConsumerGroupCommand.scala uses deprecated components Key: KAFKA-6996 URL: https://issues.apache.org/jira/browse/KAFKA-6996 Project: Kafka

[jira] [Created] (KAFKA-6995) Make config "internal.leave.group.on.close" public

Boyang Chen created KAFKA-6995: -- Summary: Make config "internal.leave.group.on.close" public Key: KAFKA-6995 URL: https://issues.apache.org/jira/browse/KAFKA-6995 Project: Kafka Issue Type:

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

See Changes: [ismael] KAFKA-3665: Enable TLS hostname verification by default (KIP-294) -- [...truncated 2.56 MB...]

[jira] [Resolved] (KAFKA-6982) java.lang.ArithmeticException: / by zero

[ https://issues.apache.org/jira/browse/KAFKA-6982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6982. -- Resolution: Fixed Fix Version/s: 2.0.0 > java.lang.ArithmeticException: / by zero >

[jira] [Resolved] (KAFKA-6972) Kafka ACL does not work expected with wildcard

[ https://issues.apache.org/jira/browse/KAFKA-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6972. -- Resolution: Information Provided > Kafka ACL does not work expected with wildcard >

[jira] [Resolved] (KAFKA-5523) ReplayLogProducer not using the new Kafka consumer

[ https://issues.apache.org/jira/browse/KAFKA-5523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5523. -- Resolution: Fixed Assignee: Manikumar Fix Version/s: 2.0.0 > ReplayLogProducer not

[jira] [Resolved] (KAFKA-5940) kafka-delete-records.sh doesn't give any feedback when the JSON offset configuration file is invalid

[ https://issues.apache.org/jira/browse/KAFKA-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5940. -- Resolution: Fixed Fixed in KAFKA-5919 > kafka-delete-records.sh doesn't give any feedback when the

[jira] [Created] (KAFKA-6994) KafkaConsumer.poll throwing AuthorizationException timeout-dependent

Edoardo Comar created KAFKA-6994: Summary: KafkaConsumer.poll throwing AuthorizationException timeout-dependent Key: KAFKA-6994 URL: https://issues.apache.org/jira/browse/KAFKA-6994 Project: Kafka

How to initiate a KIP?

Hi all, Here it says that “anyone can initiate a KIP”, however the “Create KIP” link doesn’t work for me. How can I get the permissions to initiate one? (or if I

[jira] [Created] (KAFKA-6993) Defective documentations for KStream/KTable methods

Lee Dongjin created KAFKA-6993: -- Summary: Defective documentations for KStream/KTable methods Key: KAFKA-6993 URL: https://issues.apache.org/jira/browse/KAFKA-6993 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-6762) log-cleaner thread terminates due to java.lang.IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6762. Resolution: Duplicate Duplicate of KAFKA-6854. > log-cleaner thread terminates due to

[jira] [Created] (KAFKA-6992) Configuring the batch.size to zero won't disable the batching entirely

Chia-Ping Tsai created KAFKA-6992: - Summary: Configuring the batch.size to zero won't disable the batching entirely Key: KAFKA-6992 URL: https://issues.apache.org/jira/browse/KAFKA-6992 Project: