[jira] [Commented] (KAFKA-2835) FAILING TEST: LogCleaner

[ https://issues.apache.org/jira/browse/KAFKA-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15063664#comment-15063664 ] jin xing commented on KAFKA-2835: - related to KAFKA-2977, already patch available > FAILING TEST:

[GitHub] kafka pull request: KAFKA-2455: Test Failure: kafka.consumer.Metri...

GitHub user ZoneMayor opened a pull request: https://github.com/apache/kafka/pull/694 KAFKA-2455: Test Failure: kafka.consumer.MetricsTest > testMetricsLeak @guozhangwang I reproduced this; Every time this test failed, I found extra "type=DelayedFetchMetrics,

[jira] [Updated] (KAFKA-2455) Test Failure: kafka.consumer.MetricsTest > testMetricsLeak

[ https://issues.apache.org/jira/browse/KAFKA-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jin xing updated KAFKA-2455: Labels: newbie (was: ) Assignee: jin xing Reviewer: Guozhang Wang

[GitHub] kafka pull request: KAFKA-2977: Transient Failure in kafka.log.Log...

Github user ZoneMayor closed the pull request at: https://github.com/apache/kafka/pull/671 --- 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-2455) Test Failure: kafka.consumer.MetricsTest > testMetricsLeak

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

[jira] [Commented] (KAFKA-2977) Transient Failure in kafka.log.LogCleanerIntegrationTest.cleanerTest

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

[jira] [Commented] (KAFKA-2977) Transient Failure in kafka.log.LogCleanerIntegrationTest.cleanerTest

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

[GitHub] kafka pull request: KAFKA-2977: Transient Failure in kafka.log.Log...

GitHub user ZoneMayor reopened a pull request: https://github.com/apache/kafka/pull/671 KAFKA-2977: Transient Failure in kafka.log.LogCleanerIntegrationTest.cleanerTest Hi @guozhangwang Code is as below: val appends = writeDups(numKeys = 100, numDups = 3, log,

[jira] [Commented] (KAFKA-3007) new Consumer should expose mechanism to fetch single message, consumer.poll(timeout, maxMessageLimit)

[ https://issues.apache.org/jira/browse/KAFKA-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064110#comment-15064110 ] Jens Rantil commented on KAFKA-3007: > Is this on the dev mailing list? If so, please can you share a

[jira] [Commented] (KAFKA-2310) Add config to prevent broker becoming controller

[ https://issues.apache.org/jira/browse/KAFKA-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064136#comment-15064136 ] Stevo Slavic commented on KAFKA-2310: - Preventing broker from becoming controller, and controller

Re: Consider increasing the default reserved.broker.max.id

Hi Grant, On Fri, Dec 18, 2015 at 4:07 PM, Grant Henke wrote: > I have seen a few issues utilizing the default value of > reserved.broker.max.id=1000 in existing clusters during upgrades. 1000 seems a bit low to me too and a larger number seems safer. It would be good to

[jira] [Comment Edited] (KAFKA-2310) Add config to prevent broker becoming controller

[ https://issues.apache.org/jira/browse/KAFKA-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064136#comment-15064136 ] Stevo Slavic edited comment on KAFKA-2310 at 12/18/15 4:04 PM: --- Enabling

[jira] [Commented] (KAFKA-3007) new Consumer should expose mechanism to fetch single message, consumer.poll(timeout, maxMessageLimit)

[ https://issues.apache.org/jira/browse/KAFKA-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064073#comment-15064073 ] Jens Rantil commented on KAFKA-3007: Fixing this issue, would probably fix that issue. > new Consumer

[jira] [Commented] (KAFKA-3006) Make collection default container type for sequences in the consumer API

[ https://issues.apache.org/jira/browse/KAFKA-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064119#comment-15064119 ] Pierre-Yves Ritschard commented on KAFKA-3006: -- [~granthenke] I am not going to argue with

[jira] [Commented] (KAFKA-3006) Make collection default container type for sequences in the consumer API

[ https://issues.apache.org/jira/browse/KAFKA-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064112#comment-15064112 ] Grant Henke commented on KAFKA-3006: I am for fixing it the right way, and utilizing the fact that it

[jira] [Updated] (KAFKA-269) ./system_test/producer_perf/bin/run-test.sh without --async flag does not run

[ https://issues.apache.org/jira/browse/KAFKA-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-269: Resolution: Won't Fix Reviewer: Ewen Cheslack-Postava Status: Resolved

[jira] [Commented] (KAFKA-3006) Make collection default container type for sequences in the consumer API

[ https://issues.apache.org/jira/browse/KAFKA-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064182#comment-15064182 ] Pierre-Yves Ritschard commented on KAFKA-3006: -- [~granthenke] ok, i'll wait for more opinions

[jira] [Updated] (KAFKA-868) System Test - add test case for rolling controlled shutdown

[ https://issues.apache.org/jira/browse/KAFKA-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-868: Resolution: Fixed Reviewer: Ewen Cheslack-Postava Fix Version/s:

[jira] [Work started] (KAFKA-2069) Replace OffsetFetch request/response with their org.apache.kafka.common.requests equivalent

[ https://issues.apache.org/jira/browse/KAFKA-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-2069 started by Grant Henke. -- > Replace OffsetFetch request/response with their >

[jira] [Assigned] (KAFKA-2069) Replace OffsetFetch request/response with their org.apache.kafka.common.requests equivalent

[ https://issues.apache.org/jira/browse/KAFKA-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-2069: -- Assignee: Grant Henke (was: Ashish K Singh) > Replace OffsetFetch request/response with their

[jira] [Commented] (KAFKA-2937) Topics marked for delete in Zookeeper may become undeletable

[ https://issues.apache.org/jira/browse/KAFKA-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064365#comment-15064365 ] Mayuresh Gharat commented on KAFKA-2937: I ran a test with few commits behind trunk HEAD : 1)

Re: Consider increasing the default reserved.broker.max.id

There is some discussion on KAFKA-1070 around the design choice and compatibility. The value 1000 was thrown out as a quick example but it was never discussed beyond that. The discussion also sites a few cases where a value of 1000 would cause

[jira] [Resolved] (KAFKA-392) Refactor and optimize system tests

[ https://issues.apache.org/jira/browse/KAFKA-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-392. - Resolution: Won't Fix Fix Version/s: (was: 0.10.0.0) This is for the

[jira] [Updated] (KAFKA-645) Create a shell script to run System Test with DEBUG details and "tee" console output to a file

[ https://issues.apache.org/jira/browse/KAFKA-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-645: Resolution: Won't Fix Reviewer: Ewen Cheslack-Postava Status: Resolved

Re: Consider increasing the default reserved.broker.max.id

On Fri, Dec 18, 2015 at 4:44 PM, Grant Henke wrote: > There is some discussion on KAFKA-1070 > around the design > choice > and compatibility. The value 1000 was thrown out as a quick example but it > was never discussed

[jira] [Created] (KAFKA-3014) Integer overflow causes incorrect node iteration in leastLoadedNode()

Jason Gustafson created KAFKA-3014: -- Summary: Integer overflow causes incorrect node iteration in leastLoadedNode() Key: KAFKA-3014 URL: https://issues.apache.org/jira/browse/KAFKA-3014 Project:

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

See Changes: [me] MINOR: Change return type of `Schema.read` to be `Struct` instead of -- [...truncated 2802 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest >

[jira] [Commented] (KAFKA-3006) Make collection default container type for sequences in the consumer API

[ https://issues.apache.org/jira/browse/KAFKA-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064523#comment-15064523 ] Ewen Cheslack-Postava commented on KAFKA-3006: -- [~gwenshap] I double checked because of

[jira] [Commented] (KAFKA-3006) Make collection default container type for sequences in the consumer API

[ https://issues.apache.org/jira/browse/KAFKA-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064547#comment-15064547 ] Gwen Shapira commented on KAFKA-3006: - Yeah, I was thinking about it in the context of the move to the

[jira] [Commented] (KAFKA-3014) Integer overflow causes incorrect node iteration in leastLoadedNode()

[ https://issues.apache.org/jira/browse/KAFKA-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064548#comment-15064548 ] Ismael Juma commented on KAFKA-3014: Nice catch! > Integer overflow causes incorrect node iteration

[jira] [Created] (KAFKA-3013) Display the topic-partition in the exception message for expired batches in recordAccumulator

Mayuresh Gharat created KAFKA-3013: -- Summary: Display the topic-partition in the exception message for expired batches in recordAccumulator Key: KAFKA-3013 URL: https://issues.apache.org/jira/browse/KAFKA-3013

[jira] [Commented] (KAFKA-3013) Display the topic-partition in the exception message for expired batches in recordAccumulator

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

[jira] [Commented] (KAFKA-3006) Make collection default container type for sequences in the consumer API

[ https://issues.apache.org/jira/browse/KAFKA-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064478#comment-15064478 ] Gwen Shapira commented on KAFKA-3006: - I'm not seeing how stream processing frameworks are impacted.

[GitHub] kafka pull request: MINOR: Change return type of `Schema.read` to ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/684 --- 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-3006) Make collection default container type for sequences in the consumer API

[ https://issues.apache.org/jira/browse/KAFKA-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064502#comment-15064502 ] Jay Kreps commented on KAFKA-3006: -- [~gwenshap] Yeah I suppose you're right, I was thinking you'd end up

[jira] [Created] (KAFKA-3015) Improve JBOD data balancing

Jay Kreps created KAFKA-3015: Summary: Improve JBOD data balancing Key: KAFKA-3015 URL: https://issues.apache.org/jira/browse/KAFKA-3015 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-3014) Integer overflow causes incorrect node iteration in leastLoadedNode()

[ https://issues.apache.org/jira/browse/KAFKA-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064685#comment-15064685 ] Guozhang Wang commented on KAFKA-3014: -- This is great find! > Integer overflow causes incorrect node

[GitHub] kafka pull request: KAFKA-3013

GitHub user MayureshGharat opened a pull request: https://github.com/apache/kafka/pull/695 KAFKA-3013 Added topic-partition information to the exception message on batch expiry in RecordAccumulator You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-2000) Delete consumer offsets from kafka once the topic is deleted

[ https://issues.apache.org/jira/browse/KAFKA-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064564#comment-15064564 ] Parth Brahmbhatt commented on KAFKA-2000: - Talked to [~harsha_ch] , I will submit an updated patch

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

See Changes: [me] MINOR: Change return type of `Schema.read` to be `Struct` instead of -- [...truncated 3577 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[0] PASSED

[jira] [Commented] (KAFKA-2953) Kafka documentation is really wide

[ https://issues.apache.org/jira/browse/KAFKA-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065013#comment-15065013 ] Chris Horrocks commented on KAFKA-2953: --- Agreed, the LinkedIn engineering blog posts are generally

[GitHub] kafka pull request: KAFKA-1860

GitHub user MayureshGharat opened a pull request: https://github.com/apache/kafka/pull/698 KAFKA-1860 The JVM should stop if the underlying file system goes in to Read only mode You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-1860) File system errors are not detected unless Kafka tries to write

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

[jira] [Commented] (KAFKA-1860) File system errors are not detected unless Kafka tries to write

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

[GitHub] kafka pull request: KAFKA-1860

Github user MayureshGharat closed the pull request at: https://github.com/apache/kafka/pull/697 --- 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-3016) Add KStream-KStream window joins

Yasuhiro Matsuda created KAFKA-3016: --- Summary: Add KStream-KStream window joins Key: KAFKA-3016 URL: https://issues.apache.org/jira/browse/KAFKA-3016 Project: Kafka Issue Type: Sub-task

[jira] [Assigned] (KAFKA-3010) include error code when logging an error when ack = 0

[ https://issues.apache.org/jira/browse/KAFKA-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3010: -- Assignee: Ismael Juma > include error code when logging an error when ack = 0 >

[jira] [Work started] (KAFKA-2836) FAILING TEST: SaslSslTopicMetadataTest

[ https://issues.apache.org/jira/browse/KAFKA-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-2836 started by Bill Bejeck. -- > FAILING TEST: SaslSslTopicMetadataTest > -- >

[jira] [Commented] (KAFKA-3006) Make collection default container type for sequences in the consumer API

[ https://issues.apache.org/jira/browse/KAFKA-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064125#comment-15064125 ] Grant Henke commented on KAFKA-3006: [~pyritschard] Just know that my opinion is by no means

Consider increasing the default reserved.broker.max.id

I have seen a few issues utilizing the default value of reserved.broker.max.id=1000 in existing clusters during upgrades. For many that started broker.ids at 0 and incremented by 1 this may not be an issue. However, others may have very different numbering schemes. Given that we have the entire

[GitHub] kafka pull request: KAFKA-1860

GitHub user MayureshGharat opened a pull request: https://github.com/apache/kafka/pull/697 KAFKA-1860 The JVM should stop if the underlying file system goes in to Read only mode You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-1860) File system errors are not detected unless Kafka tries to write

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

[jira] [Commented] (KAFKA-3015) Improve JBOD data balancing

[ https://issues.apache.org/jira/browse/KAFKA-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064740#comment-15064740 ] Gwen Shapira commented on KAFKA-3015: - +1 Currently we work around the issue by using RAID-0 to

[GitHub] kafka pull request: KAFKA-3014: fix integer overflow problem in le...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/696 KAFKA-3014: fix integer overflow problem in leastLoadedNode You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-3014

[jira] [Commented] (KAFKA-3006) Make collection default container type for sequences in the consumer API

[ https://issues.apache.org/jira/browse/KAFKA-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064819#comment-15064819 ] Pierre-Yves Ritschard commented on KAFKA-3006: -- Hi, I just wanted to clarify something. The

[jira] [Commented] (KAFKA-3014) Integer overflow causes incorrect node iteration in leastLoadedNode()

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

[jira] [Commented] (KAFKA-3006) Make collection default container type for sequences in the consumer API

[ https://issues.apache.org/jira/browse/KAFKA-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064879#comment-15064879 ] Pierre-Yves Ritschard commented on KAFKA-3006: -- I pushed a version with the superfluous

[jira] [Commented] (KAFKA-3017) hostnames with underscores '_' are not valid

[ https://issues.apache.org/jira/browse/KAFKA-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065227#comment-15065227 ] Manikumar Reddy commented on KAFKA-3017: The Internet standards (Requests for Comments) for

[jira] [Created] (KAFKA-3017) hostnames with underscores '_' are not valid

Michael Martin created KAFKA-3017: - Summary: hostnames with underscores '_' are not valid Key: KAFKA-3017 URL: https://issues.apache.org/jira/browse/KAFKA-3017 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3015) Improve JBOD data balancing

[ https://issues.apache.org/jira/browse/KAFKA-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065237#comment-15065237 ] Guozhang Wang commented on KAFKA-3015: -- Would be definitely good to add. [~jkreps] I remember you

[jira] [Commented] (KAFKA-3015) Improve JBOD data balancing

[ https://issues.apache.org/jira/browse/KAFKA-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065239#comment-15065239 ] Todd Palino commented on KAFKA-3015: While this seems good on the surface, it makes it impossible to

[jira] [Updated] (KAFKA-2455) Test Failure: kafka.consumer.MetricsTest > testMetricsLeak

[ https://issues.apache.org/jira/browse/KAFKA-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2455: - Reviewer: Ismael Juma (was: Guozhang Wang) > Test Failure: kafka.consumer.MetricsTest >