[jira] [Work started] (KAFKA-3611) Remove WARNs when using reflections

[ https://issues.apache.org/jira/browse/KAFKA-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3611 started by Liquan Pei. - > Remove WARNs when using reflections > > >

[jira] [Work started] (KAFKA-3611) Remove WARNs when using reflections

[ https://issues.apache.org/jira/browse/KAFKA-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3611 started by Liquan Pei. - > Remove WARNs when using reflections > > >

[jira] [Updated] (KAFKA-3611) Remove WARNs when using reflections

[ https://issues.apache.org/jira/browse/KAFKA-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-3611: -- Status: Patch Available (was: In Progress) > Remove WARNs when using reflections >

[jira] [Work stopped] (KAFKA-3611) Remove WARNs when using reflections

[ https://issues.apache.org/jira/browse/KAFKA-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3611 stopped by Liquan Pei. - > Remove WARNs when using reflections > > >

[GitHub] kafka pull request: KAFKA-3611: Remove warnings when using reflect...

GitHub user Ishiihara opened a pull request: https://github.com/apache/kafka/pull/1259 KAFKA-3611: Remove warnings when using reflections @ewencp @granders Can you take a look? Thanks! You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-3611) Remove WARNs when using reflections

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

[jira] [Created] (KAFKA-3611) Remove WARNs when using reflections

Liquan Pei created KAFKA-3611: - Summary: Remove WARNs when using reflections Key: KAFKA-3611 URL: https://issues.apache.org/jira/browse/KAFKA-3611 Project: Kafka Issue Type: Improvement

kafka 0.8.2.1 High CPU load

Hi，we are using kafka_2.10-0.8.2.1，and our vm machine config is：4 core，8G our cluster is consist of three brokers，and our broker config is default 2 replica，our broker load often very high once in a while， load is greater than 1.5 on average core。 we have about 70 topics on this cluster when we

[jira] [Commented] (KAFKA-3607) Close state stores explicitly in unit tests upon completing

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

[GitHub] kafka pull request: [WIP]KAFKA-3607: Close KStreamTestDriver upon ...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1258 [WIP]KAFKA-3607: Close KStreamTestDriver upon completing You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka K3607

Re: [VOTE] KIP-35: Retrieve protocol version - Round 2

+1 (non-binding) On Apr 22, 2016 3:33 PM, "Magnus Edenhill" wrote: > Good point Rajini, I will clarify that. > > Thanks, > Magnus > > 2016-04-22 12:35 GMT-07:00 Rajini Sivaram : > > > +1 (non-binding) > > > > One minor comment: > > > > "11: The

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

Hey Guys, If there are no objections or major modifications to suggest I would like to start a vote thread on this. I will wait till EOD today before starting a vote thread. On Thu, Apr 21, 2016 at 4:36 PM, Gwen Shapira wrote: > I would like to suggest taking the discussion

Re: [VOTE] KIP-35: Retrieve protocol version - Round 2

Good point Rajini, I will clarify that. Thanks, Magnus 2016-04-22 12:35 GMT-07:00 Rajini Sivaram : > +1 (non-binding) > > One minor comment: > > "11: The broker returns its full list of supported ApiKeys and versions > regardless of current authentication state

[jira] [Commented] (KAFKA-3128) Add metrics for ZooKeeper events

[ https://issues.apache.org/jira/browse/KAFKA-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254591#comment-15254591 ] Flavio Junqueira commented on KAFKA-3128: - [~junrao] Perhaps we can do more than just counting the

[jira] [Commented] (KAFKA-3579) TopicCommand references outdated consumer property fetch.message.max.bytes

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

[GitHub] kafka pull request: KAFKA-3579 - Update reference to the outdated ...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1239 KAFKA-3579 - Update reference to the outdated consumer property Replace references to the old consumer property 'fetch.message.max.bytes' with the corresponding property in the new

[jira] [Commented] (KAFKA-3579) TopicCommand references outdated consumer property fetch.message.max.bytes

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

[GitHub] kafka pull request: KAFKA-3579 - Update reference to the outdated ...

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

[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=15254550#comment-15254550 ] Jiangjie Qin commented on KAFKA-3565: - [~jkreps] [~ijuma] I ran the tests a few more times and

[GitHub] kafka pull request: KAFKA-3608: Fix ZooKeeper structures and outpu...

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

[jira] [Commented] (KAFKA-3608) ZooKeeper structures are not correctly described in the document

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

Re: [VOTE] KIP-35: Retrieve protocol version - Round 2

+1 (non-binding) One minor comment: "11: The broker returns its full list of supported ApiKeys and versions regardless of current authentication state (e.g., before SASL authentication). If this is considered to leak information SSL can be used for early authentication." It may be better to

[GitHub] kafka pull request: KAFKA-3579 - Update reference to the outdated ...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1239 KAFKA-3579 - Update reference to the outdated consumer property Replace references to the old consumer property 'fetch.message.max.bytes' with the corresponding property in the new

[GitHub] kafka pull request: KAFKA-3579 - Update reference to the outdated ...

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

[jira] [Commented] (KAFKA-3579) TopicCommand references outdated consumer property fetch.message.max.bytes

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

[jira] [Commented] (KAFKA-3579) TopicCommand references outdated consumer property fetch.message.max.bytes

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

Re: [VOTE] KIP-35: Retrieve protocol version - Round 2

+1 (non-binding) from me, assuming that the changes suggested by Jun below are included. Some minor comments. "5. Clients are recommended to use latest common supported API version." Maybe this would be clearer as: "Clients are recommended to use latest version supported by the broker and

[jira] [Updated] (KAFKA-3608) ZooKeeper structures are not correctly described in the document

[ https://issues.apache.org/jira/browse/KAFKA-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-3608: --- Status: Patch Available (was: Open) > ZooKeeper structures are not correctly described in

[GitHub] kafka pull request: KAFKA-3608: Fix ZooKeeper structures and outpu...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1257 KAFKA-3608: Fix ZooKeeper structures and output format in documentation You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-3608) ZooKeeper structures are not correctly described in the document

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

Re: [VOTE] KIP-35: Retrieve protocol version - Round 2

Hello Jun, On Fri, Apr 22, 2016 at 11:31 AM, Jun Rao wrote: > Ashish, > > Just a couple of clarifications. > > 1. In ApiVersionRequest, we should get rid of ApiKeys since the request has > an empty body, right? > Yes. > > 2. In ApiVersionResponse, we should list ErrorCode

Re: [VOTE] KIP-35: Retrieve protocol version - Round 2

Ashish, Just a couple of clarifications. 1. In ApiVersionRequest, we should get rid of ApiKeys since the request has an empty body, right? 2. In ApiVersionResponse, we should list ErrorCode before ApiVersions, right? Thanks, Jun On Thu, Apr 21, 2016 at 4:48 PM, Ashish Singh

[jira] [Commented] (KAFKA-3128) Add metrics for ZooKeeper events

[ https://issues.apache.org/jira/browse/KAFKA-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254407#comment-15254407 ] Jun Rao commented on KAFKA-3128: ZKClient probably doesn't expose connection loss events. So, in 0.10.0,

[jira] [Commented] (KAFKA-3579) TopicCommand references outdated consumer property fetch.message.max.bytes

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

[jira] [Commented] (KAFKA-3579) TopicCommand references outdated consumer property fetch.message.max.bytes

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

[GitHub] kafka pull request: KAFKA-3579 - Update reference to the outdated ...

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

[GitHub] kafka pull request: KAFKA-3579 - Update reference to the outdated ...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1239 KAFKA-3579 - Update reference to the outdated consumer property Replace references to the old consumer property 'fetch.message.max.bytes' with the corresponding property in the new

[jira] [Assigned] (KAFKA-3608) ZooKeeper structures are not correctly described in the document

[ https://issues.apache.org/jira/browse/KAFKA-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-3608: -- Assignee: Vahid Hashemian > ZooKeeper structures are not correctly described in the

[jira] [Commented] (KAFKA-3610) Improve TimeoutException message when a RecordBatch expires

[ https://issues.apache.org/jira/browse/KAFKA-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254212#comment-15254212 ] Ismael Juma commented on KAFKA-3610: Some brief guidance seems like a good idea (users can check the

[jira] [Commented] (KAFKA-3610) Improve TimeoutException message when a RecordBatch expires

[ https://issues.apache.org/jira/browse/KAFKA-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254205#comment-15254205 ] Grant Henke commented on KAFKA-3610: Thinking further, perhaps documentation is a better place for

[jira] [Commented] (KAFKA-3610) Improve TimeoutException message when a RecordBatch expires

[ https://issues.apache.org/jira/browse/KAFKA-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254190#comment-15254190 ] Grant Henke commented on KAFKA-3610: [~ijuma] You are right it is improved in trunk. Since recordCount

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

See Changes: [cshapi] KAFKA-3605: Return error if connector config includes mismatching -- [...truncated 2437 lines...] kafka.api.SslConsumerTest > testPartitionReassignmentCallback PASSED

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

See Changes: [cshapi] KAFKA-3605: Return error if connector config includes mismatching -- [...truncated 3785 lines...] org.apache.kafka.common.SerializeCompatibilityTopicPartitionTest >

[jira] [Commented] (KAFKA-3610) Improve TimeoutException message when a RecordBatch expires

[ https://issues.apache.org/jira/browse/KAFKA-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254136#comment-15254136 ] Ismael Juma commented on KAFKA-3610: This is fixed in trunk, right? > Improve TimeoutException

[jira] [Created] (KAFKA-3610) Improve TimeoutException message when a RecordBatch expires

Grant Henke created KAFKA-3610: -- Summary: Improve TimeoutException message when a RecordBatch expires Key: KAFKA-3610 URL: https://issues.apache.org/jira/browse/KAFKA-3610 Project: Kafka Issue

Re: [DISCUSS] KIP-55: Secure quotas for authenticated users

The PR for KAFKA-3492 (https://github.com/apache/kafka/pull/1256) contains the code associated with KIP-55. I will keep it updated during the review process. Thanks, Rajini On Mon, Apr 18, 2016 at 4:41 PM, Rajini Sivaram < rajinisiva...@googlemail.com> wrote: > Hi All, > > I have just created

[jira] [Commented] (KAFKA-3570) It'd be nice to line up display output in columns in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15253998#comment-15253998 ] Mickael Maison commented on KAFKA-3570: --- I believe this has been fixed in 0.10 by this commit:

[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=15254011#comment-15254011 ] ASF GitHub Bot commented on KAFKA-3492: --- GitHub user rajinisivaram opened a pull request:

[GitHub] kafka pull request: KAFKA-3492: Secure quotas for authenticated us...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/1256 KAFKA-3492: Secure quotas for authenticated users Code associated with KIP-55 to enable secure quotas for authenticated users with sub-quotas for client-ids of a user. You can merge this

[jira] [Commented] (KAFKA-3605) Connector REST endpoint allows incorrectly overriding the connector name

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

[jira] [Updated] (KAFKA-3605) Connector REST endpoint allows incorrectly overriding the connector name

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

[GitHub] kafka pull request: KAFKA-3605: Return error if connector config i...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1253 --- 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-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=15253833#comment-15253833 ] Edoardo Comar commented on KAFKA-3587: -- Hi I was having a look at this issue too. in

[GitHub] kafka pull request: MINOR: add unit test for KGroupedTable.count

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/1255 MINOR: add unit test for KGroupedTable.count You can merge this pull request into a Git repository by running: $ git pull https://github.com/dguy/kafka kgroupedtable-count-test Alternatively

[jira] [Commented] (KAFKA-3609) Implement partial mirroring functionality in Kafka Mirror Maker

[ https://issues.apache.org/jira/browse/KAFKA-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15253761#comment-15253761 ] Manikumar Reddy commented on KAFKA-3609: Current Mirror Maker supports partial mirroring of topics

[jira] [Created] (KAFKA-3609) Implement partial mirroring functionality in Kafka Mirror Maker

Sukhdev Saini created KAFKA-3609: Summary: Implement partial mirroring functionality in Kafka Mirror Maker Key: KAFKA-3609 URL: https://issues.apache.org/jira/browse/KAFKA-3609 Project: Kafka

[jira] [Updated] (KAFKA-3517) Document configuration of SASL/PLAIN and multiple mechanisms

[ https://issues.apache.org/jira/browse/KAFKA-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-3517: --- Status: Patch Available (was: Open) > Document configuration of SASL/PLAIN and multiple

[jira] [Updated] (KAFKA-3605) Connector REST endpoint allows incorrectly overriding the connector name

[ https://issues.apache.org/jira/browse/KAFKA-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-3605: --- Status: Patch Available (was: Reopened) > Connector REST endpoint allows incorrectly

[jira] [Assigned] (KAFKA-3584) NullPointer Exception found when Delete Topic and Log delete concurrent

[ https://issues.apache.org/jira/browse/KAFKA-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy reassigned KAFKA-3584: -- Assignee: Manikumar Reddy (was: Jay Kreps) > NullPointer Exception found when Delete

[jira] [Assigned] (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 ] Manikumar Reddy reassigned KAFKA-3587: -- Assignee: Manikumar Reddy > LogCleaner fails due to incorrect offset map computation

[jira] [Updated] (KAFKA-3602) Rename RecordAccumulator dequeFor() and ensure proper usage

[ https://issues.apache.org/jira/browse/KAFKA-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-3602: --- Status: Patch Available (was: Open) > Rename RecordAccumulator dequeFor() and ensure proper

[jira] [Created] (KAFKA-3608) ZooKeeper structures are not correctly described in the document

Eric Huang created KAFKA-3608: - Summary: ZooKeeper structures are not correctly described in the document Key: KAFKA-3608 URL: https://issues.apache.org/jira/browse/KAFKA-3608 Project: Kafka