[jira] [Created] (KAFKA-3281) Improve message of stop scripts when no processes are running

Sasaki Toru created KAFKA-3281: -- Summary: Improve message of stop scripts when no processes are running Key: KAFKA-3281 URL: https://issues.apache.org/jira/browse/KAFKA-3281 Project: Kafka Issu

[jira] [Updated] (KAFKA-3281) Improve message of stop scripts when no processes are running

[ https://issues.apache.org/jira/browse/KAFKA-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sasaki Toru updated KAFKA-3281: --- Description: Stop scritps such as kafka-server-stop.sh log messages of kill command's error when proc

[GitHub] kafka pull request: KAFKA-3281: Improve stop script's message when...

GitHub user sasakitoa opened a pull request: https://github.com/apache/kafka/pull/971 KAFKA-3281: Improve stop script's message when no processes are running Stop scritps such as kafka-server-stop.sh log messages of kill command's error when processes aren't running. This PR cha

[jira] [Commented] (KAFKA-3281) Improve message of stop scripts when no processes are running

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

[jira] [Updated] (KAFKA-3281) Improve message of stop scripts when no processes are running

[ https://issues.apache.org/jira/browse/KAFKA-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sasaki Toru updated KAFKA-3281: --- Fix Version/s: (was: 0.10.0.0) > Improve message of stop scripts when no processes are running > -

[jira] [Updated] (KAFKA-3281) Improve message of stop scripts when no processes are running

[ https://issues.apache.org/jira/browse/KAFKA-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sasaki Toru updated KAFKA-3281: --- Affects Version/s: (was: 0.9.0.1) 0.10.0.0 > Improve message of stop script

[GitHub] kafka pull request: KAFKA-3273; MessageFormatter and MessageReader...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/972 KAFKA-3273; MessageFormatter and MessageReader interfaces should be resilient to changes * Change `MessageFormat.writeTo` to take a `ConsumerRecord` * Change `MessageReader.readMessage()` to use `P

[jira] [Commented] (KAFKA-3273) MessageFormatter and MessageReader interfaces should be resilient to changes

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

[jira] [Updated] (KAFKA-3273) MessageFormatter and MessageReader interfaces should be resilient to changes

[ https://issues.apache.org/jira/browse/KAFKA-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3273: --- Reviewer: Jun Rao Status: Patch Available (was: Open) > MessageFormatter and MessageReader inte

[jira] [Created] (KAFKA-3282) Change tools to use --new-consumer by default and introduce --old-consumer

Ismael Juma created KAFKA-3282: -- Summary: Change tools to use --new-consumer by default and introduce --old-consumer Key: KAFKA-3282 URL: https://issues.apache.org/jira/browse/KAFKA-3282 Project: Kafka

[jira] [Commented] (KAFKA-3283) Consider marking the new consumer as production-ready

[ https://issues.apache.org/jira/browse/KAFKA-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167305#comment-15167305 ] Ismael Juma commented on KAFKA-3283: cc [~hachikuji] > Consider marking the new consu

[jira] [Created] (KAFKA-3283) Consider marking the new consumer as production-ready

Ismael Juma created KAFKA-3283: -- Summary: Consider marking the new consumer as production-ready Key: KAFKA-3283 URL: https://issues.apache.org/jira/browse/KAFKA-3283 Project: Kafka Issue Type: I

[jira] [Updated] (KAFKA-3283) Consider marking the new consumer as production-ready

[ https://issues.apache.org/jira/browse/KAFKA-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3283: --- Assignee: (was: Neha Narkhede) > Consider marking the new consumer as production-ready > -

[jira] [Commented] (KAFKA-3282) Change tools to use --new-consumer by default and introduce --old-consumer

[ https://issues.apache.org/jira/browse/KAFKA-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167307#comment-15167307 ] Ismael Juma commented on KAFKA-3282: cc [~hachikuji] > Change tools to use --new-cons

[jira] [Created] (KAFKA-3284) Consider removing beta label in security documentation

Ismael Juma created KAFKA-3284: -- Summary: Consider removing beta label in security documentation Key: KAFKA-3284 URL: https://issues.apache.org/jira/browse/KAFKA-3284 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-3285) Mirror Maker whitelist behavior differs between old and new consumer

Luke Steensen created KAFKA-3285: Summary: Mirror Maker whitelist behavior differs between old and new consumer Key: KAFKA-3285 URL: https://issues.apache.org/jira/browse/KAFKA-3285 Project: Kafka

[jira] [Updated] (KAFKA-3285) Mirror Maker whitelist behavior differs between old and new consumer

[ https://issues.apache.org/jira/browse/KAFKA-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Steensen updated KAFKA-3285: - Description: Using mirror maker's --new.consumer option changes the behavior of the --whitelist o

[jira] [Commented] (KAFKA-2435) More optimally balanced partition assignment strategy

[ https://issues.apache.org/jira/browse/KAFKA-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167424#comment-15167424 ] Andrew Olson commented on KAFKA-2435: - [~hachikuji] The pull request for this (https:

[jira] [Commented] (KAFKA-2434) remove roundrobin identical topic constraint in consumer coordinator (old API)

[ https://issues.apache.org/jira/browse/KAFKA-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167427#comment-15167427 ] Andrew Olson commented on KAFKA-2434: - [~junrao] The pull request for this (https://gi

[jira] [Commented] (KAFKA-2172) Round-robin partition assignment strategy too restrictive

[ https://issues.apache.org/jira/browse/KAFKA-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167431#comment-15167431 ] Andrew Olson commented on KAFKA-2172: - Note that the code changed in KAFKA-2196 was re

[jira] [Created] (KAFKA-3286) Add plugin to quickly check for outdated dependencies

Grant Henke created KAFKA-3286: -- Summary: Add plugin to quickly check for outdated dependencies Key: KAFKA-3286 URL: https://issues.apache.org/jira/browse/KAFKA-3286 Project: Kafka Issue Type: S

[jira] [Commented] (KAFKA-3025) KIP-31&KIP-32 (part 1): Add timestamp field to message, configs, and Producer/ConsumerRecord

[ https://issues.apache.org/jira/browse/KAFKA-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167485#comment-15167485 ] Jun Rao commented on KAFKA-3025: [~becket_qin], another thing. Could you update https://c

[jira] [Commented] (KAFKA-3286) Add plugin to quickly check for outdated dependencies

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

[GitHub] kafka pull request: KAFKA-3286: Add plugin to quickly check for ou...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/973 KAFKA-3286: Add plugin to quickly check for outdated dependencies Adds a gradle task to generate a report of outdate release dependencies: `gradle dependencyUpdates` Updates a few mino

[jira] [Updated] (KAFKA-3286) Add plugin to quickly check for outdated dependencies

[ https://issues.apache.org/jira/browse/KAFKA-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3286: --- Status: Patch Available (was: Open) > Add plugin to quickly check for outdated dependencies > ---

Re: new producer failed with org.apache.kafka.common.errors.TimeoutException

Thanks Ewen. I will get back with findings from my test run using 0.9.0.1 client. Regards, Kris On Tue, Feb 23, 2016 at 9:26 PM, Ewen Cheslack-Postava wrote: > Kris, > > This is a bit surprising, but handling the bootstrap servers, broker > failures/retirement, and cluster metadata properly is

[jira] [Commented] (KAFKA-3284) Consider removing beta label in security documentation

[ https://issues.apache.org/jira/browse/KAFKA-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167650#comment-15167650 ] Gwen Shapira commented on KAFKA-3284: - Just a doc change, right? > Consider removing

[jira] [Commented] (KAFKA-3284) Consider removing beta label in security documentation

[ https://issues.apache.org/jira/browse/KAFKA-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167656#comment-15167656 ] Ismael Juma commented on KAFKA-3284: [~gwenshap], removing the beta label is just a do

[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&focusedCommentId=15167681#comment-15167681 ] Ashish K Singh commented on KAFKA-1696: --- [~parth.brahmbhatt] thanks for working out

[GitHub] kafka pull request: MINOR: Connect status tracking API followup

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/974 MINOR: Connect status tracking API followup Fixes from @Ishiihara's review. You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka stat

[jira] [Created] (KAFKA-3287) Add over-wire encryption support between KAFKA and ZK

Ashish K Singh created KAFKA-3287: - Summary: Add over-wire encryption support between KAFKA and ZK Key: KAFKA-3287 URL: https://issues.apache.org/jira/browse/KAFKA-3287 Project: Kafka Issue T

[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&focusedCommentId=15167696#comment-15167696 ] Parth Brahmbhatt commented on KAFKA-1696: - [~singhashish] Thanks for taking the ti

[jira] [Created] (KAFKA-3288) Update ZK dependency to 3.5.1 when it is marked as stable

Ashish K Singh created KAFKA-3288: - Summary: Update ZK dependency to 3.5.1 when it is marked as stable Key: KAFKA-3288 URL: https://issues.apache.org/jira/browse/KAFKA-3288 Project: Kafka Iss

[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&focusedCommentId=15167734#comment-15167734 ] Ashish K Singh commented on KAFKA-1696: --- [~parth.brahmbhatt] I am in favor of keepin

[jira] [Commented] (KAFKA-3283) Consider marking the new consumer as production-ready

[ https://issues.apache.org/jira/browse/KAFKA-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167787#comment-15167787 ] Jiangjie Qin commented on KAFKA-3283: - [~ijuma] We have some discussion over the block

[jira] [Commented] (KAFKA-3025) KIP-31&KIP-32 (part 1): Add timestamp field to message, configs, and Producer/ConsumerRecord

[ https://issues.apache.org/jira/browse/KAFKA-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167792#comment-15167792 ] Jiangjie Qin commented on KAFKA-3025: - Sure, will do it soon. > KIP-31&KIP-32 (part 1

[jira] [Created] (KAFKA-3289) Update Kafka protocol guide wiki for KIP-31 / KIP-32

Jiangjie Qin created KAFKA-3289: --- Summary: Update Kafka protocol guide wiki for KIP-31 / KIP-32 Key: KAFKA-3289 URL: https://issues.apache.org/jira/browse/KAFKA-3289 Project: Kafka Issue Type:

[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&focusedCommentId=15167800#comment-15167800 ] Parth Brahmbhatt commented on KAFKA-1696: - So here is how that request path would

[jira] [Comment Edited] (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&focusedCommentId=15167800#comment-15167800 ] Parth Brahmbhatt edited comment on KAFKA-1696 at 2/25/16 8:23 PM: --

[jira] [Created] (KAFKA-3290) WorkerSourceTask testCommit transient failure

Jason Gustafson created KAFKA-3290: -- Summary: WorkerSourceTask testCommit transient failure Key: KAFKA-3290 URL: https://issues.apache.org/jira/browse/KAFKA-3290 Project: Kafka Issue Type: S

[jira] [Commented] (KAFKA-3283) Consider marking the new consumer as production-ready

[ https://issues.apache.org/jira/browse/KAFKA-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167900#comment-15167900 ] Ismael Juma commented on KAFKA-3283: [~becket_qin], sure. Feel free to add any other o

Re: [DISCUSS] KIP-35 - Retrieve protocol version

Kafka clients in Hadoop ecosystem, Flume, Spark, etc, have found it really difficult to cope up with Kafka releases as they want to support users on different Kafka versions. Capability to retrieve protocol version will go a long way to ease out those pain points. I will be happy to help out with t

[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&focusedCommentId=15167910#comment-15167910 ] Ashish K Singh commented on KAFKA-1696: --- [~parth.brahmbhatt] thanks for the detailed

[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&focusedCommentId=15167913#comment-15167913 ] Gwen Shapira commented on KAFKA-1696: - Just to clarify - the move away from ZK is for

[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&focusedCommentId=15167928#comment-15167928 ] Parth Brahmbhatt commented on KAFKA-1696: - [~gwenshap] [~sriharsha] Please share y

[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&focusedCommentId=15167939#comment-15167939 ] Gwen Shapira commented on KAFKA-1696: - I don't have specific opinions on the KIP yet,

[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&focusedCommentId=15167942#comment-15167942 ] Gwen Shapira commented on KAFKA-1696: - One thing I can't find in the KIP: * Will we su

[GitHub] kafka pull request: MINOR: Connect status tracking API followup

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/974 --- 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: [jira] [Commented] (KAFKA-1696) Kafka should be able to generate Hadoop delegation tokens

Gwen, I was just stating the probability of going away from ZK as there is a Kip in discuss state. I could not find any thread that says that the KIP is discarded. If it is, maybe we should move it to discarded KIPs section. Apologies if I propagated some confusion here. On Thursday, February 25,

[jira] [Commented] (KAFKA-3284) Consider removing beta label in security documentation

[ https://issues.apache.org/jira/browse/KAFKA-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167958#comment-15167958 ] Gwen Shapira commented on KAFKA-3284: - IMO: At least one large deployment saying they

[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&focusedCommentId=15167945#comment-15167945 ] Ashish K Singh commented on KAFKA-1696: --- I think posting a discuss thread makes sens

[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&focusedCommentId=15168010#comment-15168010 ] Parth Brahmbhatt commented on KAFKA-1696: - [~gwenshap] I think that discussion is

[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&focusedCommentId=15168023#comment-15168023 ] Sriharsha Chintalapani commented on KAFKA-1696: --- [~gwenshap] Port is not rel

[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&focusedCommentId=15168065#comment-15168065 ] Joel Koshy commented on KAFKA-3197: --- Hi [~fpj] so your suggestion is to preemptively inv

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

Jiangjie, I was originally only thinking about the "time.index.size.max.bytes" config in addition to the "offset.index.size.max.bytes". Since the latter's default size is 10MB, and for memory mapped file, we will allocate that much of memory at the start which could be a pressure on RAM if we doub

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

See

[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&focusedCommentId=15168130#comment-15168130 ] Gwen Shapira commented on KAFKA-1696: - OK, sounds good. Thanks. It does make this iss

[jira] [Created] (KAFKA-3291) DumpLogSegment tool should also provide an option to only verify index sanity.

Parth Brahmbhatt created KAFKA-3291: --- Summary: DumpLogSegment tool should also provide an option to only verify index sanity. Key: KAFKA-3291 URL: https://issues.apache.org/jira/browse/KAFKA-3291 Pr

[GitHub] kafka pull request: KAFKA-3291: DumpLogSegment tool should also pr...

GitHub user Parth-Brahmbhatt opened a pull request: https://github.com/apache/kafka/pull/975 KAFKA-3291: DumpLogSegment tool should also provide an option to only… … verify index sanity. You can merge this pull request into a Git repository by running: $ git pull https://gi

[jira] [Commented] (KAFKA-3291) DumpLogSegment tool should also provide an option to only verify index sanity.

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

[GitHub] kafka pull request: MINOR: Validate inner message compression attr...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/976 MINOR: Validate inner message compression attribute You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka validate-inner-message-compression

[jira] [Created] (KAFKA-3292) ClientQuotaManager.getOrCreateQuotaSensors() may return a null ClientSensors.throttleTimeSensor

Jun Rao created KAFKA-3292: -- Summary: ClientQuotaManager.getOrCreateQuotaSensors() may return a null ClientSensors.throttleTimeSensor Key: KAFKA-3292 URL: https://issues.apache.org/jira/browse/KAFKA-3292 Pro

[jira] [Assigned] (KAFKA-3292) ClientQuotaManager.getOrCreateQuotaSensors() may return a null ClientSensors.throttleTimeSensor

[ https://issues.apache.org/jira/browse/KAFKA-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3292: -- Assignee: Ismael Juma > ClientQuotaManager.getOrCreateQuotaSensors() may return a null > Clien

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

See

[GitHub] kafka pull request: KAFKA-3292; ClientQuotaManager.getOrCreateQuot...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/977 KAFKA-3292; ClientQuotaManager.getOrCreateQuotaSensors() may return a null ClientSensors.throttleTimeSensor You can merge this pull request into a Git repository by running: $ git pull https://g

[jira] [Commented] (KAFKA-3292) ClientQuotaManager.getOrCreateQuotaSensors() may return a null ClientSensors.throttleTimeSensor

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

[jira] [Updated] (KAFKA-3292) ClientQuotaManager.getOrCreateQuotaSensors() may return a null ClientSensors.throttleTimeSensor

[ https://issues.apache.org/jira/browse/KAFKA-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3292: --- Reviewer: Jun Rao Status: Patch Available (was: Open) > ClientQuotaManager.getOrCreateQuotaSens

[GitHub] kafka pull request: KAFKA-3292; ClientQuotaManager.getOrCreateQuot...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/977 --- 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-3292) ClientQuotaManager.getOrCreateQuotaSensors() may return a null ClientSensors.throttleTimeSensor

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

[jira] [Commented] (KAFKA-3292) ClientQuotaManager.getOrCreateQuotaSensors() may return a null ClientSensors.throttleTimeSensor

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

[GitHub] kafka pull request: MINOR: Validate inner message compression attr...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/976 --- 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: KAFKA-3280: KafkaConsumer Javadoc contains mis...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/968 --- 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-3280) KafkaConsumer Javadoc contains misleading description of heartbeat behavior and correct use

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

[jira] [Resolved] (KAFKA-3280) KafkaConsumer Javadoc contains misleading description of heartbeat behavior and correct use

[ https://issues.apache.org/jira/browse/KAFKA-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-3280. - Resolution: Fixed Issue resolved by pull request 968 [https://github.com/apache/kafka/pull/968] >

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

See Changes: [junrao] KAFKA-3292; ClientQuotaManager.getOrCreateQuotaSensors() may return a [junrao] MINOR: Validate inner message compression attribute [cshapi] KAFKA-3280: KafkaConsumer Javadoc contains misleading description of --

[jira] [Created] (KAFKA-3293) Consumers are not able to get messages.

Stephen Wong created KAFKA-3293: --- Summary: Consumers are not able to get messages. Key: KAFKA-3293 URL: https://issues.apache.org/jira/browse/KAFKA-3293 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3293) Consumers are not able to get messages.

[ https://issues.apache.org/jira/browse/KAFKA-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168407#comment-15168407 ] Stephen Wong commented on KAFKA-3293: - Testing code can be downloaded from: https://ww

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

See Changes: [junrao] KAFKA-3292; ClientQuotaManager.getOrCreateQuotaSensors() may return a [junrao] MINOR: Validate inner message compression attribute [cshapi] KAFKA-3280: KafkaConsumer Javadoc contains misleading description of -

[jira] [Created] (KAFKA-3294) Kafka REST API

Sriharsha Chintalapani created KAFKA-3294: - Summary: Kafka REST API Key: KAFKA-3294 URL: https://issues.apache.org/jira/browse/KAFKA-3294 Project: Kafka Issue Type: New Feature

Duplication when switching to preferred leader

Here is a case of data duplication that should be avoidable. It is observed when leadership of partition changes from the current leader back to preferred leader. Steps to reproduce: - Using 3 broker setup. - Create topic with 1 partition, replication factor=3, ISR count=2 and leader.imbalance