[jira] [Comment Edited] (KAFKA-3811) Introduce Kafka Streams metrics recording levels

2016-06-12 Thread aarti gupta (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326855#comment-15326855 ] aarti gupta edited comment on KAFKA-3811 at 6/13/16 5:51 AM: -

[jira] [Commented] (KAFKA-3811) Introduce Kafka Streams metrics recording levels

2016-06-12 Thread aarti gupta (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326855#comment-15326855 ] aarti gupta commented on KAFKA-3811: Yes indeed, as per http://www.brendangregg.com/b

Re: Any restrictions on consumer group name?

2016-06-12 Thread Jaikiran Pai
Adding the Kafka dev list to cc, hoping they would answer this question. -Jaikiran On Friday 10 June 2016 11:18 AM, Jaikiran Pai wrote: We are using 0.9.0.1 of Kafka server and (Java) clients. Our (Java) consumers are assigned to dynamic runtime generated groups i.e. the consumer group name is

[jira] [Assigned] (KAFKA-3827) log.message.format.version should default to inter.broker.protocol.version

2016-06-12 Thread Manasvi Gupta (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manasvi Gupta reassigned KAFKA-3827: Assignee: Manasvi Gupta > log.message.format.version should default to inter.broker.protoco

[jira] [Commented] (KAFKA-3769) KStream job spending 60% of time writing metrics

2016-06-12 Thread Greg Fodor (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326778#comment-15326778 ] Greg Fodor commented on KAFKA-3769: --- Discussion/resolution moved to: https://issues.apac

[jira] [Created] (KAFKA-3828) Consumer thread stalls after consumer re balance for some partition

2016-06-12 Thread Joseph Aliase (JIRA)
Joseph Aliase created KAFKA-3828: Summary: Consumer thread stalls after consumer re balance for some partition Key: KAFKA-3828 URL: https://issues.apache.org/jira/browse/KAFKA-3828 Project: Kafka

[jira] [Commented] (KAFKA-3818) Change Mirror Maker default assignment strategy to round robin

2016-06-12 Thread Jason Gustafson (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326657#comment-15326657 ] Jason Gustafson commented on KAFKA-3818: [~ewencp] Yeah, that probably makes sense

[jira] [Commented] (KAFKA-2857) ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when describing a non-existent group before the offset topic is created

2016-06-12 Thread Jason Gustafson (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326653#comment-15326653 ] Jason Gustafson commented on KAFKA-2857: [~imandhan] The __consumer_offsets topic

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

2016-06-12 Thread Jun Rao
Just to add on that list. 2. It would be good to document the format of the data stored in ZK. 7. Earlier, there was a discussion on whether the tokens should be propagated through ZK like config/acl/quota, or through the controller. Currently, the controller is only designed for propagating topic

Re: [DISCUSS] KIP-4 Create Topic Schema

2016-06-12 Thread Jun Rao
Grant, Thanks for the proposal. It looks good to me. You probably want to make it clearer if timeout > 0, what waiting for topic metadata is "complete" means. In the first implementation, it really means that the topic metadata is propagated to the controller's metadata cache. Jun On Fri, Jun 1

[jira] [Created] (KAFKA-3827) log.message.format.version should default to inter.broker.protocol.version

2016-06-12 Thread Jun Rao (JIRA)
Jun Rao created KAFKA-3827: -- Summary: log.message.format.version should default to inter.broker.protocol.version Key: KAFKA-3827 URL: https://issues.apache.org/jira/browse/KAFKA-3827 Project: Kafka

[jira] [Comment Edited] (KAFKA-3824) Docs indicate auto.commit breaks at least once delivery but that is incorrect

2016-06-12 Thread kambiz shahri (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326618#comment-15326618 ] kambiz shahri edited comment on KAFKA-3824 at 6/12/16 8:22 PM: -

[jira] [Commented] (KAFKA-3824) Docs indicate auto.commit breaks at least once delivery but that is incorrect

2016-06-12 Thread kambiz shahri (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326618#comment-15326618 ] kambiz shahri commented on KAFKA-3824: -- I read the JavaDoc (and re-read it) and compa

Re: [DISCUSS] KIP-4 Create Topic Schema

2016-06-12 Thread Jay Kreps
Hey Grant, Great to see this progressing. That API looks good to me. Thanks for the thoughtful write-up. One thing that would be great to add to this KIP would be a quick sketch of how the create topic api can be used to get rid of the thing where we create topics when you ask for their metadata.

Re: [jira] [Commented] (KAFKA-3775) Throttle maximum number of tasks assigned to a single KafkaStreams

2016-06-12 Thread Andrew Coates
Good to hear! On the network bandwidth issue... if you're running other processes on the box and what to stop your streaming app from monopolizing the available bandwidth on the box, then I'd suggest looking at some QOS / packet shaping tools to control this outside of Kafka. On Sun, 12 Jun 2016,

[jira] [Closed] (KAFKA-3775) Throttle maximum number of tasks assigned to a single KafkaStreams

2016-06-12 Thread Yuto Kawamura (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuto Kawamura closed KAFKA-3775. > Throttle maximum number of tasks assigned to a single KafkaStreams > -

[jira] [Commented] (KAFKA-3775) Throttle maximum number of tasks assigned to a single KafkaStreams

2016-06-12 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326485#comment-15326485 ] ASF GitHub Bot commented on KAFKA-3775: --- Github user kawamuray closed the pull reque

[jira] [Updated] (KAFKA-3775) Throttle maximum number of tasks assigned to a single KafkaStreams

2016-06-12 Thread Yuto Kawamura (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuto Kawamura updated KAFKA-3775: - Resolution: Won't Fix Status: Resolved (was: Patch Available) > Throttle maximum number o

[jira] [Commented] (KAFKA-3775) Throttle maximum number of tasks assigned to a single KafkaStreams

2016-06-12 Thread Yuto Kawamura (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326484#comment-15326484 ] Yuto Kawamura commented on KAFKA-3775: -- [~guozhang] Yes, both of your short and long

[GitHub] kafka pull request #1460: KAFKA-3775: Throttle maximum number of tasks assig...

2016-06-12 Thread kawamuray
Github user kawamuray closed the pull request at: https://github.com/apache/kafka/pull/1460 --- 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] [Assigned] (KAFKA-3824) Docs indicate auto.commit breaks at least once delivery but that is incorrect

2016-06-12 Thread kambiz shahri (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kambiz shahri reassigned KAFKA-3824: Assignee: kambiz shahri > Docs indicate auto.commit breaks at least once delivery but that

[jira] [Comment Edited] (KAFKA-1452) Killing last replica for partition doesn't change ISR/Leadership if replica is running controller

2016-06-12 Thread Stevo Slavic (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326383#comment-15326383 ] Stevo Slavic edited comment on KAFKA-1452 at 6/12/16 11:32 AM: -

[jira] [Commented] (KAFKA-1452) Killing last replica for partition doesn't change ISR/Leadership if replica is running controller

2016-06-12 Thread Stevo Slavic (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326383#comment-15326383 ] Stevo Slavic commented on KAFKA-1452: - This bug is still present in 0.10.0.0, I reprod

[jira] [Commented] (KAFKA-3408) consumer rebalance fail

2016-06-12 Thread kambiz shahri (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326309#comment-15326309 ] kambiz shahri commented on KAFKA-3408: -- Awesome thanks. :=) > consumer rebalance fai