Re: [DISCUSS] KIP-31 - Message format change proposal

Hey Ewen, Thanks for the comments and they are really good questions. Please inline replies. On Thu, Sep 3, 2015 at 9:35 PM, Ewen Cheslack-Postava wrote: > A few questions: > > 1. If we update the producers to only support V1, doesn't that mean people > get stuck on the current version of the p

[jira] [Updated] (KAFKA-1927) Replace requests in kafka.api with requests in org.apache.kafka.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jin xing updated KAFKA-1927: Assignee: Gwen Shapira > Replace requests in kafka.api with requests in > org.apache.kafka.common.requests

[jira] [Assigned] (KAFKA-1927) Replace requests in kafka.api with requests in org.apache.kafka.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jin xing reassigned KAFKA-1927: --- Assignee: jin xing (was: Gwen Shapira) > Replace requests in kafka.api with requests in > org.apach

[jira] [Updated] (KAFKA-1927) Replace requests in kafka.api with requests in org.apache.kafka.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jin xing updated KAFKA-1927: Assignee: (was: jin xing) > Replace requests in kafka.api with requests in > org.apache.kafka.common.re

[jira] [Commented] (KAFKA-2513) Checkstyle is not executed until gradle's tests phase

[ https://issues.apache.org/jira/browse/KAFKA-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730330#comment-14730330 ] Ewen Cheslack-Postava commented on KAFKA-2513: -- [~singhashish] Compile tasks

[jira] [Updated] (KAFKA-2489) System tests: update benchmark tests to run with new and old consumer

[ https://issues.apache.org/jira/browse/KAFKA-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-2489: - Reviewer: Gwen Shapira (was: Ewen Cheslack-Postava) Status: Patch Available

[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=14730307#comment-14730307 ] Ewen Cheslack-Postava commented on KAFKA-2516: -- Compatibility czar checking i

Re: [DISCUSS] KIP-31 - Message format change proposal

Heh, I guess in addition to my wall of text of questions, I should also say that I think this provides useful functionality and fixes issues that we've seen a bunch of questions and complaints about, so I'm in favor of a fix and this looks like a pretty good approach :) It might also be useful to

Re: [DISCUSS] KIP-31 - Message format change proposal

A few questions: 1. If we update the producers to only support V1, doesn't that mean people get stuck on the current version of the producer until they can be sure all their consumers have been upgraded? Is that going to be a problem for anyone, and does it potentially keep important fixes/enhance

Re: Review Request 36858: Patch for KAFKA-2120

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36858/#review96965 --- clients/src/main/java/org/apache/kafka/clients/InFlightRequests.jav

Huge Kafka Message size ( 386073344 ) in response

Hi all, I'm using the Kafka.Net library for implementing the Kafka Producer. One issue I find out is that sometimes it reads the response from kafka server, which indicates a huge message size 386073344. Apparently something must be wrong. But I'm not sure if it's a special flag that Kafka.net

[jira] [Commented] (KAFKA-2143) Replicas get ahead of leader and fail

[ https://issues.apache.org/jira/browse/KAFKA-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730117#comment-14730117 ] Jiangjie Qin commented on KAFKA-2143: - [~junrao], you are right. I realized there shou

[jira] [Commented] (KAFKA-2143) Replicas get ahead of leader and fail

[ https://issues.apache.org/jira/browse/KAFKA-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730109#comment-14730109 ] Jun Rao commented on KAFKA-2143: [~becket_qin], since before step (3), both A and B are in

[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=14730102#comment-14730102 ] Jun Rao commented on KAFKA-2477: Could you then try the following? In the above situation,

[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=14730063#comment-14730063 ] Ismael Juma commented on KAFKA-2516: Good point. > Rename o.a.k.client.tools to o.a.k

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

Gwen Shapira created KAFKA-2516: --- Summary: Rename o.a.k.client.tools to o.a.k.tools Key: KAFKA-2516 URL: https://issues.apache.org/jira/browse/KAFKA-2516 Project: Kafka Issue Type: Bug

Build failed in Jenkins: Kafka-trunk #615

See Changes: [cshapi] MINOR: Fix trace/debug logs in RequestChannel -- [...truncated 3203 lines...] kafka.log.LogManagerTest > testTimeBasedFlush PASSED kafka.log.LogManagerTest > testCreateLog PASSE

Re: [DISCUSS] KIP-31 - Message format change proposal

Hi Guozhang, I checked the code again. Actually CRC check probably won't fail. The newly added timestamp field might be treated as keyLength instead, so we are likely to receive an IllegalArgumentException when try to read the key. I'll update the KIP. Thanks, Jiangjie (Becket) Qin On Thu, Sep

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

Jun Rao created KAFKA-2515: -- Summary: handle oversized messages properly in new consumer Key: KAFKA-2515 URL: https://issues.apache.org/jira/browse/KAFKA-2515 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-2514) change default JVM options in kafka-run-class.sh

Jun Rao created KAFKA-2514: -- Summary: change default JVM options in kafka-run-class.sh Key: KAFKA-2514 URL: https://issues.apache.org/jira/browse/KAFKA-2514 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-2513) Checkstyle is not executed until gradle's tests phase

[ https://issues.apache.org/jira/browse/KAFKA-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729897#comment-14729897 ] Ashish K Singh commented on KAFKA-2513: --- I think if one wants to just compile, they

[jira] [Updated] (KAFKA-2512) Add version and magic byte verification on broker and clients.

[ https://issues.apache.org/jira/browse/KAFKA-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-2512: Description: Both new and old consumer do not verify the magic byte of a message when it consumes a

[jira] [Commented] (KAFKA-2120) Add a request timeout to NetworkClient

[ https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729893#comment-14729893 ] Mayuresh Gharat commented on KAFKA-2120: Updated reviewboard https://reviews.apach

Re: Review Request 36858: Patch for KAFKA-2120

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36858/ --- (Updated Sept. 3, 2015, 10:12 p.m.) Review request for kafka. Bugs: KAFKA-212

[jira] [Updated] (KAFKA-2120) Add a request timeout to NetworkClient

[ https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-2120: --- Attachment: KAFKA-2120_2015-09-03_15:12:02.patch > Add a request timeout to NetworkClient > --

[jira] [Updated] (KAFKA-2120) Add a request timeout to NetworkClient

[ https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-2120: --- Status: Patch Available (was: In Progress) > Add a request timeout to NetworkClient > ---

[jira] [Updated] (KAFKA-2512) Add version and magic byte verification on broker and clients.

[ https://issues.apache.org/jira/browse/KAFKA-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-2512: Summary: Add version and magic byte verification on broker and clients. (was: KafkaConsumer and Zoo

[jira] [Commented] (KAFKA-2513) Checkstyle is not executed until gradle's tests phase

[ https://issues.apache.org/jira/browse/KAFKA-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729875#comment-14729875 ] Ismael Juma commented on KAFKA-2513: [~ewencp], the way this should work IMO is that t

[jira] [Commented] (KAFKA-2513) Checkstyle is not executed until gradle's tests phase

[ https://issues.apache.org/jira/browse/KAFKA-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729824#comment-14729824 ] Ewen Cheslack-Postava commented on KAFKA-2513: -- I considered the same thing w

[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=14729800#comment-14729800 ] Jason Gustafson commented on KAFKA-2397: [~becket_qin] I'm not sure anyone was sug

[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=14729769#comment-14729769 ] Jiangjie Qin commented on KAFKA-2397: - [~ewencp] [~hachikuji] Some thoughts on this. I

[jira] [Commented] (KAFKA-2513) Checkstyle is not executed until gradle's tests phase

[ https://issues.apache.org/jira/browse/KAFKA-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729755#comment-14729755 ] Ismael Juma commented on KAFKA-2513: I agree that it's more like compile than tests. D

[jira] [Commented] (KAFKA-2513) Checkstyle is not executed until gradle's tests phase

[ https://issues.apache.org/jira/browse/KAFKA-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729740#comment-14729740 ] Ashish K Singh commented on KAFKA-2513: --- [~ijuma], [~gwenshap] thoughts? > Checksty

[jira] [Created] (KAFKA-2513) Checkstyle is not executed until gradle's tests phase

Ashish K Singh created KAFKA-2513: - Summary: Checkstyle is not executed until gradle's tests phase Key: KAFKA-2513 URL: https://issues.apache.org/jira/browse/KAFKA-2513 Project: Kafka Issue T

[GitHub] kafka pull request: MINOR: Fix trace/debug logs in RequestChannel

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/192 --- 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-2461) request logger no longer logs extra information in debug mode

[ https://issues.apache.org/jira/browse/KAFKA-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729711#comment-14729711 ] Ashish K Singh commented on KAFKA-2461: --- [~gwenshap], [~ijuma], created https://gith

[GitHub] kafka pull request: MINOR: Fix trace/debug logs in RequestChannel

GitHub user SinghAsDev opened a pull request: https://github.com/apache/kafka/pull/192 MINOR: Fix trace/debug logs in RequestChannel You can merge this pull request into a Git repository by running: $ git pull https://github.com/SinghAsDev/kafka KAFKA-2461-2 Alternatively you

[jira] [Created] (KAFKA-2512) KafkaConsumer and ZookeeperConsumerConnector should verify the magic byte.

Jiangjie Qin created KAFKA-2512: --- Summary: KafkaConsumer and ZookeeperConsumerConnector should verify the magic byte. Key: KAFKA-2512 URL: https://issues.apache.org/jira/browse/KAFKA-2512 Project: Kafka

Re: [DISCUSS] KIP-31 - Message format change proposal

Hi, Guozhang, Thanks for reading the KIP. By "old consumer", I meant the ZookeeperConsumerConnector in trunk now, i.e. without this bug fixed. If we fix the ZookeeperConsumerConnector then it will throw exception complaining about the unsupported version when it sees message format V1. What I was

Re: Review Request 36578: Patch for KAFKA-2338

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36578/#review97668 --- Thanks for the patch. A couple of comments below. core/src/main/sc

Re: [DISCUSS] KIP-31 - Message format change proposal

Thanks for the write-up Jiangjie. One comment about migration plan: "For old consumers, if they see the new protocol the CRC check will fail".. Do you mean this bug in the old consumer cannot be fixed in a backward-compatible way? Guozhang On Thu, Sep 3, 2015 at 8:35 AM, Jiangjie Qin wrote:

[jira] [Commented] (KAFKA-2461) request logger no longer logs extra information in debug mode

[ https://issues.apache.org/jira/browse/KAFKA-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729580#comment-14729580 ] Ismael Juma commented on KAFKA-2461: [~singhashish], I'll let [~gwenshap] comment on w

[jira] [Commented] (KAFKA-2461) request logger no longer logs extra information in debug mode

[ https://issues.apache.org/jira/browse/KAFKA-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729576#comment-14729576 ] Gwen Shapira commented on KAFKA-2461: - Well, the reason we have two different log stat

[jira] [Commented] (KAFKA-2461) request logger no longer logs extra information in debug mode

[ https://issues.apache.org/jira/browse/KAFKA-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729555#comment-14729555 ] Ashish K Singh commented on KAFKA-2461: --- Should I keep the detailed info in debug le

[jira] [Commented] (KAFKA-2461) request logger no longer logs extra information in debug mode

[ https://issues.apache.org/jira/browse/KAFKA-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729540#comment-14729540 ] Gwen Shapira commented on KAFKA-2461: - TRIVIAL pull request that doesn't require a JIR

[DISCUSS] KIP-31 - Message format change proposal

Hi, We just created KIP-31 to propose a message format change in Kafka. https://cwiki.apache.org/confluence/display/KAFKA/KIP-31+-+Message+format+change+proposal As a summary, the motivations are: 1. Avoid server side message re-compression 2. Honor time-based log roll and retention 3. Enable of

[jira] [Commented] (KAFKA-2461) request logger no longer logs extra information in debug mode

[ https://issues.apache.org/jira/browse/KAFKA-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729534#comment-14729534 ] Ashish K Singh commented on KAFKA-2461: --- [~ijuma] Oops, I got it reversed. That's my

[jira] [Created] (KAFKA-2511) KIP-31 message format change

Jiangjie Qin created KAFKA-2511: --- Summary: KIP-31 message format change Key: KAFKA-2511 URL: https://issues.apache.org/jira/browse/KAFKA-2511 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-2506) Refactor KafkaConsumer.partitionsFor(topic) to get metadata of topic without modifying state of Metadata

[ https://issues.apache.org/jira/browse/KAFKA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh resolved KAFKA-2506. --- Resolution: Duplicate > Refactor KafkaConsumer.partitionsFor(topic) to get metadata of topic w

[jira] [Commented] (KAFKA-2506) Refactor KafkaConsumer.partitionsFor(topic) to get metadata of topic without modifying state of Metadata

[ https://issues.apache.org/jira/browse/KAFKA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729502#comment-14729502 ] Ashish K Singh commented on KAFKA-2506: --- I think KAFKA-1893 does not depend on this,

[jira] [Updated] (KAFKA-1935) Consumer should use a separate socket for Coordinator connection

[ https://issues.apache.org/jira/browse/KAFKA-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-1935: --- Issue Type: Sub-task (was: Bug) Parent: KAFKA-1326 > Consumer should use a separate s

[jira] [Commented] (KAFKA-2510) Prevent broker from re-replicating / losing data due to disk misconfiguration

[ https://issues.apache.org/jira/browse/KAFKA-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729413#comment-14729413 ] Gwen Shapira commented on KAFKA-2510: - Note that if you accidentally manage to set an

[jira] [Created] (KAFKA-2510) Prevent broker from re-replicating / losing data due to disk misconfiguration

Gwen Shapira created KAFKA-2510: --- Summary: Prevent broker from re-replicating / losing data due to disk misconfiguration Key: KAFKA-2510 URL: https://issues.apache.org/jira/browse/KAFKA-2510 Project: Ka

[jira] [Commented] (KAFKA-2506) Refactor KafkaConsumer.partitionsFor(topic) to get metadata of topic without modifying state of Metadata

[ https://issues.apache.org/jira/browse/KAFKA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729374#comment-14729374 ] Jason Gustafson commented on KAFKA-2506: [~singhashish] I realized that the partit

[VOTE] 0.8.2.2 Candidate 1

This is the first candidate for release of Apache Kafka 0.8.2.2. This only fixes two critical issues (KAFKA-2189 and KAFKA-2308) related to snappy in 0.8.2.1. Release Notes for the 0.8.2.2 release https://people.apache.org/~junrao/kafka-0.8.2.2-candidate1/RELEASE_NOTES.html *** Please download, t

Re: Kafka New Consumer Performance Test ThroughPut Degradation

Hi Jason, Thanks for the update, I will be watching KAFKA-2489. Thanks, -Poorna On Wed, Sep 2, 2015 at 5:31 PM, Jason Gustafson wrote: > Hi Poorna, > > We've been looking at the same issue as part of KAFKA-2489. I suspect the > initial rebalance is causing the test to timeout, but we're still

Re: Hello!

Thank you Prabhjot. I will go through the wiki for setup. Sure :). On Thu, Sep 3, 2015 at 5:27 PM, Prabhjot Bharaj wrote: > Hi Sudhanshu, > > You can go through the details mentioned here: > http://kafka.apache.org/contributing.html > > Also, in case you need to setup your IDE, you can refer to

Re: Hello!

Hi Sudhanshu, You can go through the details mentioned here: http://kafka.apache.org/contributing.html Also, in case you need to setup your IDE, you can refer to these links:- http://www.lewuathe.com/blog/2014/10/16/build-apache-kafka-with-intellij-idea/ https://cwiki.apache.org/confluence/displ

Hello!

Hello Developers, I am Sudhanshu Gupta, software engineer working in Bangalore, India. We are using kafka in production and its fantastic. I am willing to contribute to the project. I have forked and cloned the kafka repo in my local. I want to get start on it. It would be great if anyone from th

[jira] [Commented] (KAFKA-1101) Need better java api for embedding kafkaserver in a java container app

[ https://issues.apache.org/jira/browse/KAFKA-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728732#comment-14728732 ] Dhaval M Patel commented on KAFKA-1101: --- Has support for single constructor been add

[jira] [Commented] (KAFKA-2461) request logger no longer logs extra information in debug mode

[ https://issues.apache.org/jira/browse/KAFKA-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728661#comment-14728661 ] Ismael Juma commented on KAFKA-2461: I'm a bit unclear about this. Normally, trace is

[jira] [Commented] (KAFKA-2072) Add StopReplica request/response to o.a.k.common.requests and replace the usage in core module

[ https://issues.apache.org/jira/browse/KAFKA-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728652#comment-14728652 ] Ismael Juma commented on KAFKA-2072: [~dajac], what I did for the other JIRAs like KAF

[jira] [Resolved] (KAFKA-2074) Add UpdateMetadata request/response to o.a.k.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2074. Resolution: Fixed Done as part of KAFKA-2411, filed KAFKA-2508 for replacing usage in core. > Add U

[jira] [Updated] (KAFKA-2074) Add UpdateMetadata request/response to o.a.k.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2074: --- Description: Add UpdateMetadata request/response to o.a.k.common.requests (was: Add UpdateMetadata re

[jira] [Updated] (KAFKA-2074) Add UpdateMetadata request/response to o.a.k.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2074: --- Summary: Add UpdateMetadata request/response to o.a.k.common.requests (was: Add UpdateMetadata reques

[jira] [Updated] (KAFKA-2067) Add LeaderAndISR request/response to org.apache.kafka.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2067: --- Resolution: Fixed Fix Version/s: 0.8.3 Status: Resolved (was: Patch Available) This

[jira] [Updated] (KAFKA-2067) Add LeaderAndISR request/response to org.apache.kafka.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2067: --- Description: Add LeaderAndISR request/response to org.apache.kafka.common.requests. Note that this wi

[jira] [Created] (KAFKA-2509) Replace LeaderAndIsr{Request,Response} with org.apache.kafka.common.network.requests equivalent

Ismael Juma created KAFKA-2509: -- Summary: Replace LeaderAndIsr{Request,Response} with org.apache.kafka.common.network.requests equivalent Key: KAFKA-2509 URL: https://issues.apache.org/jira/browse/KAFKA-2509

[jira] [Updated] (KAFKA-2067) Add LeaderAndISR request/response to org.apache.kafka.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2067: --- Summary: Add LeaderAndISR request/response to org.apache.kafka.common.requests (was: Add LeaderAndISR

[jira] [Updated] (KAFKA-2508) Replace UpdateMetadata{Request,Response} with org.apache.kafka.common.requests equivalent

[ https://issues.apache.org/jira/browse/KAFKA-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2508: --- Summary: Replace UpdateMetadata{Request,Response} with org.apache.kafka.common.requests equivalent (w

[jira] [Created] (KAFKA-2508) Replace UpdateMetadata{Request,Response} with org.apache.common.requests equivalent

Ismael Juma created KAFKA-2508: -- Summary: Replace UpdateMetadata{Request,Response} with org.apache.common.requests equivalent Key: KAFKA-2508 URL: https://issues.apache.org/jira/browse/KAFKA-2508 Project

[jira] [Updated] (KAFKA-2065) Add ControlledShutdown to org.apache.kafka.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2065: --- Resolution: Fixed Status: Resolved (was: Patch Available) Done via KAFKA-2411, I filed KAFKA-

[jira] [Updated] (KAFKA-2065) Add ControlledShutdown to org.apache.kafka.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2065: --- Fix Version/s: 0.8.3 > Add ControlledShutdown to org.apache.kafka.common.requests > -

[jira] [Updated] (KAFKA-2065) Add ControlledShutdown to org.apache.kafka.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2065: --- Summary: Add ControlledShutdown to org.apache.kafka.common.requests (was: Add ControlledShutdown to

[jira] [Updated] (KAFKA-2065) Add ControlledShutdown to org.apache.kafka.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2065: --- Description: Add ControlledShutdown to org.apache.kafka.common.requests (was: Add ControlledShutdown

[jira] [Created] (KAFKA-2507) Replace ControlledShutdown{Request,Response} with org.apache.kafka.common.requests equivalent

Ismael Juma created KAFKA-2507: -- Summary: Replace ControlledShutdown{Request,Response} with org.apache.kafka.common.requests equivalent Key: KAFKA-2507 URL: https://issues.apache.org/jira/browse/KAFKA-2507

[jira] [Commented] (KAFKA-2114) Unable to change min.insync.replicas default

[ https://issues.apache.org/jira/browse/KAFKA-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728627#comment-14728627 ] Stevo Slavic commented on KAFKA-2114: - I guess affected version should be 0.8.2, corre