[jira] [Commented] (KAFKA-2875) Class path contains multiple SLF4J bindings warnings when using scripts under bin

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

[jira] [Commented] (KAFKA-2875) Class path contains multiple SLF4J bindings warnings when using scripts under bin

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

[GitHub] kafka pull request: KAFKA-2875: remove slf4j multi binding warning...

GitHub user ZoneMayor reopened a pull request: https://github.com/apache/kafka/pull/693 KAFKA-2875: remove slf4j multi binding warnings when running form source distribution hi @ijuma I reopened this pr again (sorry for my inexperience using github); I think I did much

[GitHub] kafka pull request: KAFKA-2875: remove slf4j multi binding warning...

Github user ZoneMayor closed the pull request at: https://github.com/apache/kafka/pull/693 --- 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: KAFKA-3197 Fix producer sending records out of...

GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/857 KAFKA-3197 Fix producer sending records out of order This patch adds a new configuration to the producer to enforce the maximum in flight batch for each partition. The patch itself is small, but

[jira] [Updated] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

[ https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3197: Status: Patch Available (was: Open) > Producer can send message out of order even when in flight

[jira] [Commented] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

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

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

Rajini, I looked at the PR you have. I think its better with your earlier approach rather than extending the protocol. What I was thinking initially is, Broker has a config option of say sasl.mechanism = GSSAPI, PLAIN and the client can have similar config of

[jira] [Commented] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

[ https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130306#comment-15130306 ] Eno Thereska commented on KAFKA-3197: - [~becket_qin]: I don't think the documentation for

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

A slightly different approach for supporting different SASL mechanisms within a broker is to allow the same "*security protocol*" to be used on different ports with different configuration options. An advantage of this approach is that it extends the configurability of not just SASL, but any

[jira] [Commented] (KAFKA-3200) MessageSet from broker seems invalid

[ https://issues.apache.org/jira/browse/KAFKA-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131148#comment-15131148 ] Rajiv Kurian commented on KAFKA-3200: - Yeah I have a similar workaround but this seems unfortunate. >

[jira] [Commented] (KAFKA-3200) MessageSet from broker seems invalid

[ https://issues.apache.org/jira/browse/KAFKA-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131120#comment-15131120 ] Grant Henke commented on KAFKA-3200: There is a relevant discussion in the mailing list here:

[jira] [Commented] (KAFKA-3200) MessageSet from broker seems invalid

[ https://issues.apache.org/jira/browse/KAFKA-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131142#comment-15131142 ] Dana Powers commented on KAFKA-3200: the minimum Message payload size is 26 bytes (8 offset, 4 size,

[jira] [Commented] (KAFKA-3200) MessageSet from broker seems invalid

[ https://issues.apache.org/jira/browse/KAFKA-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131150#comment-15131150 ] Rajiv Kurian commented on KAFKA-3200: - Not attaching code any more since this seems known. Glad I am

[jira] [Created] (KAFKA-3200) MessageSet from broker seems invalid

Rajiv Kurian created KAFKA-3200: --- Summary: MessageSet from broker seems invalid Key: KAFKA-3200 URL: https://issues.apache.org/jira/browse/KAFKA-3200 Project: Kafka Issue Type: Bug Affects

[jira] [Commented] (KAFKA-3200) MessageSet from broker seems invalid

[ https://issues.apache.org/jira/browse/KAFKA-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131155#comment-15131155 ] Rajiv Kurian commented on KAFKA-3200: - Got it. Yeah it would be ideal to not have this problem. Also

[jira] [Commented] (KAFKA-3194) Validate security.inter.broker.protocol against the advertised.listeners protocols

[ https://issues.apache.org/jira/browse/KAFKA-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131181#comment-15131181 ] Grant Henke commented on KAFKA-3194: [~junrao] [~ewencp] [~gwenshap] [~guozhang] Would any of you have

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

See Changes: [me] KAFKA-3092: Replace SinkTask onPartitionsAssigned/onPartitionsRevoked [me] MINOR: Some more Kafka Streams Javadocs -- [...truncated 6919 lines...]

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

See

[jira] [Commented] (KAFKA-3088) 0.9.0.0 broker crash on receipt of produce request with empty client ID

[ https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130571#comment-15130571 ] Grant Henke commented on KAFKA-3088: I have written a basic unit test that sends a produce request

Re: [DISCUSS] KIP-45 Standardize all client sequence interaction on j.u.Collection.

Hi Becket, On Wed, Jan 27, 2016 at 10:51 PM, Becket Qin wrote: > 2. For seek(), pause(), resume(), it depends on how easily user can use > them. > If we take current interface, and user have a list of partitions to > pause(), what they can do is something like: >

[jira] [Commented] (KAFKA-3194) Validate security.inter.broker.protocol against the advertised.listeners protocols

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

[jira] [Created] (KAFKA-3201) Add system test for KIP-31 and KIP-32 - Upgrade Test

Jiangjie Qin created KAFKA-3201: --- Summary: Add system test for KIP-31 and KIP-32 - Upgrade Test Key: KAFKA-3201 URL: https://issues.apache.org/jira/browse/KAFKA-3201 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-3194) Validate security.inter.broker.protocol against the advertised.listeners protocols

[ https://issues.apache.org/jira/browse/KAFKA-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3194: Fix Version/s: 0.9.1.0 > Validate security.inter.broker.protocol against the advertised.listeners

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

[ https://issues.apache.org/jira/browse/KAFKA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3188: Summary: Add integration test for KIP-31 and KIP-32 - Compatibility Test (was: Add integration

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

[ https://issues.apache.org/jira/browse/KAFKA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3188: Description: The integration test should test the compatibility between 0.10.0 broker with clients

[GitHub] kafka pull request: KAFKA-3198: Ticket Renewal Thread exits premat...

GitHub user kunickiaj opened a pull request: https://github.com/apache/kafka/pull/858 KAFKA-3198: Ticket Renewal Thread exits prematurely due to inverted c… KAFKA-3198: Ticket Renewal Thread exits prematurely due to inverted comparison The >= should be < since we are

[jira] [Commented] (KAFKA-3198) Ticket Renewal Thread exits prematurely due to inverted comparison

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

[GitHub] kafka pull request: HOTFIX: fix broken WorkerSourceTask test

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/859 HOTFIX: fix broken WorkerSourceTask test You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka hotfix-worker-source-test

[jira] [Updated] (KAFKA-3194) Validate security.inter.broker.protocol against the advertised.listeners protocols

[ https://issues.apache.org/jira/browse/KAFKA-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3194: Resolution: Fixed Status: Resolved (was: Patch Available) > Validate

[GitHub] kafka pull request: KAFKA-3194: Validate security.inter.broker.pro...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/851 --- 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-3198) Ticket Renewal Thread exits prematurely due to inverted comparison

[ https://issues.apache.org/jira/browse/KAFKA-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3198: --- Fix Version/s: 0.9.0.1 > Ticket Renewal Thread exits prematurely due to inverted comparison >

[jira] [Commented] (KAFKA-3188) Add system test for KIP-31 and KIP-32 - Compatibility Test

[ https://issues.apache.org/jira/browse/KAFKA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131425#comment-15131425 ] Jiangjie Qin commented on KAFKA-3188: - [~apovzner] Thanks for the suggestion. I just split the system

[jira] [Commented] (KAFKA-3199) LoginManager should allow using an existing Subject

[ https://issues.apache.org/jira/browse/KAFKA-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131356#comment-15131356 ] Gwen Shapira commented on KAFKA-3199: - Are there any drawbacks for simply checking if a valid subject

[jira] [Updated] (KAFKA-3188) Add system test for KIP-31 and KIP-32 - Compatibility Test

[ https://issues.apache.org/jira/browse/KAFKA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3188: Summary: Add system test for KIP-31 and KIP-32 - Compatibility Test (was: Add integration test for

[jira] [Created] (KAFKA-3202) Add system test for KIP-31 and KIP-32 - Change message format version on the fly

Jiangjie Qin created KAFKA-3202: --- Summary: Add system test for KIP-31 and KIP-32 - Change message format version on the fly Key: KAFKA-3202 URL: https://issues.apache.org/jira/browse/KAFKA-3202

[jira] [Commented] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

[ https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131451#comment-15131451 ] Jay Kreps commented on KAFKA-3197: -- Would it be better to treat this more as a bug than a configurable

[GitHub] kafka pull request: MINOR: Fix restoring for source KTable

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/860 MINOR: Fix restoring for source KTable You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka KRestoreChangelog Alternatively

[jira] [Work started] (KAFKA-3199) LoginManager should allow using an existing Subject

[ https://issues.apache.org/jira/browse/KAFKA-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3199 started by Adam Kunicki. --- > LoginManager should allow using an existing Subject >

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

See Changes: [cshapi] KAFKA-3194: Validate security.inter.broker.protocol against the adver… -- [...truncated 4723 lines...] org.apache.kafka.connect.json.JsonConverterTest > timeToConnect

[jira] [Created] (KAFKA-3203) Add UnknownCodecException and UnknownMagicByteException to error mapping

Jiangjie Qin created KAFKA-3203: --- Summary: Add UnknownCodecException and UnknownMagicByteException to error mapping Key: KAFKA-3203 URL: https://issues.apache.org/jira/browse/KAFKA-3203 Project: Kafka

[jira] [Assigned] (KAFKA-3203) Add UnknownCodecException and UnknownMagicByteException to error mapping

[ https://issues.apache.org/jira/browse/KAFKA-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-3203: -- Assignee: Grant Henke > Add UnknownCodecException and UnknownMagicByteException to error

[jira] [Updated] (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:all-tabpanel ] Ashish K Singh updated KAFKA-3186: -- Status: Patch Available (was: Open) > Kafka authorizer should be aware of principal types it

[GitHub] kafka pull request: KAFKA-3186: Make Kafka authorizer aware of pri...

GitHub user SinghAsDev opened a pull request: https://github.com/apache/kafka/pull/861 KAFKA-3186: Make Kafka authorizer aware of principal types it supports. You can merge this pull request into a Git repository by running: $ git pull https://github.com/SinghAsDev/kafka

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

[jira] [Commented] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

[ https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131507#comment-15131507 ] Jiangjie Qin commented on KAFKA-3197: - Hey Jay, Yes, idempotent producer would solve the problem. And

[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=15131536#comment-15131536 ] Jiangjie Qin commented on KAFKA-3177: - [~hachikuji] The two categories makes sense. As you said it is

[jira] [Updated] (KAFKA-3199) LoginManager should allow using an existing Subject

[ https://issues.apache.org/jira/browse/KAFKA-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Kunicki updated KAFKA-3199: Status: Patch Available (was: In Progress) https://github.com/apache/kafka/pull/862 >

[jira] [Commented] (KAFKA-3199) LoginManager should allow using an existing Subject

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

[jira] [Issue Comment Deleted] (KAFKA-3199) LoginManager should allow using an existing Subject

[ https://issues.apache.org/jira/browse/KAFKA-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Kunicki updated KAFKA-3199: Comment: was deleted (was: https://github.com/apache/kafka/pull/862) > LoginManager should allow

[GitHub] kafka pull request: KAFKA-3199: LoginManager should allow using an...

GitHub user kunickiaj opened a pull request: https://github.com/apache/kafka/pull/862 KAFKA-3199: LoginManager should allow using an existing Subject One possible solution which doesn't require a new configuration parameter: But it assumes that if there is already a Subject you

[jira] [Updated] (KAFKA-3088) 0.9.0.0 broker crash on receipt of produce request with empty client ID

[ https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3088: --- Fix Version/s: 0.9.0.1 > 0.9.0.0 broker crash on receipt of produce request with empty client ID >

[jira] [Commented] (KAFKA-3088) 0.9.0.0 broker crash on receipt of produce request with empty client ID

[ https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130616#comment-15130616 ] Grant Henke commented on KAFKA-3088: [~ijuma] Sounds good. Thanks for the confirmation. I will make a

[jira] [Commented] (KAFKA-3088) 0.9.0.0 broker crash on receipt of produce request with empty client ID

[ https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130601#comment-15130601 ] Ismael Juma commented on KAFKA-3088: [~granthenke], your suggestion seems to make sense given the

[jira] [Commented] (KAFKA-3088) 0.9.0.0 broker crash on receipt of produce request with empty client ID

[ https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130609#comment-15130609 ] Ismael Juma commented on KAFKA-3088: This may be a candidate for 0.9.0.1. > 0.9.0.0 broker crash on

[jira] [Commented] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

[ https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131409#comment-15131409 ] Jiangjie Qin commented on KAFKA-3197: - [~enothereska] We have already defined sync and async in the

[GitHub] kafka pull request: MINOR: Pin to system tests to ducktape 0.3.10

GitHub user granders opened a pull request: https://github.com/apache/kafka/pull/863 MINOR: Pin to system tests to ducktape 0.3.10 You can merge this pull request into a Git repository by running: $ git pull https://github.com/confluentinc/kafka increment-ducktape-0.9.0

[jira] [Commented] (KAFKA-3198) Ticket Renewal Thread exits prematurely due to inverted comparison

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

[GitHub] kafka pull request: KAFKA-3198: Ticket Renewal Thread exits premat...

GitHub user kunickiaj reopened a pull request: https://github.com/apache/kafka/pull/858 KAFKA-3198: Ticket Renewal Thread exits prematurely due to inverted c… KAFKA-3198: Ticket Renewal Thread exits prematurely due to inverted comparison The >= should be < since we are

[GitHub] kafka pull request: KAFKA-3198: Ticket Renewal Thread exits premat...

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

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

See Changes: [wangguoz] MINOR: Fix restoring for source KTable -- [...truncated 4695 lines...] org.apache.kafka.connect.json.JsonConverterTest > mapToConnectStringKeys PASSED

[jira] [Commented] (KAFKA-3203) Add UnknownCodecException and UnknownMagicByteException to error mapping

[ https://issues.apache.org/jira/browse/KAFKA-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131805#comment-15131805 ] Grant Henke commented on KAFKA-3203: [~becket_qin] I couldn't find anywhere that

[jira] [Commented] (KAFKA-3198) Ticket Renewal Thread exits prematurely due to inverted comparison

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

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

See Changes: [wangguoz] MINOR: Fix restoring for source KTable -- [...truncated 5040 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[0] PASSED

[GitHub] kafka pull request: MINOR: Fix restoring for source KTable

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/860 --- 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-3198) Ticket Renewal Thread exits prematurely due to inverted comparison

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

[GitHub] kafka pull request: KAFKA-3198: Ticket Renewal Thread exits premat...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/858 --- 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-3198) Ticket Renewal Thread exits prematurely due to inverted comparison

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

[jira] [Commented] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

[ https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130781#comment-15130781 ] Joel Koshy commented on KAFKA-3197: --- [~enothereska] - the documentation is accurate in that it . The

[jira] [Commented] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

[ https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130785#comment-15130785 ] Joel Koshy commented on KAFKA-3197: --- Sorry - hit enter too soon. "in that it does not specifically say

[jira] [Commented] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

[ https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130761#comment-15130761 ] Jiangjie Qin commented on KAFKA-3197: - [~enothereska] The documentation of

Re: Kafka cluster performance degradation (Kafka 0.8.2.1)

Hi Cliff, Thanks for getting back to me on this. Sorry for the delay on replying to you, but I was away on holiday. I have been monitoring the Kafka brokers via JMX and on all nodes CPU usage was pretty much idle, under 1% as you said. I should have mentioned before that the Kafka cluster was

[GitHub] kafka pull request: KAFKA-3092: Replace SinkTask onPartitionsAssig...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/815 --- 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-3092) Rename SinkTask.onPartitionsAssigned/onPartitionsRevoked and Clarify Contract

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

[jira] [Commented] (KAFKA-3092) Rename SinkTask.onPartitionsAssigned/onPartitionsRevoked and Clarify Contract

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

[GitHub] kafka pull request: MINOR: some more Javadocs

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/853 --- 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-3129) Console Producer/Consumer Issue

[ https://issues.apache.org/jira/browse/KAFKA-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-3129: --- Attachment: server.log.normal.txt server.log entries for a successful console producer of

[jira] [Comment Edited] (KAFKA-3129) Console Producer/Consumer Issue

[ https://issues.apache.org/jira/browse/KAFKA-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130998#comment-15130998 ] Vahid Hashemian edited comment on KAFKA-3129 at 2/3/16 7:49 PM: Attached

[jira] [Updated] (KAFKA-3129) Console Producer/Consumer Issue

[ https://issues.apache.org/jira/browse/KAFKA-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-3129: --- Attachment: server.log.abnormal.txt server.log entries for an unsuccessful console producer

[jira] [Comment Edited] (KAFKA-3129) Console Producer/Consumer Issue

[ https://issues.apache.org/jira/browse/KAFKA-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131005#comment-15131005 ] Vahid Hashemian edited comment on KAFKA-3129 at 2/3/16 7:49 PM: Attached

Re: Kafka cluster performance degradation (Kafka 0.8.2.1)

Hi Leo, We also have a fairly idle CPU for our brokers, but we aren't tracking latency like you are. We are mostly interested in overall throughput and storage. We are using compression and bundling which add to latency but decrease storage usage. Good luck, Cliff On Wed, Feb 3, 2016 at 10:55

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

Hi Harsha, Thank you for the review. Can you clarify - I think you are saying that the client should send its mechanism over the wire to the server. Is that correct? The exchange is slightly different in the KIP (the PR matches the KIP) from the one you described to enable interoperability with

[jira] [Created] (KAFKA-3198) Ticket Renewal Thread exits prematurely due to inverted comparison

Adam Kunicki created KAFKA-3198: --- Summary: Ticket Renewal Thread exits prematurely due to inverted comparison Key: KAFKA-3198 URL: https://issues.apache.org/jira/browse/KAFKA-3198 Project: Kafka

Re: [DISCUSS] KIP-45 Standardize all client sequence interaction on j.u.Collection.

Most of the use cases of pause/resume that I've seen work only on single partitions (e.g in Kafka Streams), so the current varargs method is kind of nice. It would also be nice to be able to do the following: consumer.pause(consumer.assignment()); Both variants seem convenient in different

[jira] [Created] (KAFKA-3199) LoginManager should allow using an existing Subject

Adam Kunicki created KAFKA-3199: --- Summary: LoginManager should allow using an existing Subject Key: KAFKA-3199 URL: https://issues.apache.org/jira/browse/KAFKA-3199 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

[ https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130806#comment-15130806 ] Eno Thereska commented on KAFKA-3197: - [~jjkoshy], [~becket_qin] Makes sense. I can't help but think

[jira] [Updated] (KAFKA-3199) LoginManager should allow using an existing Subject

[ https://issues.apache.org/jira/browse/KAFKA-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Kunicki updated KAFKA-3199: Issue Type: Improvement (was: Bug) > LoginManager should allow using an existing Subject >

[VOTE] KIP-33 - Add a time based log index to Kafka

Hi all, I would like to initiate the vote for KIP-33. https://cwiki.apache.org/confluence/display/KAFKA/KIP-33 +-+Add+a+time+based+log+index A good amount of the KIP has been touched during the discussion on KIP-32. So I also put the link to KIP-32 here for reference.

[jira] [Commented] (KAFKA-3129) Console Producer/Consumer Issue

[ https://issues.apache.org/jira/browse/KAFKA-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131021#comment-15131021 ] Vahid Hashemian commented on KAFKA-3129: [~hachikuji] I attached debug logs from server.log for