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

Sent incomplete message by mistake. I do not have a preference for (1) or (2). (1) basically makes us view supported versions for all brokers as a part of cluster wide state, however (2) lets client deal with individual brokers. From usage perspective, clients would need to choose a certain

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

I do not have a preference for 1 or 2. 1 basically makes us view supported versions for all brokers On Tuesday, March 15, 2016, Jay Kreps wrote: > Yeah I think there are two possible approaches: > 1. You get the versions in the metadata request and cache them and > invalidate

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

[ https://issues.apache.org/jira/browse/KAFKA-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15196767#comment-15196767 ] Ewen Cheslack-Postava commented on KAFKA-3290: -- This was reopened because it seemed to be

[jira] [Created] (KAFKA-3409) Mirror maker hangs indefinitely due to commit

TAO XIAO created KAFKA-3409: --- Summary: Mirror maker hangs indefinitely due to commit Key: KAFKA-3409 URL: https://issues.apache.org/jira/browse/KAFKA-3409 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-3408) consumer rebalance fail

zhongkai liu created KAFKA-3408: --- Summary: consumer rebalance fail Key: KAFKA-3408 URL: https://issues.apache.org/jira/browse/KAFKA-3408 Project: Kafka Issue Type: Bug Components:

[jira] [Commented] (KAFKA-3407) ErrorLoggingCallback trims helpful diagnostic information.

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

[GitHub] kafka pull request: KAFKA-3407 - ErrorLoggingCallback trims helpfu...

GitHub user jcustenborder opened a pull request: https://github.com/apache/kafka/pull/1079 KAFKA-3407 - ErrorLoggingCallback trims helpful diagnostic information. This should help when diagnosing issues with the console producer. This allows the logger to use `exception` rather

[jira] [Updated] (KAFKA-3407) ErrorLoggingCallback trims helpful diagnostic information.

[ https://issues.apache.org/jira/browse/KAFKA-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Custenborder updated KAFKA-3407: --- Summary: ErrorLoggingCallback trims helpful diagnostic information. (was:

[jira] [Updated] (KAFKA-3407) ErrorLoggingCallback trims helpful diagnosting information.

[ https://issues.apache.org/jira/browse/KAFKA-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Custenborder updated KAFKA-3407: --- Summary: ErrorLoggingCallback trims helpful diagnosting information. (was:

[jira] [Created] (KAFKA-3407) ErrorLoggingCallback trims helpful logging messages.

Jeremy Custenborder created KAFKA-3407: -- Summary: ErrorLoggingCallback trims helpful logging messages. Key: KAFKA-3407 URL: https://issues.apache.org/jira/browse/KAFKA-3407 Project: Kafka

[GitHub] kafka pull request: Fixes for Windows #154

GitHub user JeffersJi opened a pull request: https://github.com/apache/kafka/pull/1078 Fixes for Windows #154 See the link: https://github.com/apache/kafka/pull/154 You can merge this pull request into a Git repository by running: $ git pull

[jira] [Updated] (KAFKA-3378) Client blocks forever if SocketChannel connects instantly

[ https://issues.apache.org/jira/browse/KAFKA-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3378: --- Priority: Blocker (was: Critical) Thanks for reporting this. Marking this as a blocker for 0.10.0 since it

[jira] [Commented] (KAFKA-2078) Getting Selector [WARN] Error in I/O with host java.io.EOFException

[ https://issues.apache.org/jira/browse/KAFKA-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15196540#comment-15196540 ] Mart Haitjema commented on KAFKA-2078: -- I posted a

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

See Changes: [me] MINOR: Remove unused import in `WordCountJob` to fix checkstyle failure [me] KAFKA-3260 - Added SourceTask.commitRecord -- [...truncated 1544 lines...]

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

Both the KIP and the PR have been updated to a cut-down version as discussed in the KIP meeting today. Any feedback is appreciated. On Tue, Mar 15, 2016 at 7:39 PM, Rajini Sivaram < rajinisiva...@googlemail.com> wrote: > Following on from the discussions in the KIP meeting today, the suggestion

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

Yeah I think there are two possible approaches: 1. You get the versions in the metadata request and cache them and invalidate that cache if you get a version mismatch error (basically as we do with leadership information). 2. You check each connection I think combining metadata request and

[jira] [Created] (KAFKA-3406) CommonClientConfigs.RETRY_BACKOFF_MS_DOC should be more general

Jun Rao created KAFKA-3406: -- Summary: CommonClientConfigs.RETRY_BACKOFF_MS_DOC should be more general Key: KAFKA-3406 URL: https://issues.apache.org/jira/browse/KAFKA-3406 Project: Kafka Issue

[jira] [Commented] (KAFKA-3205) Error in I/O with host (java.io.EOFException) raised in producer

[ https://issues.apache.org/jira/browse/KAFKA-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15196471#comment-15196471 ] Mart Haitjema commented on KAFKA-3205: -- I also ran into this issue and discovered that the broker

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

Hey Jay, as discussed earlier it is not safe to cache/relay a broker's version or its supported API versions, by the time the client connects the broker might have upgraded to another version which effectively makes this information useless in a cached form. The complexity of querying for

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

Hello Jay, On Tue, Mar 15, 2016 at 3:35 PM, Jay Kreps wrote: > Hey Ashish, > > Can you expand in the proposal on how this would be used by clients? > Will add some info along this line. This proposal only has one slot for api versions, though in fact there > is potentially

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

Hey Ashish, Can you expand in the proposal on how this would be used by clients? This proposal only has one slot for api versions, though in fact there is potentially a different version on each broker. I think the proposal is that every single time the client establishes a connection it would

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

Magnus and I had a brief discussion following the KIP call. KIP-35 wiki has been updated accordingly. Please review the KIP and vote on the corresponding vote thread. On Mon, Mar 14, 2016 at 11:27 PM, Ashish

[jira] [Resolved] (KAFKA-3260) Increase the granularity of commit for SourceTask

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

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

See Changes: [wangguoz] MINOR: kstream/ktable counting method with default long serdes [wangguoz] MINOR: Add test that verifies fix for KAFKA-3047 -- [...truncated 5741 lines...]

[jira] [Commented] (KAFKA-3260) Increase the granularity of commit for SourceTask

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

[GitHub] kafka pull request: KAFKA-3260 - Added SourceTask.commitRecord

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

[VOTE] KIP-45: Standardize KafkaConsumer API to use Collection

I'd like to open the vote for KIP-45. We've discussed several alternatives on the mailing list and in the KIP call, but this vote is only on the documented KIP: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61337336. This change will not be compatible with 0.9, but it will

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

See Changes: [wangguoz] MINOR: kstream/ktable counting method with default long serdes [wangguoz] MINOR: Add test that verifies fix for KAFKA-3047 [me] MINOR: Remove unused import in `WordCountJob` to fix checkstyle failure

Re: Kafka KIP meeting Mar 15 at 11:00am PST

The following are the notes from today's KIP discussion. - KIP-33 - Add a time based log index to Kafka: We decided NOT to include this in 0.10.0 since the changes may have performance risks. - KIP-45 - Standardize all client sequence interaction on j.u.Collection: There is no

[GitHub] kafka pull request: MINOR: Remove unused import in `WordCountJob` ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1077 --- 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-2982) Mark the old Scala producer and related classes as deprecated

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

[GitHub] kafka pull request: KAFKA-2982; Mark the old Scala producer and re...

Github user ijuma closed the pull request at: https://github.com/apache/kafka/pull/1067 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] kafka pull request: MINOR: Remove unused import in `WordCountJob` ...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1077 MINOR: Remove unused import in `WordCountJob` to fix checkstyle failure You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka

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

Following on from the discussions in the KIP meeting today, the suggestion is to implement a cut-down version of KIP-43 for 0.10.0.0 with a follow-on KIP after the release to address support for custom mechanisms. Changes to be removed from KIP-43: 1. Remove the configuration for

[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=15196012#comment-15196012 ] ASF GitHub Bot commented on KAFKA-3047: --- Github user asfgit closed the pull request at:

[GitHub] kafka pull request: MINOR: Add test that verifies fix for KAFKA-30...

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

See Changes: [junrao] KAFKA-1215; Rack-Aware replica assignment option -- [...truncated 70 lines...] if (value.expireTimestamp ==

[GitHub] kafka pull request: MINOR: kstream/ktable counting method with def...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1065 --- 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-3401) Message format change on the fly breaks 0.9 consumer

[ https://issues.apache.org/jira/browse/KAFKA-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3401: --- Fix Version/s: (was: 0.10.0.0) > Message format change on the fly breaks 0.9 consumer >

[jira] [Resolved] (KAFKA-3401) Message format change on the fly breaks 0.9 consumer

[ https://issues.apache.org/jira/browse/KAFKA-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3401. Resolution: Not A Problem Thanks for clarifying Becket. [~enothereska], please update the test to

[jira] [Comment Edited] (KAFKA-3401) Message format change on the fly breaks 0.9 consumer

[ https://issues.apache.org/jira/browse/KAFKA-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15195757#comment-15195757 ] Jiangjie Qin edited comment on KAFKA-3401 at 3/15/16 5:39 PM: -- [~ijuma] You

[jira] [Commented] (KAFKA-3401) Message format change on the fly breaks 0.9 consumer

[ https://issues.apache.org/jira/browse/KAFKA-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15195757#comment-15195757 ] Jiangjie Qin commented on KAFKA-3401: - [~ijuma] You are right. We should only change the message

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

[ https://issues.apache.org/jira/browse/KAFKA-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3387: -- Status: Patch Available (was: Open) > Update GetOffsetShell tool to not rely on old producer.

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

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

[GitHub] kafka pull request: KAFKA-3387: Update GetOffsetShell tool to not ...

GitHub user SinghAsDev opened a pull request: https://github.com/apache/kafka/pull/1076 KAFKA-3387: Update GetOffsetShell tool to not rely on old producer You can merge this pull request into a Git repository by running: $ git pull https://github.com/SinghAsDev/kafka

[jira] [Updated] (KAFKA-3315) Add Connect API to expose connector configuration info

[ https://issues.apache.org/jira/browse/KAFKA-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3315: - Status: Patch Available (was: Open) https://github.com/apache/kafka/pull/964 >

[jira] [Updated] (KAFKA-3336) Unify ser/de pair classes into one serde class

[ https://issues.apache.org/jira/browse/KAFKA-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3336: Status: Patch Available (was: Open) > Unify ser/de pair classes into one serde class >

[jira] [Commented] (KAFKA-1215) Rack-Aware replica assignment option

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

[GitHub] kafka pull request: KAFKA-1215: Rack-Aware replica assignment opti...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/132 --- 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-1215) Rack-Aware replica assignment option

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

[jira] [Updated] (KAFKA-3364) Centrallize doc generation

[ https://issues.apache.org/jira/browse/KAFKA-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3364: --- Description: Currently docs generation is scattered throughout the build file/process. Centralizing

[jira] [Commented] (KAFKA-3364) Centrallize doc generation

[ https://issues.apache.org/jira/browse/KAFKA-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15195643#comment-15195643 ] Grant Henke commented on KAFKA-3364: Moving docs under a single "generated" folder was done in

[jira] [Created] (KAFKA-3405) Deduplicate and break out release tasks

Grant Henke created KAFKA-3405: -- Summary: Deduplicate and break out release tasks Key: KAFKA-3405 URL: https://issues.apache.org/jira/browse/KAFKA-3405 Project: Kafka Issue Type: Sub-task

[jira] [Updated] (KAFKA-3364) Centrallize doc generation

[ https://issues.apache.org/jira/browse/KAFKA-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3364: --- Summary: Centrallize doc generation (was: Centrallize doc generation and move all generated docs

[jira] [Updated] (KAFKA-2787) Refactor gradle build

[ https://issues.apache.org/jira/browse/KAFKA-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-2787: --- Fix Version/s: (was: 0.10.0.0) 0.10.1.0 > Refactor gradle build >

[jira] [Commented] (KAFKA-3390) ReplicaManager may infinitely try-fail to shrink ISR set of deleted partition

[ https://issues.apache.org/jira/browse/KAFKA-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15195612#comment-15195612 ] Stevo Slavic commented on KAFKA-3390: - Yes. Topic ZK node and subnodes would not get deleted if topic

[jira] [Comment Edited] (KAFKA-3390) ReplicaManager may infinitely try-fail to shrink ISR set of deleted partition

[ https://issues.apache.org/jira/browse/KAFKA-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15195612#comment-15195612 ] Stevo Slavic edited comment on KAFKA-3390 at 3/15/16 4:44 PM: -- Yes. Topic ZK

[jira] [Commented] (KAFKA-3390) ReplicaManager may infinitely try-fail to shrink ISR set of deleted partition

[ https://issues.apache.org/jira/browse/KAFKA-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15195593#comment-15195593 ] Mayuresh Gharat commented on KAFKA-3390: Do you mean that even after the topic got completely

[jira] [Updated] (KAFKA-3250) release tarball is unnecessarily large due to duplicate libraries

[ https://issues.apache.org/jira/browse/KAFKA-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3250: --- Status: Patch Available (was: Open) > release tarball is unnecessarily large due to duplicate

[jira] [Commented] (KAFKA-3250) release tarball is unnecessarily large due to duplicate libraries

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

[GitHub] kafka pull request: KAFKA-3250: release tarball is unnecessarily l...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1075 KAFKA-3250: release tarball is unnecessarily large due to duplicate l… …ibraries This ensures duplicates are not copied in the distribution without rewriting all of the tar'ing

[jira] [Updated] (KAFKA-3250) release tarball is unnecessarily large due to duplicate libraries

[ https://issues.apache.org/jira/browse/KAFKA-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3250: --- Affects Version/s: 0.9.0.1 > release tarball is unnecessarily large due to duplicate libraries >

[jira] [Updated] (KAFKA-3250) release tarball is unnecessarily large due to duplicate libraries

[ https://issues.apache.org/jira/browse/KAFKA-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3250: --- Fix Version/s: 0.10.0.0 > release tarball is unnecessarily large due to duplicate libraries >

[jira] [Assigned] (KAFKA-3250) release tarball is unnecessarily large due to duplicate libraries

[ https://issues.apache.org/jira/browse/KAFKA-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-3250: -- Assignee: Grant Henke > release tarball is unnecessarily large due to duplicate libraries >

[GitHub] kafka pull request: Changed port of bootstrap server to default.

GitHub user raphw opened a pull request: https://github.com/apache/kafka/pull/1074 Changed port of bootstrap server to default. Kafka is typically running on port 9092. The example named a different port what makes it difficult to run a bootstrap example without any further

[jira] [Created] (KAFKA-3404) Issues running the kafka system test Sasl

Mickael Maison created KAFKA-3404: - Summary: Issues running the kafka system test Sasl Key: KAFKA-3404 URL: https://issues.apache.org/jira/browse/KAFKA-3404 Project: Kafka Issue Type: Bug

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

[ https://issues.apache.org/jira/browse/KAFKA-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3284: --- Priority: Major (was: Critical) > Consider removing beta label in security documentation >

[jira] [Updated] (KAFKA-1464) Add a throttling option to the Kafka replication tool

[ https://issues.apache.org/jira/browse/KAFKA-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1464: --- Fix Version/s: (was: 0.10.0.0) 0.10.1.0 > Add a throttling option to the Kafka

[jira] [Updated] (KAFKA-3383) Producer should not remove an in flight request before successfully parsing the response.

[ https://issues.apache.org/jira/browse/KAFKA-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3383: --- Priority: Critical (was: Major) > Producer should not remove an in flight request before

[jira] [Updated] (KAFKA-3123) Follower Broker cannot start if offsets are already out of range

[ https://issues.apache.org/jira/browse/KAFKA-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3123: --- Priority: Critical (was: Major) > Follower Broker cannot start if offsets are already out of range >

[jira] [Commented] (KAFKA-2311) Consumer's ensureNotClosed method not thread safe

[ https://issues.apache.org/jira/browse/KAFKA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15195419#comment-15195419 ] Ismael Juma commented on KAFKA-2311: [~timbrooks], would you like to submit a PR as per

[jira] [Commented] (KAFKA-3173) Error while moving some partitions to OnlinePartition state

[ https://issues.apache.org/jira/browse/KAFKA-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15195412#comment-15195412 ] Ismael Juma commented on KAFKA-3173: PR from [~fpj] is here: https://github.com/apache/kafka/pull/1041

[jira] [Updated] (KAFKA-3173) Error while moving some partitions to OnlinePartition state

[ https://issues.apache.org/jira/browse/KAFKA-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3173: --- Reviewer: Jun Rao Status: Patch Available (was: Open) > Error while moving some partitions to

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

[ https://issues.apache.org/jira/browse/KAFKA-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3284: --- Fix Version/s: (was: 0.10.0.0) 0.10.0.1 > Consider removing beta label in

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

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3177: --- Priority: Critical (was: Major) > Kafka consumer can hang when position() is called on a

Re: KIP-4 Wiki Update

Moving the relevant wiki text here for discussion/tracking: > > Server-side Admin Request handlers > > At the highest level, admin requests will be handled on the brokers the > same way that all message types are. However, because admin messages modify > cluster metadata they should be handled by

[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: --- Fix Version/s: (was: 0.10.0.0) 0.10.1.0 > Consider marking the new consumer as

[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: --- Priority: Major (was: Critical) > Consider marking the new consumer as production-ready >

[jira] [Updated] (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:all-tabpanel ] Ismael Juma updated KAFKA-3282: --- Fix Version/s: (was: 0.10.0.0) 0.10.1.0 > Change tools to use --new-consumer

[jira] [Created] (KAFKA-3403) Upgrade ZkClient to 0.8

Grant Henke created KAFKA-3403: -- Summary: Upgrade ZkClient to 0.8 Key: KAFKA-3403 URL: https://issues.apache.org/jira/browse/KAFKA-3403 Project: Kafka Issue Type: Improvement

[jira] [Updated] (KAFKA-3402) Restore behaviour of MetadataCache.getTopicMetadata when unsupported security protocol is received

[ https://issues.apache.org/jira/browse/KAFKA-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3402: --- Status: Patch Available (was: Open) > Restore behaviour of MetadataCache.getTopicMetadata when

[jira] [Commented] (KAFKA-3402) Restore behaviour of MetadataCache.getTopicMetadata when unsupported security protocol is received

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

[GitHub] kafka pull request: KAFKA-3402; Restore behaviour of MetadataCache...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1073 KAFKA-3402; Restore behaviour of MetadataCache.getTopicMetadata when unsupported security protocol is received You can merge this pull request into a Git repository by running: $ git pull

[jira] [Updated] (KAFKA-2832) support exclude.internal.topics in new consumer

[ https://issues.apache.org/jira/browse/KAFKA-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2832: --- Reviewer: (was: Gwen Shapira) > support exclude.internal.topics in new consumer >

[jira] [Created] (KAFKA-3402) Restore behaviour of MetadataCache.getTopicMetadata when unsupported security protocol is received

Ismael Juma created KAFKA-3402: -- Summary: Restore behaviour of MetadataCache.getTopicMetadata when unsupported security protocol is received Key: KAFKA-3402 URL: https://issues.apache.org/jira/browse/KAFKA-3402

[jira] [Updated] (KAFKA-2832) support exclude.internal.topics in new consumer

[ https://issues.apache.org/jira/browse/KAFKA-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2832: --- Assignee: Vahid Hashemian (was: Ismael Juma) > support exclude.internal.topics in new consumer >

[jira] [Updated] (KAFKA-2832) support exclude.internal.topics in new consumer

[ https://issues.apache.org/jira/browse/KAFKA-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2832: --- Assignee: Ismael Juma (was: Vahid Hashemian) Reviewer: Gwen Shapira > support

[jira] [Updated] (KAFKA-3394) Broker fails to parse Null Metadata in OffsetCommit requests

[ https://issues.apache.org/jira/browse/KAFKA-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3394: --- Reviewer: Jun Rao Status: Patch Available (was: Open) > Broker fails to parse Null Metadata in

[jira] [Commented] (KAFKA-3401) Message format change on the fly breaks 0.9 consumer

[ https://issues.apache.org/jira/browse/KAFKA-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15195218#comment-15195218 ] Ismael Juma commented on KAFKA-3401: [~becket_qin], the upgrade notes say: {code} Note: By setting

[jira] [Commented] (KAFKA-3373) Add `log` prefix to KIP-31/32 configs

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

[GitHub] kafka pull request: MINOR: KAFKA-3373 follow-up, a few val renames...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1072 MINOR: KAFKA-3373 follow-up, a few val renames remaining You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-3373-follow-up

[jira] [Updated] (KAFKA-3401) Message format change on the fly breaks 0.9 consumer

[ https://issues.apache.org/jira/browse/KAFKA-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3401: Attachment: 2016-03-15--009.zip Attaching error logs. > Message format change on the fly breaks

[jira] [Created] (KAFKA-3401) Message format change on the fly breaks 0.9 consumer

Eno Thereska created KAFKA-3401: --- Summary: Message format change on the fly breaks 0.9 consumer Key: KAFKA-3401 URL: https://issues.apache.org/jira/browse/KAFKA-3401 Project: Kafka Issue Type:

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

[GitHub] kafka pull request: MINOR: Add test that verifies fix for KAFKA-30...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1071 MINOR: Add test that verifies fix for KAFKA-3047 Also clean-up `LogTest` a little. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka

[jira] [Created] (KAFKA-3400) Topic stop working / can't describe topic

Tobias created KAFKA-3400: - Summary: Topic stop working / can't describe topic Key: KAFKA-3400 URL: https://issues.apache.org/jira/browse/KAFKA-3400 Project: Kafka Issue Type: Bug Affects

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

[GitHub] kafka pull request: KAFKA-3202: System test that changes message v...

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/1070 KAFKA-3202: System test that changes message version on the fly @becketqin @apovzner please have a look. @becketqin the test fails when the producer and consumer are 0.9.x and the message

[jira] [Commented] (KAFKA-3399) Offset/logfile corruption and kafka closing connections

[ https://issues.apache.org/jira/browse/KAFKA-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15195006#comment-15195006 ] Ismael Juma commented on KAFKA-3399: Thanks for letting us know. > Offset/logfile corruption and

[jira] [Resolved] (KAFKA-3399) Offset/logfile corruption and kafka closing connections

[ https://issues.apache.org/jira/browse/KAFKA-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Vetter resolved KAFKA-3399. Resolution: Fixed sry, this was a client library bug > Offset/logfile corruption and kafka

  1   2   >