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

Looking at "existing solutions", it looks like Zookeeper allows plugging in any SASL mechanism, but the server will only support one mechanism at a time. If this is good enough for our use-case (do we actually need to support multiple mechanisms at once?), it will simplify life a lot for us (

[jira] [Updated] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajiv Kurian updated KAFKA-3159: Attachment: Screen Shot 2016-02-01 at 11.09.32 AM.png CPU break down of the patched client. Some

[jira] [Work started] (KAFKA-2673) Log JmxTool output to logger

[ https://issues.apache.org/jira/browse/KAFKA-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-2673 started by chen zhu. --- > Log JmxTool output to logger > > > Key:

[jira] [Updated] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajiv Kurian updated KAFKA-3159: Attachment: Memory-profile-patched-client.png Memory profile of the patched client. Notes: 1.A lot

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126877#comment-15126877 ] Rajiv Kurian commented on KAFKA-3159: - [~hachikuji] I tried your patch. The Exceptions are now gone,

[jira] [Commented] (KAFKA-3172) Consumer threads stay in 'Watiting' status and are blocked at consumer poll method

[ https://issues.apache.org/jira/browse/KAFKA-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126875#comment-15126875 ] Gwen Shapira commented on KAFKA-3172: - Your description says "consumer" but your jstack dump says

[VOTE] KIP-42: Add Producer and Consumer Interceptors

Hi All, I am opening the voting thread for KIP-42: Add Producer and Consumer Interceptors. For reference, here's the KIP wiki: https://cwiki.apache.org/confluence/display/KAFKA/KIP-42%3A+Add+Producer+and+Consumer+Interceptors And the mailing list threads: January:

[VOTE] KIP-42 -- Add Producer and Consumer Interceptors.

Hi All, I am opening the voting thread for KIP-42: Add Producer and Consumer Interceptors. For reference, here's the KIP wiki: https://cwiki.apache.org/confluence/display/KAFKA/KIP-42%3A+Add+Producer+and+Consumer+Interceptors And the mailing list threads: January:

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126959#comment-15126959 ] Jiangjie Qin commented on KAFKA-3174: - [~ijuma] My test code was as below. Initially I only tested 1MB

Re: [VOTE] KIP-42 -- Add Producer and Consumer Interceptors.

+1 (non-binding). Nice wiki. Thanks Anna. On Mon, Feb 1, 2016 at 12:00 PM, Anna Povzner wrote: > Hi All, > > I am opening the voting thread for KIP-42: Add Producer and Consumer > Interceptors. > > For reference, here's the KIP wiki: > >

[GitHub] kafka pull request: MINOR: some javadocs for kstream public api

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/844 MINOR: some javadocs for kstream public api @guozhangwang You can merge this pull request into a Git repository by running: $ git pull https://github.com/ymatsuda/kafka javadoc

[jira] [Commented] (KAFKA-3175) topic not accessible after deletion even when delete.topic.enable is disabled

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

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127127#comment-15127127 ] Ismael Juma commented on KAFKA-3174: Unfortunately, the micro-benchmark above is not reliable. That's

Re: [VOTE] KIP-42 -- Add Producer and Consumer Interceptors.

+1 -Jay On Mon, Feb 1, 2016 at 12:00 PM, Anna Povzner wrote: > Hi All, > > I am opening the voting thread for KIP-42: Add Producer and Consumer > Interceptors. > > For reference, here's the KIP wiki: > >

[jira] [Created] (KAFKA-3184) Add Checkpoint for In-memory State Store

Guozhang Wang created KAFKA-3184: Summary: Add Checkpoint for In-memory State Store Key: KAFKA-3184 URL: https://issues.apache.org/jira/browse/KAFKA-3184 Project: Kafka Issue Type: Sub-task

[jira] [Commented] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127201#comment-15127201 ] Guozhang Wang commented on KAFKA-3177: -- [~hachikuji] Just checking, this infinite loop's pattern is

[jira] [Commented] (KAFKA-3186) Kafka authorizer should be aware of principal types it supports.

[ https://issues.apache.org/jira/browse/KAFKA-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127213#comment-15127213 ] Ashish K Singh commented on KAFKA-3186: --- [~gwenshap] [~ijuma] I would like to know your thoughts on

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

See Changes: [wangguoz] MINOR: removed obsolete class [wangguoz] KAFKA-1860: Fix issue that file system errors are not detected unless -- [...truncated 6827 lines...]

[GitHub] kafka pull request: MINOR: removed obsolete class

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

[GitHub] kafka pull request: MINOR: Improve error message for inconsistent ...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/847 MINOR: Improve error message for inconsistent broker ids Provides a more actionable and descriptive error message. You can merge this pull request into a Git repository by running: $ git

[jira] [Work started] (KAFKA-3175) topic not accessible after deletion even when delete.topic.enable is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3175 started by Mayuresh Gharat. -- > topic not accessible after deletion even when delete.topic.enable is

[jira] [Updated] (KAFKA-3175) topic not accessible after deletion even when delete.topic.enable is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-3175: --- Status: Patch Available (was: In Progress) > topic not accessible after deletion even when

[GitHub] kafka pull request: KAFKA-3175 : Topic not accessible after deleti...

GitHub user MayureshGharat opened a pull request: https://github.com/apache/kafka/pull/846 KAFKA-3175 : Topic not accessible after deletion even when delete.topic.enable is disabled Remove topics under /admin/delete_topics path in zk if deleteTopic is disabled. The topic should

[jira] [Commented] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127255#comment-15127255 ] Jiangjie Qin commented on KAFKA-3177: - [~guozhang] In this particular case, the issue is different

[jira] [Created] (KAFKA-3183) Add metrics for persistent store caching layer

Guozhang Wang created KAFKA-3183: Summary: Add metrics for persistent store caching layer Key: KAFKA-3183 URL: https://issues.apache.org/jira/browse/KAFKA-3183 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-3185) Allow users to cleanup internal data

Guozhang Wang created KAFKA-3185: Summary: Allow users to cleanup internal data Key: KAFKA-3185 URL: https://issues.apache.org/jira/browse/KAFKA-3185 Project: Kafka Issue Type: Sub-task

[jira] [Updated] (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:all-tabpanel ] Guozhang Wang updated KAFKA-1860: - Resolution: Fixed Status: Resolved (was: Patch Available) > File system errors are not

[jira] [Created] (KAFKA-3187) Make kafka-acls.sh help messages more generic.

Ashish K Singh created KAFKA-3187: - Summary: Make kafka-acls.sh help messages more generic. Key: KAFKA-3187 URL: https://issues.apache.org/jira/browse/KAFKA-3187 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-3186) Kafka authorizer should be aware of principal types it supports.

Ashish K Singh created KAFKA-3186: - Summary: Kafka authorizer should be aware of principal types it supports. Key: KAFKA-3186 URL: https://issues.apache.org/jira/browse/KAFKA-3186 Project: Kafka

[GitHub] kafka pull request: MINOR: Reorder StreamThread shutdown sequence

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/845 MINOR: Reorder StreamThread shutdown sequence We need to close producer first before closing tasks to make sure all messages are acked and hence checkpoint offsets are updated before closing

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

On Mon, Feb 1, 2016 at 7:04 PM, Gwen Shapira wrote: > Looking at "existing solutions", it looks like Zookeeper allows plugging in > any SASL mechanism, but the server will only support one mechanism at a > time. > This was the original proposal from Rajini as that is enough

Re: [VOTE] KIP-42 -- Add Producer and Consumer Interceptors.

+1 (non-binding) Ismael On Mon, Feb 1, 2016 at 10:23 PM, Jay Kreps wrote: > +1 > > -Jay > > On Mon, Feb 1, 2016 at 12:00 PM, Anna Povzner wrote: > > > Hi All, > > > > I am opening the voting thread for KIP-42: Add Producer and Consumer > > Interceptors. >

[jira] [Assigned] (KAFKA-3097) Acls for PrincipalType User are case sensitive

[ https://issues.apache.org/jira/browse/KAFKA-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh reassigned KAFKA-3097: - Assignee: Ashish K Singh > Acls for PrincipalType User are case sensitive >

[GitHub] kafka pull request: KAFKA-1860 File system errors are not detected...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/698 --- 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-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=15127177#comment-15127177 ] ASF GitHub Bot commented on KAFKA-1860: --- Github user asfgit closed the pull request at:

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

See Changes: [wangguoz] MINOR: removed obsolete class [wangguoz] KAFKA-1860: Fix issue that file system errors are not detected unless -- Started by an SCM change [EnvInject] - Loading node

Re: [VOTE] KIP-42 -- Add Producer and Consumer Interceptors.

+1 On Mon, Feb 1, 2016 at 2:39 PM, Ismael Juma wrote: > +1 (non-binding) > > Ismael > > On Mon, Feb 1, 2016 at 10:23 PM, Jay Kreps wrote: > > > +1 > > > > -Jay > > > > On Mon, Feb 1, 2016 at 12:00 PM, Anna Povzner wrote: > > > > > Hi

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

See Changes: [me] MINOR: Reorder StreamThread shutdown sequence -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-2 (docker Ubuntu ubuntu

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

See Changes: [me] KAFKA-3060: Refactor MeteredStore and RockDBStore Impl -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H11 (docker Ubuntu

[jira] [Created] (KAFKA-3188) Add integration test for KIP-31 and KIP-32

Jiangjie Qin created KAFKA-3188: --- Summary: Add integration test for KIP-31 and KIP-32 Key: KAFKA-3188 URL: https://issues.apache.org/jira/browse/KAFKA-3188 Project: Kafka Issue Type: Sub-task

[jira] [Commented] (KAFKA-3189) Kafka server always return UnknownServerException.

[ https://issues.apache.org/jira/browse/KAFKA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127475#comment-15127475 ] Jiangjie Qin commented on KAFKA-3189: - [~junrao] Would like to see if you have any concern on moving

[jira] [Updated] (KAFKA-3060) Refactor MeteredXXStore

[ https://issues.apache.org/jira/browse/KAFKA-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3060: - Assignee: Guozhang Wang > Refactor MeteredXXStore > --- > >

[jira] [Commented] (KAFKA-3060) Refactor MeteredXXStore

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

[jira] [Resolved] (KAFKA-3060) Refactor MeteredXXStore

[ https://issues.apache.org/jira/browse/KAFKA-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3060. -- Resolution: Fixed Fix Version/s: 0.9.1.0 Issue resolved by pull request

[GitHub] kafka pull request: KAFKA-3060: Refactor MeteredStore and RockDBSt...

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

[GitHub] kafka pull request: MINOR: Reorder StreamThread shutdown sequence

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

Jenkins build is back to normal : kafka-trunk-jdk7 #1007

See

[jira] [Created] (KAFKA-3189) Kafka server always return UnknownServerException.

Jiangjie Qin created KAFKA-3189: --- Summary: Kafka server always return UnknownServerException. Key: KAFKA-3189 URL: https://issues.apache.org/jira/browse/KAFKA-3189 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-3189) Kafka server always return UnknownServerException.

[ https://issues.apache.org/jira/browse/KAFKA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3189: Fix Version/s: 0.9.0.1 Component/s: core > Kafka server always return UnknownServerException.

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

Gwen, Yes, we should consider the support for different SASL mechanisms via separate ports. At the moment, this is included under "*Rejected alternatives*". It was slightly lost in the text, so I have updated it. It will be worth exploring this further. The KIP considers three requirements:

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

Hi Gwen, On Mon, Feb 1, 2016 at 6:06 AM, Gwen Shapira wrote: > Could we support separate SASL mechanisms via separate ports? > This option was also discussed in the KIP and there are some advantages as you say. However, there are some drawbacks as well. This was the main

[jira] [Comment Edited] (KAFKA-2607) Review `Time` interface and its usage

[ https://issues.apache.org/jira/browse/KAFKA-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14941066#comment-14941066 ] Ismael Juma edited comment on KAFKA-2607 at 2/1/16 10:11 AM: - We should

[jira] [Commented] (KAFKA-3086) unused handle method in MirrorMakerMessageHandler

[ https://issues.apache.org/jira/browse/KAFKA-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15125984#comment-15125984 ] Ismael Juma commented on KAFKA-3086: [~gwenshap], you said the following in the PR when I asked the

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

Hi Gwen, A few comments below. On Mon, Feb 1, 2016 at 4:30 PM, Gwen Shapira wrote: > Thanks for clarifying, Ismael and Rajini. And I'm sorry for reopenning a > point that was clearly discussed already. Your input is definitely welcome. :) There was an initial discussion in

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

Thanks for clarifying, Ismael and Rajini. And I'm sorry for reopenning a point that was clearly discussed already. I wouldn't be doing this if I didn't think my concerns are important and that the administrative aspect may have been ignored (or de-prioritize). In my view, we should prioritize

[jira] [Updated] (KAFKA-3181) Check occurrences of Runtime.halt() in the codebase and try to handle it at a single place

[ https://issues.apache.org/jira/browse/KAFKA-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-3181: --- Description: Currently runtime.halt() is called at multiple places in the code. In an ideal

[jira] [Commented] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126609#comment-15126609 ] Jason Gustafson commented on KAFKA-3177: [~becket_qin] Nice find. Your suggestion seems reasonable

[jira] [Assigned] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-3177: --- Assignee: Jiangjie Qin > Kafka consumer can hang when position() is called on a non-existing

[jira] [Work started] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3177 started by Jiangjie Qin. --- > Kafka consumer can hang when position() is called on a non-existing partition. >

[jira] [Created] (KAFKA-3180) issue for extracting JSON from https web page

swayam created KAFKA-3180: - Summary: issue for extracting JSON from https web page Key: KAFKA-3180 URL: https://issues.apache.org/jira/browse/KAFKA-3180 Project: Kafka Issue Type: Test

Re: Pluggable Log Compaction Policy

Hi Bill, The PR is still under review. It might take some more time because it touches a bunch of files. You can watch KAFKA-3025 so once it gets closed you will get email notification. Looking forward to your tool. Thanks, Jiangjie (Becket) Qin On Mon, Feb 1, 2016 at 6:54 AM, Bill Warshaw

[jira] [Updated] (KAFKA-3189) Kafka server always return UnknownServerException.

[ https://issues.apache.org/jira/browse/KAFKA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3189: --- Fix Version/s: (was: 0.9.0.1) 0.9.1.0 > Kafka server always return

[GitHub] kafka pull request: 0.9.0

GitHub user quanrs opened a pull request: https://github.com/apache/kafka/pull/848 0.9.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/kafka 0.9.0 Alternatively you can review and apply these changes as the patch at:

[jira] [Created] (KAFKA-3191) Improve offset committing JavaDoc in KafkaConsumer

Adam Kunicki created KAFKA-3191: --- Summary: Improve offset committing JavaDoc in KafkaConsumer Key: KAFKA-3191 URL: https://issues.apache.org/jira/browse/KAFKA-3191 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-3189) Kafka server always return UnknownServerException.

[ https://issues.apache.org/jira/browse/KAFKA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127813#comment-15127813 ] Ismael Juma commented on KAFKA-3189: Changed the fix version to 0.9.1.0 as it doesn't affect the 0.9.0

[jira] [Commented] (KAFKA-1696) Kafka should be able to generate Hadoop delegation tokens

[ https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127639#comment-15127639 ] Gwen Shapira commented on KAFKA-1696: - [~harsha_ch], you are following [~rsivaram]'s KIP on new SASL

[jira] [Commented] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127701#comment-15127701 ] Dana Powers commented on KAFKA-3177: A similar infinite loop happens when the partition exists but has

[jira] [Created] (KAFKA-3190) KafkaProducer should not invoke callback in send()

Jiangjie Qin created KAFKA-3190: --- Summary: KafkaProducer should not invoke callback in send() Key: KAFKA-3190 URL: https://issues.apache.org/jira/browse/KAFKA-3190 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-3186) Kafka authorizer should be aware of principal types it supports.

[ https://issues.apache.org/jira/browse/KAFKA-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127632#comment-15127632 ] Gwen Shapira commented on KAFKA-3186: - I assume you are referring to the fact that Sentry also manages

Re: [VOTE] KIP-42 -- Add Producer and Consumer Interceptors.

+1 -Ewen On Mon, Feb 1, 2016 at 8:06 PM, Gwen Shapira wrote: > +1 > > And seconding Becket, the wiki is great - comprehensive and readable. > > On Mon, Feb 1, 2016 at 12:00 PM, Anna Povzner wrote: > > > Hi All, > > > > I am opening the voting thread for

Re: [VOTE] KIP-42 -- Add Producer and Consumer Interceptors.

+1 And seconding Becket, the wiki is great - comprehensive and readable. On Mon, Feb 1, 2016 at 12:00 PM, Anna Povzner wrote: > Hi All, > > I am opening the voting thread for KIP-42: Add Producer and Consumer > Interceptors. > > For reference, here's the KIP wiki: > >

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

I am the author of KIP-44. I hope my use case will add some values to this discussion. The reason I raised KIP44 is that I want to be able to implement a custom security protocol that can fulfill the need of my company. As pointed out by Ismael KIP-43 now supports a pluggable way to inject custom

[GitHub] kafka pull request: MINOR: removed obsolete class

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/843 MINOR: removed obsolete class @guozhangwang You can merge this pull request into a Git repository by running: $ git pull https://github.com/ymatsuda/kafka remove_unused Alternatively you can

Re: Pluggable Log Compaction Policy

Becket, I took a look at KIP-32 and your PR for it. This looks like something that would be great to build off of; I'm envisioning a timestamp-based policy where the client application sets a minimum timestamp, before which everything can be deleted / compacted. How far along is this pull

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126292#comment-15126292 ] Todd Palino commented on KAFKA-3174: Yeah, definitely no problems with Java 1.8. We've been running

[jira] [Updated] (KAFKA-3175) topic not accessible after deletion even when delete.topic.enable is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3175: --- Fix Version/s: 0.9.0.1 > topic not accessible after deletion even when delete.topic.enable is

[jira] [Commented] (KAFKA-3175) topic not accessible after deletion even when delete.topic.enable is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126407#comment-15126407 ] Jun Rao commented on KAFKA-3175: Also, another thing is that if topic deletion is not enabled, the

[jira] [Updated] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3159: --- Fix Version/s: 0.9.0.1 > Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain >

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126346#comment-15126346 ] Ismael Juma commented on KAFKA-3174: [~becket_qin] We have started recommending Java 8 around the same

[jira] [Comment Edited] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126346#comment-15126346 ] Ismael Juma edited comment on KAFKA-3174 at 2/1/16 3:02 PM: [~becket_qin] We

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126349#comment-15126349 ] Ismael Juma commented on KAFKA-3174: [~toddpalino], let us know when you switch to u40 so that we

[jira] [Commented] (KAFKA-3086) unused handle method in MirrorMakerMessageHandler

[ https://issues.apache.org/jira/browse/KAFKA-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126438#comment-15126438 ] Gwen Shapira commented on KAFKA-3086: - Ick. Sorry for the confusion and inconsistency. All good then

[jira] [Commented] (KAFKA-3175) topic not accessible after deletion even when delete.topic.enable is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126711#comment-15126711 ] Mayuresh Gharat commented on KAFKA-3175: I am thinking that once we detect that the delete topic

[jira] [Created] (KAFKA-3182) Failure in kafka.network.SocketServerTest.testSocketsCloseOnShutdown

Guozhang Wang created KAFKA-3182: Summary: Failure in kafka.network.SocketServerTest.testSocketsCloseOnShutdown Key: KAFKA-3182 URL: https://issues.apache.org/jira/browse/KAFKA-3182 Project: Kafka

[jira] [Created] (KAFKA-3181) Check occurrences of Runtime.halt() in the codebase and try to handle it at a single place

Mayuresh Gharat created KAFKA-3181: -- Summary: Check occurrences of Runtime.halt() in the codebase and try to handle it at a single place Key: KAFKA-3181 URL: https://issues.apache.org/jira/browse/KAFKA-3181

[jira] [Commented] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126619#comment-15126619 ] Jiangjie Qin commented on KAFKA-3177: - Thanks [~hachikuji], I'll submit patch for the ticket then. >