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

See Changes: [me] KAFKA-3627: consumer fails to execute delayed tasks in poll when records -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubunt

Re: Get topic level detail from new consumer group command

you need to run describe topic command to get the topic details: ./kafka-topics.sh --zookeeper ":2181" --describe --topic From: ravi singh To: us...@kafka.apache.org; dev@kafka.apache.org Sent: Friday, 6 May 2016 1:07 AM Subject: Get topic level detail from new consumer group command

KAFKA-3112

Hi All, Does anyone know if KAFKA-3112 is merged to 0.9.0.1? Is there a place to check which version has this fix? Jira doesn’t show fix versions. https://issues.apache.org/jira/browse/KAFKA-3112 Thanks, Raj Tanneru Information contained in this e-mail message is confidential. This e-mail mes

[jira] [Commented] (KAFKA-3627) New consumer doesn't run delayed tasks while under load

[ https://issues.apache.org/jira/browse/KAFKA-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273645#comment-15273645 ] ASF GitHub Bot commented on KAFKA-3627: --- Github user asfgit closed the pull request

[jira] [Resolved] (KAFKA-3627) New consumer doesn't run delayed tasks while under load

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

[GitHub] kafka pull request: KAFKA-3627: consumer fails to execute delayed ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1295 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273626#comment-15273626 ] Manas Alekar commented on KAFKA-3587: - [~junrao] That will create the same pairs in c

[jira] [Assigned] (KAFKA-3487) Support per-connector/per-task classloaders in Connect

[ https://issues.apache.org/jira/browse/KAFKA-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei reassigned KAFKA-3487: - Assignee: Liquan Pei (was: Ewen Cheslack-Postava) > Support per-connector/per-task classloaders

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273606#comment-15273606 ] Jun Rao commented on KAFKA-3587: [~alekar], I think [~ecomar] is suggesting a potentially

[jira] [Created] (KAFKA-3664) When subscription set changes on new consumer, the partitions may be removed without offset being committed.

Jiangjie Qin created KAFKA-3664: --- Summary: When subscription set changes on new consumer, the partitions may be removed without offset being committed. Key: KAFKA-3664 URL: https://issues.apache.org/jira/browse/KAFK

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273592#comment-15273592 ] ASF GitHub Bot commented on KAFKA-3587: --- Github user Ishiihara closed the pull reque

[GitHub] kafka pull request: KAFKA-3587: Fix fake large log segment in log ...

Github user Ishiihara closed the pull request at: https://github.com/apache/kafka/pull/1328 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is e

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273584#comment-15273584 ] Liquan Pei commented on KAFKA-3587: --- [~ecomar] [~alekar] Moving the pessimistic check to

Build failed in Jenkins: kafka-trunk-jdk7 #1256

See Changes: [wangguoz] HOTFIX: follow-up on KAFKA-725 to remove the check and return empty -- [...truncated 6383 lines...] org.apache.kafka.connect.storage.KafkaStatusBackingStoreTest > readC

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273482#comment-15273482 ] Edoardo Comar commented on KAFKA-3587: -- [~ishiihara] In your PR the very pessimistic

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273481#comment-15273481 ] Manas Alekar commented on KAFKA-3587: - 1. I believe this should happen when any scratc

[jira] [Commented] (KAFKA-3656) Avoid stressing system more when already under stress

[ https://issues.apache.org/jira/browse/KAFKA-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273477#comment-15273477 ] Gwen Shapira commented on KAFKA-3656: - The fix is pretty trivial (remove a log line).

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273466#comment-15273466 ] Manas Alekar commented on KAFKA-3587: - [~ecomar] I used 1/2 because the worst case fo

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

See Changes: [wangguoz] HOTFIX: follow-up on KAFKA-725 to remove the check and return empty -- [...truncated 6424 lines...] org.apache.kafka.connect.storage.KafkaOffsetBackingStoreTest > testRe

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273457#comment-15273457 ] Jun Rao commented on KAFKA-3587: [~alekar] and [~liquanpei], thanks for both your patches.

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273455#comment-15273455 ] Edoardo Comar commented on KAFKA-3587: -- [~alekar] I had a look at your patch. The app

[jira] [Commented] (KAFKA-3656) Avoid stressing system more when already under stress

[ https://issues.apache.org/jira/browse/KAFKA-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273436#comment-15273436 ] John Ky commented on KAFKA-3656: I spent a day writing reflection to work around this issu

Build failed in Jenkins: kafka-trunk-jdk7 #1255

See Changes: [ismael] KAFKA-3661; fix NPE in o.a.k.c.c.RoundRobinAssignor when topic metadata [ismael] KAFKA-3651; Remove the condition variable waiting on memory availability -- [...truncated

Re: list of challenges encountered using 0.9.0.1

Hey Cliff, Thanks for the feedback. A few select comments: 1. The new Java KafkaConsumer doesn’t have a method to return the high >watermark (last offset in the topic/partition's log. This is currently exposed in fetch responses, so we could add it to the ConsumerRecords object. In general

Build failed in Jenkins: kafka-0.10.0-jdk7 #57

See Changes: [wangguoz] HOTFIX: follow-up on KAFKA-725 to remove the check and return empty -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubun

Re: Reg: Kafka-Acls

Try the following /bin/kafka-acls.sh --topic permissiontopic --allow-host {host} --allow-principal User:dev --producer --add --authorizer-properties zookeeper.connect={host:port} Thanks Parth On Thu, May 5, 2016 at 4:26 PM, BigData dev wrote: > Hi, > Thanks for Info. > It worked. > Acls are co

[jira] [Assigned] (KAFKA-2720) Periodic purging groups in the coordinator

[ https://issues.apache.org/jira/browse/KAFKA-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-2720: -- Assignee: Jason Gustafson (was: Guozhang Wang) > Periodic purging groups in the coordi

[jira] [Commented] (KAFKA-725) Broker Exception: Attempt to read with a maximum offset less than start offset

[ https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273337#comment-15273337 ] ASF GitHub Bot commented on KAFKA-725: -- Github user asfgit closed the pull request at:

[GitHub] kafka pull request: HOTFIX: follow-up on KAFKA-725 to remove the c...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1327 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273325#comment-15273325 ] Manas Alekar commented on KAFKA-3587: - It was easier to explain a fix in code than in

Build failed in Jenkins: kafka-0.10.0-jdk7 #56

See Changes: [ismael] KAFKA-3661; fix NPE in o.a.k.c.c.RoundRobinAssignor when topic metadata [ismael] KAFKA-3651; Remove the condition variable waiting on memory availability -- Started by an

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

See Changes: [ismael] KAFKA-3661; fix NPE in o.a.k.c.c.RoundRobinAssignor when topic metadata [ismael] KAFKA-3651; Remove the condition variable waiting on memory availability -- Started by an

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273313#comment-15273313 ] Gwen Shapira commented on KAFKA-3587: - [~alekar] Thanks for the patch! In general, Apa

Re: Reg: Kafka-Acls

Hi, Thanks for Info. It worked. Acls are correctly set, but when i run the producer is throwing error, even if acl's are correctlt set. bin/kafka-console-producer.sh --broker-list bdavm1222.svl.ibm.com:6667 --topic permissiontopic --producer.config producer.properties jj [2016-05-05 16:02:23,308]

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273305#comment-15273305 ] Liquan Pei commented on KAFKA-3587: --- Hi [~ecomar] I have a WIP PR, mind to take a look?

Re: Reg: Kafka-Acls

Acls will be written in zookeeper but you are using getAcl , what you need is get /kafka-acl/Topic/permissiontopic Thanks Parth On Thu, May 5, 2016 at 3:28 PM, BigData dev wrote: > Hi, > When I run the command > /bin/kafka-acls.sh --topic permissiontopic --add --allow-host {host} > --allow-p

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273293#comment-15273293 ] Manas Alekar commented on KAFKA-3587: - I have attached a patch which explains one feas

Build failed in Jenkins: kafka-0.10.0-jdk7 #55

See Changes: [wangguoz] HOTFIX: Reverted timeouts to larger values -- [...truncated 6377 lines...] org.apache.kafka.connect.storage.KafkaStatusBackingStoreTest > readConnectorState PASSED org.

[jira] [Updated] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manas Alekar updated KAFKA-3587: Attachment: 0001-POC-improving-deduping-segments.patch > LogCleaner fails due to incorrect offset ma

[jira] [Assigned] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-3144: -- Assignee: Vahid Hashemian (was: Konrad Kalita) > report members with no assigned parti

[jira] [Commented] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273277#comment-15273277 ] Ismael Juma commented on KAFKA-3144: [~vahid], please go ahead. > report members with

[jira] [Commented] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273275#comment-15273275 ] Vahid Hashemian commented on KAFKA-3144: [~ijuma] [~gwenshap] [~granthenke] I have

[jira] [Commented] (KAFKA-3651) Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" exception, it should also remove the condition object from the wait

[ https://issues.apache.org/jira/browse/KAFKA-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273264#comment-15273264 ] ASF GitHub Bot commented on KAFKA-3651: --- Github user asfgit closed the pull request

[jira] [Resolved] (KAFKA-3651) Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" exception, it should also remove the condition object from the waite

[ https://issues.apache.org/jira/browse/KAFKA-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3651. Resolution: Fixed Issue resolved by pull request 1314 [https://github.com/apache/kafka/pull/1314] >

[GitHub] kafka pull request: KAFKA-3651 : Remove the condition variable wai...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1314 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[GitHub] kafka pull request: WIP: Fix fake large log segment in log cleaner

GitHub user Ishiihara opened a pull request: https://github.com/apache/kafka/pull/1328 WIP: Fix fake large log segment in log cleaner You can merge this pull request into a Git repository by running: $ git pull https://github.com/Ishiihara/kafka kafka-3587 Alternatively you c

Reg: Kafka-Acls

Hi, When I run the command /bin/kafka-acls.sh --topic permissiontopic --add --allow-host {host} --allow-principal User:dev --operation Write --authorizer-properties zookeeper.connect={host:port} I am getting output as acls are set. But when i check under zookeeper using below command, it is not

[jira] [Commented] (KAFKA-3661) org.apache.kafka.clients.consumer.RoundRobinAssignor throws NPE when topic metadata not found

[ https://issues.apache.org/jira/browse/KAFKA-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273226#comment-15273226 ] ASF GitHub Bot commented on KAFKA-3661: --- Github user asfgit closed the pull request

[jira] [Resolved] (KAFKA-3661) org.apache.kafka.clients.consumer.RoundRobinAssignor throws NPE when topic metadata not found

[ https://issues.apache.org/jira/browse/KAFKA-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3661. Resolution: Fixed Fix Version/s: 0.10.0.0 Issue resolved by pull request 1326 [https://github

[GitHub] kafka pull request: KAFKA-3661: fix NPE in o.a.k.c.c.RoundRobinAss...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1326 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-3525) max.reserved.broker.id off-by-one error

[ https://issues.apache.org/jira/browse/KAFKA-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273215#comment-15273215 ] Flavio Junqueira commented on KAFKA-3525: - Got it, thank you both for the clarific

[jira] [Commented] (KAFKA-3627) New consumer doesn't run delayed tasks while under load

[ https://issues.apache.org/jira/browse/KAFKA-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273186#comment-15273186 ] Jason Gustafson commented on KAFKA-3627: [~davispw] Yes, you are right. No heartbe

Re: Get topic level detail from new consumer group command

I think you're asking for only the details of a particular topic? Could you just grep the output or are you concerned about the overhead because you have tons of topics? -Jason On Thu, May 5, 2016 at 12:37 PM, ravi singh wrote: > ./bin/kafka-consumer-groups.sh --group batchprocessord_zero > -

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

See Changes: [me] KAFKA-3581: add timeouts to joins in background thread services [wangguoz] HOTFIX: Reverted timeouts to larger values -- Started by an SCM change [EnvInject] - Loading node env

Build failed in Jenkins: kafka-0.10.0-jdk7 #54

See Changes: [me] KAFKA-3581: add timeouts to joins in background thread services -- [...truncated 8731 lines...] org.apache.kafka.connect.storage.KafkaStatusBackingStoreTest > readConnectorSta

Build failed in Jenkins: kafka-trunk-jdk7 #1254

See Changes: [me] KAFKA-3581: add timeouts to joins in background thread services [wangguoz] HOTFIX: Reverted timeouts to larger values -- Started by an SCM change [EnvInject] - Loading node en

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

See Changes: [me] KAFKA-3659: Handle coordinator disconnects more gracefully in client -- [...truncated 6458 lines...] org.apache.kafka.connect.runtime.WorkerSourceTaskTest > testCommitFailure P

Re: Mapping topic partition owner id to group member id?

I forgot to mention that my question is in the context of the old consumer. Regards, --Vahid Hashemian From: Vahid S Hashemian/Silicon Valley/IBM@IBMUS To: dev@kafka.apache.org Date: 05/05/2016 01:55 PM Subject:Mapping topic partition owner id to group member id? Hi, The

Jenkins build is back to normal : kafka-trunk-jdk7 #1253

See

Mapping topic partition owner id to group member id?

Hi, The consumer group command directly uses ZooKeeper (through zkUtils) to return information about a consumer group. Inside a /consumers/[group]/ structure member ids exist under ids/ and owner information for each topic partition is under owners/[topic]/[partition]/. An example member id is

[GitHub] kafka pull request: HOTFIX: Reverted timeouts to larger values

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1324 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[VOTE] 0.10.0.0 RC3

Hello Kafka users, developers and client-developers, This is the fourth candidate for release of Apache Kafka 0.10.0.0. This is a major release that includes: (1) New message format including timestamps (2) client interceptor API (3) Kafka Streams. Since this is a major release, we will give peop

Jenkins build is back to normal : kafka-0.10.0-jdk7 #53

See

[jira] [Created] (KAFKA-3663) Proposal for a kafka broker command - kafka-brokers.sh

Jayesh Thakrar created KAFKA-3663: - Summary: Proposal for a kafka broker command - kafka-brokers.sh Key: KAFKA-3663 URL: https://issues.apache.org/jira/browse/KAFKA-3663 Project: Kafka Issue

[jira] [Commented] (KAFKA-3581) Use timeout when joining threads in system test services

[ https://issues.apache.org/jira/browse/KAFKA-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272983#comment-15272983 ] ASF GitHub Bot commented on KAFKA-3581: --- Github user asfgit closed the pull request

[GitHub] kafka pull request: KAFKA-3581: add timeouts to joins in backgroun...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1297 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Resolved] (KAFKA-3581) Use timeout when joining threads in system test services

[ https://issues.apache.org/jira/browse/KAFKA-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3581. -- Resolution: Fixed Fix Version/s: 0.10.0.0 0.10.1.0 Iss

[jira] [Commented] (KAFKA-725) Broker Exception: Attempt to read with a maximum offset less than start offset

[ https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272948#comment-15272948 ] Stig Rohde Døssing commented on KAFKA-725: -- Thanks for fixing this. The scenario J

Get topic level detail from new consumer group command

./bin/kafka-consumer-groups.sh --group batchprocessord_zero --bootstrap-server kafka-1-evilcorp.com:9092 --new-consumer --describe Running the above ConsumerGroupcommad will describe consumer for all the topics it's listening to. Is there any workaround to get *only topic level detail*? ​ -- *

[jira] [Created] (KAFKA-3662) Failure in kafka.network.SocketServerTest.tooBigRequestIsRejecte

Guozhang Wang created KAFKA-3662: Summary: Failure in kafka.network.SocketServerTest.tooBigRequestIsRejecte Key: KAFKA-3662 URL: https://issues.apache.org/jira/browse/KAFKA-3662 Project: Kafka

[jira] [Commented] (KAFKA-3659) Consumer does not handle coordinator connection blackout period gracefully

[ https://issues.apache.org/jira/browse/KAFKA-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272870#comment-15272870 ] ASF GitHub Bot commented on KAFKA-3659: --- Github user asfgit closed the pull request

[jira] [Commented] (KAFKA-725) Broker Exception: Attempt to read with a maximum offset less than start offset

[ https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272872#comment-15272872 ] ASF GitHub Bot commented on KAFKA-725: -- GitHub user guozhangwang opened a pull request

[jira] [Resolved] (KAFKA-3659) Consumer does not handle coordinator connection blackout period gracefully

[ https://issues.apache.org/jira/browse/KAFKA-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3659. -- Resolution: Fixed Fix Version/s: 0.10.0.0 0.10.1.0 Iss

[GitHub] kafka pull request: KAFKA-3659: Handle coordinator disconnects mor...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1322 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[GitHub] kafka pull request: HOTFIX: follow-up on KAFKA-725 to remove the c...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1327 HOTFIX: follow-up on KAFKA-725 to remove the check and return empty response instead of throw exceptions You can merge this pull request into a Git repository by running: $ git pull http

[jira] [Commented] (KAFKA-3661) org.apache.kafka.clients.consumer.RoundRobinAssignor throws NPE when topic metadata not found

[ https://issues.apache.org/jira/browse/KAFKA-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272768#comment-15272768 ] ASF GitHub Bot commented on KAFKA-3661: --- GitHub user onurkaraman opened a pull reque

[GitHub] kafka pull request: KAFKA-3661: fix NPE in o.a.k.c.c.RoundRobinAss...

GitHub user onurkaraman opened a pull request: https://github.com/apache/kafka/pull/1326 KAFKA-3661: fix NPE in o.a.k.c.c.RoundRobinAssignor when topic metadata not found AbstractPartitionAssignor.assign has an ambiguous line in its documentation: > @param partitionsPerTopic The

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272750#comment-15272750 ] Jun Rao commented on KAFKA-3565: [~becket_qin], thanks for the latest consumer results. Ye

[jira] [Created] (KAFKA-3661) org.apache.kafka.clients.consumer.RoundRobinAssignor throws NPE when topic metadata not found

Onur Karaman created KAFKA-3661: --- Summary: org.apache.kafka.clients.consumer.RoundRobinAssignor throws NPE when topic metadata not found Key: KAFKA-3661 URL: https://issues.apache.org/jira/browse/KAFKA-3661

[jira] [Updated] (KAFKA-725) Broker Exception: Attempt to read with a maximum offset less than start offset

[ https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-725: -- Priority: Blocker (was: Major) > Broker Exception: Attempt to read with a maximum offset less than start offset

[jira] [Commented] (KAFKA-3525) max.reserved.broker.id off-by-one error

[ https://issues.apache.org/jira/browse/KAFKA-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272696#comment-15272696 ] Sriharsha Chintalapani commented on KAFKA-3525: --- [~fpj] reservered.broker.ma

[jira] [Commented] (KAFKA-3173) Error while moving some partitions to OnlinePartition state

[ https://issues.apache.org/jira/browse/KAFKA-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272603#comment-15272603 ] Jun Rao commented on KAFKA-3173: [~fpj], yes, I agree that the lock there is confusing. Mo

[jira] [Assigned] (KAFKA-3443) Support regex topics in addSource() and stream()

[ https://issues.apache.org/jira/browse/KAFKA-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck reassigned KAFKA-3443: -- Assignee: Bill Bejeck > Support regex topics in addSource() and stream() >

[jira] [Commented] (KAFKA-3330) Truncate log cleaner offset checkpoint if the log is truncated

[ https://issues.apache.org/jira/browse/KAFKA-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272621#comment-15272621 ] Jun Rao commented on KAFKA-3330: If you see the issue now, the simplest thing is to remove

[jira] [Updated] (KAFKA-3658) Incorrect validation check on maintenance period with join window size

[ https://issues.apache.org/jira/browse/KAFKA-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3658: - Description: As [~h...@pinterest.com] found out, the current validation check of {{KStreamJoinWin

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272619#comment-15272619 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] I ran the tests again with more data

[jira] [Commented] (KAFKA-3627) New consumer doesn't run delayed tasks while under load

[ https://issues.apache.org/jira/browse/KAFKA-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272615#comment-15272615 ] Peter Davis commented on KAFKA-3627: I believe this problem is aggravated by max.poll.

[jira] [Updated] (KAFKA-3658) Incorrect validation check on maintenance period with join window size

[ https://issues.apache.org/jira/browse/KAFKA-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3658: - Summary: Incorrect validation check on maintenance period with join window size (was: RocksDBWind

[jira] [Commented] (KAFKA-725) Broker Exception: Attempt to read with a maximum offset less than start offset

[ https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272591#comment-15272591 ] Jun Rao commented on KAFKA-725: --- Yes, I agree. If the requested offset is > MaxOffset, it's b

[jira] [Commented] (KAFKA-725) Broker Exception: Attempt to read with a maximum offset less than start offset

[ https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272490#comment-15272490 ] Guozhang Wang commented on KAFKA-725: - Jun, thanks for pointing it out. While reverting

[jira] [Assigned] (KAFKA-3101) Optimize Aggregation Outputs

[ https://issues.apache.org/jira/browse/KAFKA-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck reassigned KAFKA-3101: -- Assignee: (was: Bill Bejeck) > Optimize Aggregation Outputs >

[jira] [Commented] (KAFKA-3101) Optimize Aggregation Outputs

[ https://issues.apache.org/jira/browse/KAFKA-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272433#comment-15272433 ] Bill Bejeck commented on KAFKA-3101: Hi [~enothereska], No problem. I was wrestling

[jira] [Work stopped] (KAFKA-3101) Optimize Aggregation Outputs

[ https://issues.apache.org/jira/browse/KAFKA-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3101 stopped by Bill Bejeck. -- > Optimize Aggregation Outputs > > > Key

[jira] [Commented] (KAFKA-3101) Optimize Aggregation Outputs

[ https://issues.apache.org/jira/browse/KAFKA-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272339#comment-15272339 ] Eno Thereska commented on KAFKA-3101: - Hi [~bbejeck], Thanks for picking this up. We'r

[jira] [Commented] (KAFKA-3525) max.reserved.broker.id off-by-one error

[ https://issues.apache.org/jira/browse/KAFKA-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272275#comment-15272275 ] Manikumar Reddy commented on KAFKA-3525: 1. Assume reserved.broker.max.id =1000 2.

[jira] [Updated] (KAFKA-3511) Provide built-in aggregators sum() and avg() in Kafka Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3511: Labels: api (was: api newbie) > Provide built-in aggregators sum() and avg() in Kafka Streams DSL >

[jira] [Commented] (KAFKA-3660) Log exception message in ControllerBrokerRequestBatch

[ https://issues.apache.org/jira/browse/KAFKA-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272265#comment-15272265 ] Flavio Junqueira commented on KAFKA-3660: - [~ijuma] could you have a look, pls? >

[GitHub] kafka pull request: KAFKA-3660: Log exception message in Controlle...

GitHub user fpj opened a pull request: https://github.com/apache/kafka/pull/1325 KAFKA-3660: Log exception message in ControllerBrokerRequestBatch You can merge this pull request into a Git repository by running: $ git pull https://github.com/fpj/kafka KAFKA-3660 Alternativel

[jira] [Commented] (KAFKA-3660) Log exception message in ControllerBrokerRequestBatch

[ https://issues.apache.org/jira/browse/KAFKA-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272263#comment-15272263 ] ASF GitHub Bot commented on KAFKA-3660: --- GitHub user fpj opened a pull request:

[jira] [Created] (KAFKA-3660) Log exception message in ControllerBrokerRequestBatch

Flavio Junqueira created KAFKA-3660: --- Summary: Log exception message in ControllerBrokerRequestBatch Key: KAFKA-3660 URL: https://issues.apache.org/jira/browse/KAFKA-3660 Project: Kafka Iss

  1   2   >