[jira] [Resolved] (KAFKA-1554) Corrupt index found on clean startup

[ https://issues.apache.org/jira/browse/KAFKA-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat resolved KAFKA-1554. Resolution: Duplicate > Corrupt index found on clean startup > -

[jira] [Commented] (KAFKA-1554) Corrupt index found on clean startup

[ https://issues.apache.org/jira/browse/KAFKA-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958225#comment-14958225 ] Mayuresh Gharat commented on KAFKA-1554: [~wangbo23] thanks for the review. We did

[jira] [Commented] (KAFKA-2017) Persist Coordinator State for Coordinator Failover

[ https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958100#comment-14958100 ] Ashish K Singh commented on KAFKA-2017: --- I agree with [~guozhang] that if we are not

[jira] [Commented] (KAFKA-2515) handle oversized messages properly in new consumer

[ https://issues.apache.org/jira/browse/KAFKA-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958099#comment-14958099 ] Guozhang Wang commented on KAFKA-2515: -- [~junrao] just to clarify, for step 3) above

[jira] [Commented] (KAFKA-2391) Blocking call such as position(), partitionsFor(), committed() and listTopics() should have a timeout

[ https://issues.apache.org/jira/browse/KAFKA-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958089#comment-14958089 ] Onur Karaman commented on KAFKA-2391: - Escalating the priority of this to blocker as t

[jira] [Updated] (KAFKA-2391) Blocking call such as position(), partitionsFor(), committed() and listTopics() should have a timeout

[ https://issues.apache.org/jira/browse/KAFKA-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-2391: Priority: Blocker (was: Major) > Blocking call such as position(), partitionsFor(), committed() and

[jira] [Commented] (KAFKA-2106) Partition balance tool between borkers

[ https://issues.apache.org/jira/browse/KAFKA-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958052#comment-14958052 ] Guozhang Wang commented on KAFKA-2106: -- [~chenshangan...@163.com] I have added you to

[jira] [Updated] (KAFKA-2146) adding partition did not find the correct startIndex

[ https://issues.apache.org/jira/browse/KAFKA-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2146: - Assignee: chenshangan > adding partition did not find the correct startIndex > --

[jira] [Updated] (KAFKA-2106) Partition balance tool between borkers

[ https://issues.apache.org/jira/browse/KAFKA-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2106: - Assignee: chenshangan > Partition balance tool between borkers > -

[jira] [Commented] (KAFKA-2146) adding partition did not find the correct startIndex

[ https://issues.apache.org/jira/browse/KAFKA-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958050#comment-14958050 ] Guozhang Wang commented on KAFKA-2146: -- [~chenshangan...@163.com] your updated patch

[jira] [Commented] (KAFKA-2500) Make logEndOffset available in the 0.8.3 Consumer

[ https://issues.apache.org/jira/browse/KAFKA-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958045#comment-14958045 ] James Cheng commented on KAFKA-2500: Is there any chance this will make it into 0.9.0?

[jira] [Created] (KAFKA-2657) Kafka clients fail to start if one of broker isn't resolved by DNS

Alexander Pakulov created KAFKA-2657: Summary: Kafka clients fail to start if one of broker isn't resolved by DNS Key: KAFKA-2657 URL: https://issues.apache.org/jira/browse/KAFKA-2657 Project: Ka

[jira] [Updated] (KAFKA-2657) Kafka clients fail to start if one of broker isn't resolved by DNS

[ https://issues.apache.org/jira/browse/KAFKA-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Pakulov updated KAFKA-2657: - Description: During org.apache.kafka.clients.producer.KafkaProducer and org.apache.kafka.

[jira] [Updated] (KAFKA-2516) Rename o.a.k.client.tools to o.a.k.tools

[ https://issues.apache.org/jira/browse/KAFKA-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2516: - Reviewer: Gwen Shapira > Rename o.a.k.client.tools to o.a.k.tools > --

[jira] [Commented] (KAFKA-2629) Enable getting SSL password from an executable rather than passing plaintext password

[ https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958025#comment-14958025 ] Ashish K Singh commented on KAFKA-2629: --- [~sriharsha] I am proposing this as an opti

[jira] [Updated] (KAFKA-2441) SSL/TLS in official docs

[ https://issues.apache.org/jira/browse/KAFKA-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2441: - Reviewer: Jun Rao > SSL/TLS in official docs > > > Key: K

[jira] [Updated] (KAFKA-2562) check Kafka scripts for 0.9.0.0

[ https://issues.apache.org/jira/browse/KAFKA-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2562: - Reviewer: Ismael Juma > check Kafka scripts for 0.9.0.0 > --- > >

[jira] [Updated] (KAFKA-2464) Client-side assignment and group generalization

[ https://issues.apache.org/jira/browse/KAFKA-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2464: - Reviewer: Guozhang Wang > Client-side assignment and group generalization > --

[jira] [Updated] (KAFKA-2449) Update mirror maker (MirrorMaker) docs

[ https://issues.apache.org/jira/browse/KAFKA-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2449: - Reviewer: Ismael Juma > Update mirror maker (MirrorMaker) docs > -

[jira] [Updated] (KAFKA-2412) Documentation bug: Add information for key.serializer and value.serializer to New Producer Config sections

[ https://issues.apache.org/jira/browse/KAFKA-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2412: - Reviewer: Gwen Shapira > Documentation bug: Add information for key.serializer and value.serialize

[jira] [Updated] (KAFKA-2417) Ducktape tests for SSL/TLS

[ https://issues.apache.org/jira/browse/KAFKA-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2417: - Reviewer: Jun Rao > Ducktape tests for SSL/TLS > -- > > Ke

[jira] [Updated] (KAFKA-2502) Quotas documentation for 0.8.3

[ https://issues.apache.org/jira/browse/KAFKA-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2502: - Reviewer: Ismael Juma > Quotas documentation for 0.8.3 > -- > >

[jira] [Updated] (KAFKA-2515) handle oversized messages properly in new consumer

[ https://issues.apache.org/jira/browse/KAFKA-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2515: - Reviewer: Jun Rao > handle oversized messages properly in new consumer > -

[jira] [Updated] (KAFKA-2274) Add integration test for consumer coordinator

[ https://issues.apache.org/jira/browse/KAFKA-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2274: - Reviewer: Guozhang Wang > Add integration test for consumer coordinator >

[jira] [Updated] (KAFKA-2452) enable new consumer in mirror maker

[ https://issues.apache.org/jira/browse/KAFKA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2452: - Reviewer: Jason Gustafson > enable new consumer in mirror maker >

[jira] [Updated] (KAFKA-1686) Implement SASL/Kerberos

[ https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-1686: - Reviewer: Jun Rao > Implement SASL/Kerberos > --- > > Key: KAF

[jira] [Updated] (KAFKA-2487) change kafka.examples.Consumer to use the new java consumer

[ https://issues.apache.org/jira/browse/KAFKA-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2487: - Reviewer: Guozhang Wang > change kafka.examples.Consumer to use the new java consumer > --

[jira] [Updated] (KAFKA-2490) support new consumer in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2490: - Reviewer: Guozhang Wang > support new consumer in ConsumerGroupCommand > -

[jira] [Commented] (KAFKA-2629) Enable getting SSL password from an executable rather than passing plaintext password

[ https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958020#comment-14958020 ] Ashish K Singh commented on KAFKA-2629: --- [~gwenshap] sure. We can pick this up once

[jira] [Comment Edited] (KAFKA-2295) Dynamically loaded classes (encoders, etc.) may not be found by Kafka Producer

[ https://issues.apache.org/jira/browse/KAFKA-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958017#comment-14958017 ] Guozhang Wang edited comment on KAFKA-2295 at 10/14/15 11:40 PM: ---

[jira] [Commented] (KAFKA-2295) Dynamically loaded classes (encoders, etc.) may not be found by Kafka Producer

[ https://issues.apache.org/jira/browse/KAFKA-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958017#comment-14958017 ] Guozhang Wang commented on KAFKA-2295: -- [~omkreddy] Could you rebase the patch again?

Re: Slow request log in Kafka

I had some experience with the feature in MySQL. Its main good use is to identify queries that are obviously bad (full scans on OLTP system) and need optimization. You can't infer from it anything about the system as a whole because it lacks context and information about what the rest of the syste

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

See Changes: [cshapi] TRIVIAL: add @throws ConsumerWakeupException in KafkaConsumer -- [...truncated 322 lines...] :kafka-trunk-jdk7:clients:jar UP-TO-DATE :kafka-trunk-jdk7:clients:javadoc UP-TO

Slow request log in Kafka

Hey everyone, We were recently discussing a small logging improvement for Kafka. Basically, add a request log for queries that took longer than a certain configurable time to execute. This can be quite useful for debugging purposes, in fact it would have proven handy while investigating a recent i

[jira] [Updated] (KAFKA-2656) Default SSL keystore and truststore config are unusable

[ https://issues.apache.org/jira/browse/KAFKA-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-2656: -- Status: Patch Available (was: Open) Removed default keystore and truststore for Kafka server an

[GitHub] kafka pull request: KAFKA-2656: Remove hardcoded default key and t...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/312 KAFKA-2656: Remove hardcoded default key and truststores Removed default hardcoded keystore and truststore in /tmp so that default JVM keystore/truststore may be used when keystore/truststore i

[jira] [Commented] (KAFKA-2656) Default SSL keystore and truststore config are unusable

[ https://issues.apache.org/jira/browse/KAFKA-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957933#comment-14957933 ] ASF GitHub Bot commented on KAFKA-2656: --- GitHub user rajinisivaram opened a pull req

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

See Changes: [cshapi] KAFKA-2536: topics tool should allow users to alter topic configuration [cshapi] TRIVIAL: add @throws ConsumerWakeupException in KafkaConsumer -- [...truncated 362 lines...]

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

See Changes: [wangguoz] KAFKA-2603: Add timeout arg to ConsoleConsumer for new consumer [wangguoz] KAFKA-2593: Key value stores can use specified serializers and [cshapi] KAFKA-2650: Change ConfigCommand --deleted-config option to alig

[GitHub] kafka pull request: TRIVIAL: add @throws ConsumerWakeupException i...

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

[GitHub] kafka pull request: TRIVIAL: add @throws ConsumerWakeupException i...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/311 TRIVIAL: add @throws ConsumerWakeupException in KafkaConsumer You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka wakeupComme

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

See Changes: [wangguoz] KAFKA-2593: Key value stores can use specified serializers and [cshapi] KAFKA-2650: Change ConfigCommand --deleted-config option to align wit… [cshapi] KAFKA-2536: topics tool should allow users to alter top

Re: [DISCUSS] KIP-36 - Rack aware replica assignment

Can you clarify the workflow for the following scenarios: 1. I currently have 6 brokers and want to add rack information for each 2. I'm adding a new broker and I want to specify which rack it belongs on while adding it. Thanks! On Tue, Oct 13, 2015 at 2:21 PM, Allen Wang wrote: > We discussed

[jira] [Created] (KAFKA-2656) Default SSL keystore and truststore config are unusable

Rajini Sivaram created KAFKA-2656: - Summary: Default SSL keystore and truststore config are unusable Key: KAFKA-2656 URL: https://issues.apache.org/jira/browse/KAFKA-2656 Project: Kafka Issue

[jira] [Commented] (KAFKA-2655) Consumer.poll(0)'s overhead too large

[ https://issues.apache.org/jira/browse/KAFKA-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957824#comment-14957824 ] Ismael Juma commented on KAFKA-2655: It would be good to get some actual numbers befor

[jira] [Comment Edited] (KAFKA-2655) Consumer.poll(0)'s overhead too large

[ https://issues.apache.org/jira/browse/KAFKA-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957824#comment-14957824 ] Ismael Juma edited comment on KAFKA-2655 at 10/14/15 9:30 PM: --

[jira] [Commented] (KAFKA-2536) topics tool should allow users to alter topic configuration

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

[jira] [Updated] (KAFKA-2536) topics tool should allow users to alter topic configuration

[ https://issues.apache.org/jira/browse/KAFKA-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2536: Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 30

[GitHub] kafka pull request: KAFKA-2536: topics tool should allow users to ...

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

[jira] [Commented] (KAFKA-2629) Enable getting SSL password from an executable rather than passing plaintext password

[ https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957801#comment-14957801 ] Sriharsha Chintalapani commented on KAFKA-2629: --- [~singhashish] I still dis

[jira] [Commented] (KAFKA-2397) leave group request

[ https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957784#comment-14957784 ] Onur Karaman commented on KAFKA-2397: - Cool. It sounds like we all generally agree on

[jira] [Created] (KAFKA-2655) Consumer.poll(0)'s overhead too large

Guozhang Wang created KAFKA-2655: Summary: Consumer.poll(0)'s overhead too large Key: KAFKA-2655 URL: https://issues.apache.org/jira/browse/KAFKA-2655 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-2654) Avoid calling Consumer.poll(0) in each iteration

Guozhang Wang created KAFKA-2654: Summary: Avoid calling Consumer.poll(0) in each iteration Key: KAFKA-2654 URL: https://issues.apache.org/jira/browse/KAFKA-2654 Project: Kafka Issue Type: Su

[jira] [Commented] (KAFKA-2516) Rename o.a.k.client.tools to o.a.k.tools

[ https://issues.apache.org/jira/browse/KAFKA-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957773#comment-14957773 ] ASF GitHub Bot commented on KAFKA-2516: --- Github user granthenke closed the pull requ

[jira] [Commented] (KAFKA-2516) Rename o.a.k.client.tools to o.a.k.tools

[ https://issues.apache.org/jira/browse/KAFKA-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957774#comment-14957774 ] ASF GitHub Bot commented on KAFKA-2516: --- GitHub user granthenke reopened a pull requ

[GitHub] kafka pull request: KAFKA-2516: Rename o.a.k.client.tools to o.a.k...

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

[GitHub] kafka pull request: KAFKA-2516: Rename o.a.k.client.tools to o.a.k...

GitHub user granthenke reopened a pull request: https://github.com/apache/kafka/pull/310 KAFKA-2516: Rename o.a.k.client.tools to o.a.k.tools You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka tools-packaging Alter

[jira] [Created] (KAFKA-2653) Stateful operations in the KStream DSL layer

Guozhang Wang created KAFKA-2653: Summary: Stateful operations in the KStream DSL layer Key: KAFKA-2653 URL: https://issues.apache.org/jira/browse/KAFKA-2653 Project: Kafka Issue Type: Sub-ta

[jira] [Created] (KAFKA-2652) Incorporate the new consumer protocol with partition-group interface

Guozhang Wang created KAFKA-2652: Summary: Incorporate the new consumer protocol with partition-group interface Key: KAFKA-2652 URL: https://issues.apache.org/jira/browse/KAFKA-2652 Project: Kafka

[jira] [Commented] (KAFKA-2650) Change ConfigCommand --deleted-config option to align with TopicCommand

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

[jira] [Updated] (KAFKA-2650) Change ConfigCommand --deleted-config option to align with TopicCommand

[ https://issues.apache.org/jira/browse/KAFKA-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2650: Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 30

[GitHub] kafka pull request: KAFKA-2650: Change ConfigCommand --deleted-con...

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

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

See Changes: [wangguoz] KAFKA-2603: Add timeout arg to ConsoleConsumer for new consumer -- [...truncated 1825 lines...] kafka.coordinator.ConsumerGroupMetadataTest > testPreparingRebalanceToPre

[jira] [Updated] (KAFKA-2590) Kafka Streams Checklist

[ https://issues.apache.org/jira/browse/KAFKA-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2590: - Issue Type: New Feature (was: Task) > Kafka Streams Checklist > --- > >

[jira] [Commented] (KAFKA-2593) KeyValueStores should not require use of the context's default serializers and deserializers

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

[GitHub] kafka pull request: KAFKA-2593 Key value stores can use specified ...

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

[jira] [Updated] (KAFKA-2593) KeyValueStores should not require use of the context's default serializers and deserializers

[ https://issues.apache.org/jira/browse/KAFKA-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2593: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

Re: Kafka Monitoring Framework

Lin: Yes, I think so. On Wed, Oct 14, 2015 at 1:48 PM, Lin Ma wrote: > Thanks Dong. Then I bet it will take a while before its release. > > Lin > > > -Original Message- > From: Dong Lin [mailto:lindon...@gmail.com] > Sent: Tuesday, October 13, 2015 11:21 PM > To: dev@kafka.apache.org >

[jira] [Commented] (KAFKA-2629) Enable getting SSL password from an executable rather than passing plaintext password

[ https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957726#comment-14957726 ] Gwen Shapira commented on KAFKA-2629: - [~singhashish], I see the need for this type of

RE: Kafka Monitoring Framework

Thanks Dong. Then I bet it will take a while before its release. Lin -Original Message- From: Dong Lin [mailto:lindon...@gmail.com] Sent: Tuesday, October 13, 2015 11:21 PM To: dev@kafka.apache.org Subject: Re: Kafka Monitoring Framework Hey Lin, Thanks for your interest. As Kartik m

[jira] [Commented] (KAFKA-2397) leave group request

[ https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957718#comment-14957718 ] Guozhang Wang commented on KAFKA-2397: -- For consumer shutdown, in the ZK-based consum

[jira] [Commented] (KAFKA-2603) Add timeout to ConsoleConsumer running with new consumer

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

[jira] [Updated] (KAFKA-2603) Add timeout to ConsoleConsumer running with new consumer

[ https://issues.apache.org/jira/browse/KAFKA-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2603: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

[GitHub] kafka pull request: KAFKA-2603: Add timeout arg to ConsoleConsumer...

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

Re: KIP-28 does not allow Processor to specify partition of output message

>The bottom line is that *different* topics will likely need to be partitioned differently. You can do it with the existing Partitioner interface. Centralizing the logic doesn't mean all topics must use the same partitioning scheme. On Wed, Oct 14, 2015 at 1:03 PM, Randall Hauch wrote: > It ab

Re: KIP-28 does not allow Processor to specify partition of output message

I think part of Yasu's motivation for cross-cluster partitioning is that, for example, there could be multiple stream jobs reading / writing to some shared topics but controlled by different teams or services inside an organization, and if one team mistakenly specifying the partitioning in a wrong

[jira] [Commented] (KAFKA-2017) Persist Coordinator State for Coordinator Failover

[ https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957665#comment-14957665 ] Guozhang Wang commented on KAFKA-2017: -- Here is my two cents comparing those two appr

[jira] [Commented] (KAFKA-2477) Replicas spuriously deleting all segments in partition

[ https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957645#comment-14957645 ] Chinmay Soman commented on KAFKA-2477: -- [~ewencp] Totally agree. Its just that the cu

Re: KIP-28 does not allow Processor to specify partition of output message

It absolutely is important that the partitioning logic for a single topic be the same across an entire cluster. IOW, if a topology has a single sink, then no matter where that topology is run in the cluster, it had better use the same partitioning logic. I would argue that when the partitioning

Re: KIP-28 does not allow Processor to specify partition of output message

I agree that cluster-wide partitioning would be preferable in cases where multiple producers from different services sharing the same topics, and this may well be resolved by the same manner like the schema registry service. On the other hand, I think this is not a problem that would be solved at t

[jira] [Commented] (KAFKA-2629) Enable getting SSL password from an executable rather than passing plaintext password

[ https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957626#comment-14957626 ] Ashish K Singh commented on KAFKA-2629: --- [~junrao] [~gwenshap] what do you guys thin

Re: [DISCUSS] KIP-37 - Add namespaces in Kafka

Hey Jason, I actually think this is one of the advantages. The problem we have today is that you can't really do bidirectional replication between clusters because it would actually be a feedback loop. So the intended use would be that you would have a structure where the top-level directory was

[jira] [Commented] (KAFKA-2017) Persist Coordinator State for Coordinator Failover

[ https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957570#comment-14957570 ] Jason Gustafson commented on KAFKA-2017: One additional point worth considering is

[jira] [Commented] (KAFKA-2397) leave group request

[ https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957550#comment-14957550 ] Jay Kreps commented on KAFKA-2397: -- Dunno if we closed the loop on the approach. [~onurk

[jira] [Commented] (KAFKA-1436) Idempotent Producer / Duplicate Detection

[ https://issues.apache.org/jira/browse/KAFKA-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957497#comment-14957497 ] Manish commented on KAFKA-1436: --- Hi Neha, Is there an ETA for getting this issue fixed? Th

Re: [DISCUSS] KIP-37 - Add namespaces in Kafka

Hey Ashish, thanks for the write-up. I think having a namespace capability is a useful feature for Kafka, in particular with the addition of the authorization layer. I probably prefer Jay's hierarchical approach if we're going to embed the namespace in the topic name since it seems more general. Th

Re: KIP-28 does not allow Processor to specify partition of output message

A partitioning scheme should be a cluster wide thing. Letting each sink have a different partitioning scheme does not make sense to me. A partitioning scheme is not specific to a stream job, each task or a sink. I think specifying it at sink level is more error prone. If a user wants to customize

[jira] [Commented] (KAFKA-2017) Persist Coordinator State for Coordinator Failover

[ https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957348#comment-14957348 ] Joel Koshy commented on KAFKA-2017: --- If we reused this topic, then I think we could end

[jira] [Commented] (KAFKA-2017) Persist Coordinator State for Coordinator Failover

[ https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957330#comment-14957330 ] Guozhang Wang commented on KAFKA-2017: -- I am not sure if we want to piggy-back the me

[jira] [Commented] (KAFKA-2017) Persist Coordinator State for Coordinator Failover

[ https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957268#comment-14957268 ] Jason Gustafson commented on KAFKA-2017: I think persistence in Kafka is a promisi

[jira] [Commented] (KAFKA-2516) Rename o.a.k.client.tools to o.a.k.tools

[ https://issues.apache.org/jira/browse/KAFKA-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957253#comment-14957253 ] ASF GitHub Bot commented on KAFKA-2516: --- GitHub user granthenke opened a pull reques

[jira] [Assigned] (KAFKA-2516) Rename o.a.k.client.tools to o.a.k.tools

[ https://issues.apache.org/jira/browse/KAFKA-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-2516: -- Assignee: Grant Henke > Rename o.a.k.client.tools to o.a.k.tools >

[jira] [Updated] (KAFKA-2516) Rename o.a.k.client.tools to o.a.k.tools

[ https://issues.apache.org/jira/browse/KAFKA-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-2516: --- Status: Patch Available (was: Open) > Rename o.a.k.client.tools to o.a.k.tools >

[GitHub] kafka pull request: KAFKA-2516: Rename o.a.k.client.tools to o.a.k...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/310 KAFKA-2516: Rename o.a.k.client.tools to o.a.k.tools You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka tools-packaging Alterna

[jira] [Commented] (KAFKA-2017) Persist Coordinator State for Coordinator Failover

[ https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957204#comment-14957204 ] Joel Koshy commented on KAFKA-2017: --- I agree with those benefits. If we go that route th

[jira] [Updated] (KAFKA-2649) Add support for custom partitioner in sink nodes

[ https://issues.apache.org/jira/browse/KAFKA-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-2649: - Status: Patch Available (was: Open) > Add support for custom partitioner in sink nodes >

Re: KIP-28 does not allow Processor to specify partition of output message

Created https://issues.apache.org/jira/browse/KAFKA-2649 and attached a PR with the proposed change. Thanks! On October 14, 2015 at 3:12:34 AM, Guozhang Wang (wangg...@gmail.com) wrote: Thanks! On Tue, Oct 13, 2015 at 9:34 PM, Randall Hauch wrote: Ok, cool. I agree we want something simple. 

[jira] [Commented] (KAFKA-2649) Add support for custom partitioner in sink nodes

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

[GitHub] kafka pull request: KAFKA-2649 Add support for custom partitioning...

GitHub user rhauch opened a pull request: https://github.com/apache/kafka/pull/309 KAFKA-2649 Add support for custom partitioning in topology sinks Added option to use custom partitioning logic within each topology sink. You can merge this pull request into a Git repository by runni

[jira] [Updated] (KAFKA-2650) Change ConfigCommand --deleted-config option to align with TopicCommand

[ https://issues.apache.org/jira/browse/KAFKA-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-2650: --- Status: Patch Available (was: Open) > Change ConfigCommand --deleted-config option to align with Topi

  1   2   >