[jira] [Created] (KAFKA-3387) Update GetOffsetShell tool to not rely on old producer.

Ashish K Singh created KAFKA-3387: - Summary: Update GetOffsetShell tool to not rely on old producer. Key: KAFKA-3387 URL: https://issues.apache.org/jira/browse/KAFKA-3387 Project: Kafka

[jira] [Updated] (KAFKA-3380) Add system test for GetOffsetShell tool

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

[jira] [Updated] (KAFKA-3380) Add system test for GetOffsetShell tool

[ https://issues.apache.org/jira/browse/KAFKA-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3380: -- Status: Patch Available (was: Open) > Add system test for GetOffsetShell tool >

[DISCUSS] KIP-35 - Retrieve protocol version

Sounds like we are mostly in agreement. Following are the key points. 1. Every time a protocol version changes, for any request/response, broker version, ApiVersion, will be bumped up. 2. Protocol documentation will be versioned with broker version. Every time there is a broker

[jira] [Commented] (KAFKA-3047) Explicit offset assignment in Log.append can corrupt the log

[ https://issues.apache.org/jira/browse/KAFKA-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15191642#comment-15191642 ] Guozhang Wang commented on KAFKA-3047: -- Good to know, thanks for explanation! > Explicit offset

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

I'm not sure supporting specific interim versions between releases are really that big of a concern, for a start the protocol changes may be in flux and not settle until the formal release, secondly the 3rd party clients typically lag behind at least until the formal release before they implement

[jira] [Updated] (KAFKA-3379) Update tools relying on old producer to use new producer.

[ https://issues.apache.org/jira/browse/KAFKA-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3379: -- Description: Following tools are using old producer. * ReplicationVerificationTool *

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

See Changes: [wangguoz] KAFKA-3047: Explicit offset assignment in Log.append can corrupt the log -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely

[jira] [Commented] (KAFKA-3047) Explicit offset assignment in Log.append can corrupt the log

[ https://issues.apache.org/jira/browse/KAFKA-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15191656#comment-15191656 ] Guozhang Wang commented on KAFKA-3047: -- Good to know, thanks for explanation! > Explicit offset

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

See Changes: [wangguoz] KAFKA-3047: Explicit offset assignment in Log.append can corrupt the log -- [...truncated 1469 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest >

[GitHub] kafka pull request: KAFKA-3047: Explicit offset assignment in Log....

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1029 --- 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-3047) Explicit offset assignment in Log.append can corrupt the log

[ https://issues.apache.org/jira/browse/KAFKA-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15191652#comment-15191652 ] Guozhang Wang commented on KAFKA-3047: -- Good to know, thanks for explanation! > Explicit offset

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

Yeah I agree with that characterization of the tradeoff. I think what that would imply would be that evolution of the metadata request (or the protocol version request) would remain server-first, whereas other apis would be independent. Not sure if I've fully thought it through, though. -Jay On

[jira] [Commented] (KAFKA-3215) controller may not be started when there are multiple ZK session expirations

[ https://issues.apache.org/jira/browse/KAFKA-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15190794#comment-15190794 ] Flavio Junqueira commented on KAFKA-3215: - [~junrao] Let me see if I understand this issue

[jira] [Assigned] (KAFKA-3215) controller may not be started when there are multiple ZK session expirations

[ https://issues.apache.org/jira/browse/KAFKA-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Junqueira reassigned KAFKA-3215: --- Assignee: Flavio Junqueira > controller may not be started when there are multiple

[jira] [Comment Edited] (KAFKA-3215) controller may not be started when there are multiple ZK session expirations

[ https://issues.apache.org/jira/browse/KAFKA-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15190794#comment-15190794 ] Flavio Junqueira edited comment on KAFKA-3215 at 3/11/16 1:21 PM: --

[GitHub] kafka pull request: KAFKA-3371: ClientCompatibilityTest system tes...

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/1051 KAFKA-3371: ClientCompatibilityTest system test failing @becketqin have a look if this looks reasonable to you. Thanks. You can merge this pull request into a Git repository by running: $

[jira] [Commented] (KAFKA-3371) ClientCompatibilityTest system test failing since KIP-31/KIP-32 was merged

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

[jira] [Assigned] (KAFKA-3371) ClientCompatibilityTest system test failing since KIP-31/KIP-32 was merged

[ https://issues.apache.org/jira/browse/KAFKA-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-3371: --- Assignee: Eno Thereska > ClientCompatibilityTest system test failing since KIP-31/KIP-32 was

[jira] [Work started] (KAFKA-3371) ClientCompatibilityTest system test failing since KIP-31/KIP-32 was merged

[ https://issues.apache.org/jira/browse/KAFKA-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3371 started by Eno Thereska. --- > ClientCompatibilityTest system test failing since KIP-31/KIP-32 was merged >

[jira] [Updated] (KAFKA-3361) Initial protocol documentation page and generation

[ https://issues.apache.org/jira/browse/KAFKA-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3361: --- Resolution: Fixed Fix Version/s: 0.9.0.0 Status: Resolved (was: Patch Available) >

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

[ https://issues.apache.org/jira/browse/KAFKA-3202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15191327#comment-15191327 ] Eno Thereska commented on KAFKA-3202: - Thank you [~becket_qin], I'll give it a go. > Add system test

[jira] [Resolved] (KAFKA-3215) controller may not be started when there are multiple ZK session expirations

[ https://issues.apache.org/jira/browse/KAFKA-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-3215. Resolution: Fixed Fix Version/s: 0.9.0.0 > controller may not be started when there are multiple ZK

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

[ https://issues.apache.org/jira/browse/KAFKA-3202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15191286#comment-15191286 ] Jiangjie Qin commented on KAFKA-3202: - [~ijuma] Apologies that I somehow missed your poke...

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

[ https://issues.apache.org/jira/browse/KAFKA-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3190: Priority: Blocker (was: Critical) > KafkaProducer should not invoke callback in send() >

[jira] [Assigned] (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 ] Eno Thereska reassigned KAFKA-3188: --- Assignee: Eno Thereska (was: Anna Povzner) > Add system test for KIP-31 and KIP-32 -

[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=15191313#comment-15191313 ] Eno Thereska commented on KAFKA-3188: - [~apovzner] I'll help and see how far I get with this. Thanks.

[jira] [Created] (KAFKA-3385) Need to log "Rejected connection" as WARNING message

Xiaomin Zhang created KAFKA-3385: Summary: Need to log "Rejected connection" as WARNING message Key: KAFKA-3385 URL: https://issues.apache.org/jira/browse/KAFKA-3385 Project: Kafka Issue

[jira] [Comment Edited] (KAFKA-3215) controller may not be started when there are multiple ZK session expirations

[ https://issues.apache.org/jira/browse/KAFKA-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15190794#comment-15190794 ] Flavio Junqueira edited comment on KAFKA-3215 at 3/11/16 4:34 PM: --

[jira] [Closed] (KAFKA-3386) Need to log "Rejected connection" as WARNING message

[ https://issues.apache.org/jira/browse/KAFKA-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaomin Zhang closed KAFKA-3386. closing out which was duplicated with KAFKA-3386 > Need to log "Rejected connection" as WARNING

[jira] [Commented] (KAFKA-3215) controller may not be started when there are multiple ZK session expirations

[ https://issues.apache.org/jira/browse/KAFKA-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15191094#comment-15191094 ] Jun Rao commented on KAFKA-3215: [~fpj], thanks for the analysis. Yes, it does seems that this issue is

[jira] [Created] (KAFKA-3386) Need to log "Rejected connection" as WARNING message

Xiaomin Zhang created KAFKA-3386: Summary: Need to log "Rejected connection" as WARNING message Key: KAFKA-3386 URL: https://issues.apache.org/jira/browse/KAFKA-3386 Project: Kafka Issue

[GitHub] kafka pull request: KAFKA-3381: Add system test for SimpleConsumer...

GitHub user SinghAsDev opened a pull request: https://github.com/apache/kafka/pull/1053 KAFKA-3381: Add system test for SimpleConsumerShell You can merge this pull request into a Git repository by running: $ git pull https://github.com/SinghAsDev/kafka KAFKA-3381

[jira] [Commented] (KAFKA-3047) Explicit offset assignment in Log.append can corrupt the log

[ https://issues.apache.org/jira/browse/KAFKA-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15191589#comment-15191589 ] Maciek Makowski commented on KAFKA-3047: [~ijuma]: thanks for the fix! [~guozhang]: I discovered

[jira] [Commented] (KAFKA-3361) Initial protocol documentation page and generation

[ https://issues.apache.org/jira/browse/KAFKA-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15191276#comment-15191276 ] Jiangjie Qin commented on KAFKA-3361: - [~granthenke] [~gwenshap] Thanks for fixing this :) BTW, I

[GitHub] kafka pull request: Changes to KafkaApis and MetadataCache based o...

GitHub user fpj opened a pull request: https://github.com/apache/kafka/pull/1052 Changes to KafkaApis and MetadataCache based on KAFKA-2073 Changes to reduce the latency of topic metadata requests based on the PR of KAFKA-2073. This is just to review for now, please do not merge

[jira] [Commented] (KAFKA-3047) Explicit offset assignment in Log.append can corrupt the log

[ https://issues.apache.org/jira/browse/KAFKA-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15191427#comment-15191427 ] Guozhang Wang commented on KAFKA-3047: -- Hi [~mmakowski], thanks for reporting this. I'm curious how

[GitHub] kafka pull request: MINOR: update compression design doc to includ...

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

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

Magnus, If we go with release version as protocol version (which I agree is much more user-friendly) - what will be the release version on trunk? 0.10.0-SNAPSHOT? How will clients handle the fact that some 0.10.0-SNAPSHOT will have different protocol than others (because we modify the protocol

[GitHub] kafka pull request: KAFKA-2073: migrate to client-side topic metad...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/988 --- 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-2073) Replace TopicMetadata request/response with o.a.k.requests.metadata

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

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

We introduced a way to bump the API version in between releases as part of the KIP-31/KIP-32 by the way. Extending that could maybe work. Take a look at the ApiVersion class and its documentation. Ismael On 11 Mar 2016 19:06, "Gwen Shapira" wrote: > Magnus, > > If we go with

[GitHub] kafka pull request: KAFKA-2960: Clear purgatory for partitions bef...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1018 --- 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-2960) DelayedProduce may cause message loss during repeated leader change

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

[jira] [Resolved] (KAFKA-1148) Delayed fetch/producer requests should be satisfied on a leader change

[ https://issues.apache.org/jira/browse/KAFKA-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-1148. --- Resolution: Fixed Fix Version/s: 0.10.0.0 Issue resolved by pull request 1018

[jira] [Commented] (KAFKA-2960) DelayedProduce may cause message loss during repeated leader change

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