[jira] [Commented] (KAFKA-4900) Brokers stuck in controller re-election loop after failing to register metrics

[ https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929447#comment-15929447 ] Onur Karaman commented on KAFKA-4900: - Okay yeah with bad znode data, I could see how the controller

[jira] [Commented] (KAFKA-4859) Transient test failure: org.apache.kafka.streams.integration.JoinIntegrationTest.shouldCountClicksPerRegion (again)

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

[jira] [Resolved] (KAFKA-4859) Transient test failure: org.apache.kafka.streams.integration.JoinIntegrationTest.shouldCountClicksPerRegion (again)

[ https://issues.apache.org/jira/browse/KAFKA-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4859. -- Resolution: Fixed Fix Version/s: 0.11.0.0 Issue resolved by pull request 2682

[GitHub] kafka pull request #2682: KAFKA-4859: Set shorter commit interval for integr...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2682 --- 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

[jira] [Commented] (KAFKA-4885) processstreamwithcachedstatestore and other streams benchmarks fail occasionally

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

[jira] [Resolved] (KAFKA-4885) processstreamwithcachedstatestore and other streams benchmarks fail occasionally

[ https://issues.apache.org/jira/browse/KAFKA-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4885. -- Resolution: Fixed Issue resolved by pull request 2693

[GitHub] kafka pull request #2693: KAFKA-4885: Add client.close as exception handler ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2693 --- 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

[jira] [Commented] (KAFKA-4858) Long topic names created using old kafka-topics.sh can prevent newer brokers from joining any ISRs

[ https://issues.apache.org/jira/browse/KAFKA-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929421#comment-15929421 ] Jeff Widman commented on KAFKA-4858: I'd say if you patch it so that replication doesn't break, that's

[jira] [Commented] (KAFKA-4631) Refresh consumer metadata more frequently for unknown subscribed topics

[ https://issues.apache.org/jira/browse/KAFKA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929414#comment-15929414 ] jaikiran pai commented on KAFKA-4631: - Thanks [~hachikuji], am glad this made it to 0.10.x since that

[jira] [Commented] (KAFKA-4900) Brokers stuck in controller re-election loop after failing to register metrics

[ https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929381#comment-15929381 ] Nick Travers commented on KAFKA-4900: - Circling back on this, now that we (seemingly) have a

[jira] [Created] (KAFKA-4914) Partition re-assignment tool should check types before persisting state in ZooKeeper

Nick Travers created KAFKA-4914: --- Summary: Partition re-assignment tool should check types before persisting state in ZooKeeper Key: KAFKA-4914 URL: https://issues.apache.org/jira/browse/KAFKA-4914

Re: [DISCUSS] KIP-113: Support replicas movement between log directories

Hey Jun, After thinking about 14 more, I think your solution is reasonable. I have updated the KIP to specify that the number of ReplicaMoveThread defaults to # log dirs. Thanks! Dong On Thu, Mar 16, 2017 at 12:28 AM, Dong Lin wrote: > Hey Jun, > > Thanks for your

[jira] [Commented] (KAFKA-4858) Long topic names created using old kafka-topics.sh can prevent newer brokers from joining any ISRs

[ https://issues.apache.org/jira/browse/KAFKA-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929196#comment-15929196 ] Vahid Hashemian commented on KAFKA-4858: [~wushujames] Thanks for bringing those use cases up. I

[jira] [Updated] (KAFKA-4631) Refresh consumer metadata more frequently for unknown subscribed topics

[ https://issues.apache.org/jira/browse/KAFKA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4631: --- Fix Version/s: 0.10.2.1 > Refresh consumer metadata more frequently for unknown subscribed

[jira] [Commented] (KAFKA-4631) Refresh consumer metadata more frequently for unknown subscribed topics

[ https://issues.apache.org/jira/browse/KAFKA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928978#comment-15928978 ] Jason Gustafson commented on KAFKA-4631: Note: I'm merging this into 0.10.2 as well since it fixes

[GitHub] kafka pull request #2698: MINOR: Increase Throttle lower bound assertion in ...

GitHub user benstopford opened a pull request: https://github.com/apache/kafka/pull/2698 MINOR: Increase Throttle lower bound assertion in throttling_test You can merge this pull request into a Git repository by running: $ git pull https://github.com/benstopford/kafka

[jira] [Commented] (KAFKA-4863) Querying window store may return unwanted keys

[ https://issues.apache.org/jira/browse/KAFKA-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928902#comment-15928902 ] Xavier Léauté commented on KAFKA-4863: -- The current patch appears to solve the specific case

[GitHub] kafka pull request #2697: MINOR: fixed memory pollution in KafkaConsumer

GitHub user wlsc opened a pull request: https://github.com/apache/kafka/pull/2697 MINOR: fixed memory pollution in KafkaConsumer This PL fixes memory pollution in KafkaConsumer by removing creation of the unnecessary HashSet each time we need to create unmodifiableSet and using

[jira] [Created] (KAFKA-4913) creating a window store with one segment throws division by zero error

Xavier Léauté created KAFKA-4913: Summary: creating a window store with one segment throws division by zero error Key: KAFKA-4913 URL: https://issues.apache.org/jira/browse/KAFKA-4913 Project: Kafka

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

See Changes: [junrao] KAFKA-4901; Make ProduceRequest thread-safe -- [...truncated 7.47 KB...]

[jira] [Commented] (KAFKA-4396) Seeing offsets not resetting even when reset policy is configured explicitly

[ https://issues.apache.org/jira/browse/KAFKA-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928533#comment-15928533 ] Sean McKibben commented on KAFKA-4396: -- I'm seeing this behavior in a Kafka Streams application as

[jira] [Updated] (KAFKA-4912) Add check for topic name length

[ https://issues.apache.org/jira/browse/KAFKA-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4912: --- Labels: newbie (was: ) > Add check for topic name length > --- >

[jira] [Created] (KAFKA-4912) Add check for topic name length

Matthias J. Sax created KAFKA-4912: -- Summary: Add check for topic name length Key: KAFKA-4912 URL: https://issues.apache.org/jira/browse/KAFKA-4912 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-4912) Add check for topic name length

[ https://issues.apache.org/jira/browse/KAFKA-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4912: --- Description: We should check topic name length (if internal topics, and maybe for source

Re: [DISCUSS] KIP-82 - Add Record Headers

Hi, Everyone, Jason has been working on the new message format related to EOS ( https://github.com/apache/kafka/pull/2614). He has included the header changes proposed in the KIP, which reduces the overhead for supporting an additional message format change if done separately. Since the message

[jira] [Updated] (KAFKA-4903) Remove unused code for reading Shell command stdout and add unit test

[ https://issues.apache.org/jira/browse/KAFKA-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-4903: --- Summary: Remove unused code for reading Shell command stdout and add unit test (was:

[jira] [Commented] (KAFKA-4901) Make ProduceRequest thread-safe

[ https://issues.apache.org/jira/browse/KAFKA-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928347#comment-15928347 ] Jun Rao commented on KAFKA-4901: Not sure why the PR didn't show up here. Merged

[jira] [Commented] (KAFKA-4901) Make ProduceRequest thread-safe

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

[GitHub] kafka pull request #2689: KAFKA-4901: Make ProduceRequest thread-safe

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2689 --- 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

[GitHub] kafka pull request #2696: MINOR: Guard against NPE when throwing StreamsExce...

GitHub user miguno opened a pull request: https://github.com/apache/kafka/pull/2696 MINOR: Guard against NPE when throwing StreamsException on serializer mismatch You can merge this pull request into a Git repository by running: $ git pull https://github.com/miguno/kafka

[jira] [Commented] (KAFKA-4911) Add ProducerRecord to ProducerInterceptor#onAcknowledgement

[ https://issues.apache.org/jira/browse/KAFKA-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928218#comment-15928218 ] Kevin Conaway commented on KAFKA-4911: -- This would also be useful for error handling as well if you

[jira] [Commented] (KAFKA-4594) Annotate integration tests and provide gradle build targets to run subsets of tests

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

[GitHub] kafka pull request #2695: KAFKA-4594: Annotate integration tests and provide...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2695 KAFKA-4594: Annotate integration tests and provide gradle build targets to run subsets of tests This uses junit Categories to identify integration tests. Adds 2 new build targets: `integrationTest`

[jira] [Work started] (KAFKA-4594) Annotate integration tests and provide gradle build targets to run subsets of tests

[ https://issues.apache.org/jira/browse/KAFKA-4594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4594 started by Damian Guy. - > Annotate integration tests and provide gradle build targets to run subsets of >

[jira] [Created] (KAFKA-4911) Add ProducerRecord to ProducerInterceptor#onAcknowledgement

Kevin Conaway created KAFKA-4911: Summary: Add ProducerRecord to ProducerInterceptor#onAcknowledgement Key: KAFKA-4911 URL: https://issues.apache.org/jira/browse/KAFKA-4911 Project: Kafka

[jira] [Updated] (KAFKA-4910) kafka consumer not receiving messages

[ https://issues.apache.org/jira/browse/KAFKA-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhiwei updated KAFKA-4910: -- Description: kafka consumer not receiving messages consumer log： "2017-03-10 14:35:34,448" | INFO |

[jira] [Updated] (KAFKA-4910) kafka consumer not receiving messages

[ https://issues.apache.org/jira/browse/KAFKA-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhiwei updated KAFKA-4910: -- Attachment: 128314.jstack > kafka consumer not receiving messages > - > >

[jira] [Updated] (KAFKA-4910) kafka consumer not receiving messages

[ https://issues.apache.org/jira/browse/KAFKA-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhiwei updated KAFKA-4910: -- Attachment: (was: 128314.txt) > kafka consumer not receiving messages >

[jira] [Updated] (KAFKA-4910) kafka consumer not receiving messages

[ https://issues.apache.org/jira/browse/KAFKA-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhiwei updated KAFKA-4910: -- Attachment: 128314.txt > kafka consumer not receiving messages > - > >

[jira] [Created] (KAFKA-4910) kafka consumer not receiving messages

zhiwei created KAFKA-4910: - Summary: kafka consumer not receiving messages Key: KAFKA-4910 URL: https://issues.apache.org/jira/browse/KAFKA-4910 Project: Kafka Issue Type: Bug Components:

[jira] [Commented] (KAFKA-3594) Kafka new producer retries doesn't work in 0.9.0.1

[ https://issues.apache.org/jira/browse/KAFKA-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928059#comment-15928059 ] Phil Adams commented on KAFKA-3594: --- What is the recommended way to get a fix for this issue? I can't

[jira] [Updated] (KAFKA-3267) Describe/Alter Configs protocol and server side implementation (KIP-133)

[ https://issues.apache.org/jira/browse/KAFKA-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3267: --- Summary: Describe/Alter Configs protocol and server side implementation (KIP-133) (was:

[jira] [Updated] (KAFKA-2947) AlterTopic - protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2947: --- Fix Version/s: 0.11.0.0 > AlterTopic - protocol and server side implementation >

[jira] [Updated] (KAFKA-3267) Describe/Alter Configs protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3267: --- Fix Version/s: 0.11.0.0 > Describe/Alter Configs protocol and server side implementation >

[jira] [Updated] (KAFKA-3265) Create Java Admin Client

[ https://issues.apache.org/jira/browse/KAFKA-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3265: --- Fix Version/s: 0.11.0.0 > Create Java Admin Client > > >

[jira] [Assigned] (KAFKA-3267) Describe/Alter Configs protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3267: -- Assignee: Ismael Juma (was: Grant Henke) > Describe/Alter Configs protocol and server side

[jira] [Commented] (KAFKA-3267) Describe/Alter Configs protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928037#comment-15928037 ] Ismael Juma commented on KAFKA-3267: Assigning to myself after checking with [~granthenke]. >

[jira] [Comment Edited] (KAFKA-2947) AlterTopic - protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928032#comment-15928032 ] Ismael Juma edited comment on KAFKA-2947 at 3/16/17 1:36 PM: - [~cmccabe]

[jira] [Commented] (KAFKA-3355) GetOffsetShell command doesn't work with SASL enabled Kafka

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

[GitHub] kafka pull request #2289: KAFKA-3355

Github user garmes-gdev closed the pull request at: https://github.com/apache/kafka/pull/2289 --- 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

[jira] [Commented] (KAFKA-2947) AlterTopic - protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928032#comment-15928032 ] Ismael Juma commented on KAFKA-2947: [~cmccabe] started looking into this to complete the topic

[jira] [Assigned] (KAFKA-2947) AlterTopic - protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-2947: -- Assignee: Colin P. McCabe (was: Grant Henke) > AlterTopic - protocol and server side

[jira] [Resolved] (KAFKA-4909) run integration tests separate from unit tests

[ https://issues.apache.org/jira/browse/KAFKA-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-4909. --- Resolution: Duplicate > run integration tests separate from unit tests >

[jira] [Commented] (KAFKA-4594) Annotate integration tests and provide gradle build targets to run subsets of tests

[ https://issues.apache.org/jira/browse/KAFKA-4594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15927957#comment-15927957 ] Damian Guy commented on KAFKA-4594: --- [~manasvigupta] Sorry, i've already begun work on a duplicate of

[jira] [Assigned] (KAFKA-4594) Annotate integration tests and provide gradle build targets to run subsets of tests

[ https://issues.apache.org/jira/browse/KAFKA-4594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-4594: - Assignee: Damian Guy (was: Manasvi Gupta) > Annotate integration tests and provide gradle build

[jira] [Assigned] (KAFKA-4594) Annotate integration tests and provide gradle build targets to run subsets of tests

[ https://issues.apache.org/jira/browse/KAFKA-4594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manasvi Gupta reassigned KAFKA-4594: Assignee: Manasvi Gupta > Annotate integration tests and provide gradle build targets to

[jira] [Created] (KAFKA-4909) run integration tests separate from unit tests

Damian Guy created KAFKA-4909: - Summary: run integration tests separate from unit tests Key: KAFKA-4909 URL: https://issues.apache.org/jira/browse/KAFKA-4909 Project: Kafka Issue Type: New

[jira] [Commented] (KAFKA-3415) AdminOperationException when altering Topic with same number of partitions

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

[GitHub] kafka pull request #2694: MINOR: FetchRequest.Builder maxBytes for version <...

GitHub user edoardocomar opened a pull request: https://github.com/apache/kafka/pull/2694 MINOR: FetchRequest.Builder maxBytes for version <3 The maxBytes field should be set to DEFAULT_RESPONSE_MAX_BYTES, the same way as the constructor using the Struct does.

[GitHub] kafka pull request #1089: KAFKA-3415: Add partitions check if 0 partitions a...

Github user edoardocomar closed the pull request at: https://github.com/apache/kafka/pull/1089 --- 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

[jira] [Created] (KAFKA-4908) consumer.properties logging warnings

Seweryn Habdank-Wojewodzki created KAFKA-4908: - Summary: consumer.properties logging warnings Key: KAFKA-4908 URL: https://issues.apache.org/jira/browse/KAFKA-4908 Project: Kafka

Re: [DISCUSS] KIP-113: Support replicas movement between log directories

Hey Jun, Thanks for your comment! Please see my reply below. On Wed, Mar 15, 2017 at 9:45 PM, Jun Rao wrote: > Hi, Dong, > > Thanks for the reply. > > 10. Could you comment on that? > Sorry, I missed that comment. Good point. I think the log segments in topicPartition.move

[jira] [Commented] (KAFKA-4888) offset 449883 is invalid, cause: Record is corrupt (stored crc = 2171407101, computed crc = 1371274824)

[ https://issues.apache.org/jira/browse/KAFKA-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15927568#comment-15927568 ] Hanlin Liu commented on KAFKA-4888: --- [~junrao] We also suspect it's a network issue. We checked with