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

See Changes: [wangguoz] KAFKA-3470: treat commits as member heartbeats -- [...truncated 3190 lines...] kafka.KafkaTest > testGetKafkaConfigFromArgs PASSED kafka.KafkaTest >

[jira] [Commented] (KAFKA-3470) Consumer group coordinator should take commit requests as effective as heartbeats

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

[GitHub] kafka pull request: KAFKA-3470: treat commits as member heartbeats

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1206 --- 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] [Resolved] (KAFKA-3470) Consumer group coordinator should take commit requests as effective as heartbeats

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

[jira] [Created] (KAFKA-3556) Improve group coordinator metrics

Jason Gustafson created KAFKA-3556: -- Summary: Improve group coordinator metrics Key: KAFKA-3556 URL: https://issues.apache.org/jira/browse/KAFKA-3556 Project: Kafka Issue Type: Improvement

[jira] [Assigned] (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 ] Ishita Mandhan reassigned KAFKA-3511: - Assignee: Ishita Mandhan > Provide built-in aggregators sum() and avg() in Kafka Streams

[jira] [Created] (KAFKA-3555) Unexpected close of KStreams transformer

Anna Povzner created KAFKA-3555: --- Summary: Unexpected close of KStreams transformer Key: KAFKA-3555 URL: https://issues.apache.org/jira/browse/KAFKA-3555 Project: Kafka Issue Type: Bug

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

See

[jira] [Commented] (KAFKA-3552) New Consumer: java.lang.OutOfMemoryError: Direct buffer memory

[ https://issues.apache.org/jira/browse/KAFKA-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15240051#comment-15240051 ] Kanak Biscuitwala commented on KAFKA-3552: -- Looks like there is a full GC immediately before the

[jira] [Updated] (KAFKA-3552) New Consumer: java.lang.OutOfMemoryError: Direct buffer memory

[ https://issues.apache.org/jira/browse/KAFKA-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kanak Biscuitwala updated KAFKA-3552: - Attachment: Screen Shot 2016-04-13 at 11.56.05 AM.png Screen Shot

[jira] [Commented] (KAFKA-3490) Multiple version support for ducktape performance tests

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

[GitHub] kafka pull request: KAFKA-3490; Multiple version support for duckt...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1173 --- 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] [Updated] (KAFKA-3490) Multiple version support for ducktape performance tests

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

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239897#comment-15239897 ] Alexander Binzberger commented on KAFKA-3042: - In my case it was high load on the network. Had

Re: Problem with kafka doFlush method

Hi Are you using the JDBC connector? Can you share with me the command and configuration that you were running? Thanks, Liquan On Wed, Mar 23, 2016 at 8:36 AM, Aleksandar Pejakovic wrote: > Hi, > > > I have created Confluent Connect

[jira] [Commented] (KAFKA-3492) support quota based on authenticated user name

[ https://issues.apache.org/jira/browse/KAFKA-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239810#comment-15239810 ] Scott Kruger commented on KAFKA-3492: - Really, I think the important thing is to be able to control

[jira] [Commented] (KAFKA-3492) support quota based on authenticated user name

[ https://issues.apache.org/jira/browse/KAFKA-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239806#comment-15239806 ] Scott Kruger commented on KAFKA-3492: - It would nice to be able to assign clients minimum percentages

[jira] [Updated] (KAFKA-3554) Generate actual data with specific compression ratio in the ProducerPerformance tool.

[ https://issues.apache.org/jira/browse/KAFKA-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3554: Affects Version/s: 0.9.0.1 Fix Version/s: 0.10.1.0 > Generate actual data with specific

[jira] [Created] (KAFKA-3554) Generate actual data with specific compression ratio in the ProducerPerformance tool.

Jiangjie Qin created KAFKA-3554: --- Summary: Generate actual data with specific compression ratio in the ProducerPerformance tool. Key: KAFKA-3554 URL: https://issues.apache.org/jira/browse/KAFKA-3554

[jira] [Updated] (KAFKA-3554) Generate actual data with specific compression ratio in the ProducerPerformance tool.

[ https://issues.apache.org/jira/browse/KAFKA-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3554: Assignee: Dong Lin > Generate actual data with specific compression ratio in the >

[jira] [Commented] (KAFKA-3358) Only request metadata updates once we have topics or a pattern subscription

[ https://issues.apache.org/jira/browse/KAFKA-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239604#comment-15239604 ] Jason Gustafson commented on KAFKA-3358: I can confirm Phil Luckhurst's investigation. This issue

Re: [VOTE] KIP-33 - Add a time based log index

Hi Jun and Guozhang, I have updated the KIP wiki to incorporate your comments. Please let me know if you prefer starting another discussion thread for further discussion. Thanks, Jiangjie (Becket) Qin On Mon, Apr 11, 2016 at 12:21 AM, Becket Qin wrote: > Hi Guozhang and

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239575#comment-15239575 ] Jun Rao commented on KAFKA-3042: [~ismael juma], we fixed a few issues related to soft failure post 0.8.2.

[jira] [Comment Edited] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239575#comment-15239575 ] Jun Rao edited comment on KAFKA-3042 at 4/13/16 4:45 PM: - [~ijuma]], we fixed a

[jira] [Comment Edited] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239575#comment-15239575 ] Jun Rao edited comment on KAFKA-3042 at 4/13/16 4:45 PM: - [~ijuma], we fixed a few

[jira] [Commented] (KAFKA-3410) Unclean leader election and "Halting because log truncation is not allowed"

[ https://issues.apache.org/jira/browse/KAFKA-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239469#comment-15239469 ] Jun Rao commented on KAFKA-3410: [~james cheng], for #2, what you suggested makes sense. Instead of

[jira] [Assigned] (KAFKA-3522) Consider adding version information into rocksDB storage format

[ https://issues.apache.org/jira/browse/KAFKA-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-3522: --- Assignee: Eno Thereska > Consider adding version information into rocksDB storage format >

[jira] [Commented] (KAFKA-3548) Locale is not handled properly in kafka-consumer

[ https://issues.apache.org/jira/browse/KAFKA-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239434#comment-15239434 ] Ismael Juma commented on KAFKA-3548: [~rsivaram], please go ahead. > Locale is not handled properly

[jira] [Updated] (KAFKA-3548) Locale is not handled properly in kafka-consumer

[ https://issues.apache.org/jira/browse/KAFKA-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3548: --- Assignee: Rajini Sivaram (was: Neha Narkhede) > Locale is not handled properly in kafka-consumer >

[jira] [Commented] (KAFKA-3548) Locale is not handled properly in kafka-consumer

[ https://issues.apache.org/jira/browse/KAFKA-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239431#comment-15239431 ] Rajini Sivaram commented on KAFKA-3548: --- [~nehanarkhede] Is anyone working on this issue? Otherwise,

[jira] [Created] (KAFKA-3553) Issue with getting data of next offset after restarting the consumer and producer is always running

pooja sadashiv deokar created KAFKA-3553: Summary: Issue with getting data of next offset after restarting the consumer and producer is always running Key: KAFKA-3553 URL:

[jira] [Updated] (KAFKA-3149) Extend SASL implementation to support more mechanisms

[ https://issues.apache.org/jira/browse/KAFKA-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3149: -- Fix Version/s: 0.10.0.0 Status: Patch Available (was: Open) Updated based on the

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

I have updated the PR (https://github.com/apache/kafka/pull/812) and KIP-43 to use standard Kafka format for the new request/response added by KIP-43. I haven't changed the overall structure of the Java code. Feedback is appreciated. Thanks, Rajini On Tue, Apr 12, 2016 at 3:52 PM, Ismael Juma

[jira] [Commented] (KAFKA-3358) Only request metadata updates once we have topics or a pattern subscription

[ https://issues.apache.org/jira/browse/KAFKA-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239013#comment-15239013 ] Ismael Juma commented on KAFKA-3358: Phil Luckhurst mentioned in the mailing list that an additional

[jira] [Updated] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3042: --- Fix Version/s: 0.10.0.0 > updateIsr should stop after failed several times due to zkVersion issue >

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238721#comment-15238721 ] Ismael Juma commented on KAFKA-3042: [~junrao], some people have said that they have seen this issue