[jira] [Updated] (KAFKA-3124) Update protocol wiki page to reflect latest request/response formats

[ https://issues.apache.org/jira/browse/KAFKA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3124: Labels: newbie (was: ) > Update protocol wiki page to reflect latest request/response formats > ---

[jira] [Assigned] (KAFKA-3124) Update protocol wiki page to reflect latest request/response formats

[ https://issues.apache.org/jira/browse/KAFKA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei reassigned KAFKA-3124: - Assignee: Liquan Pei > Update protocol wiki page to reflect latest request/response formats > ---

[GitHub] kafka pull request: MINOR: Remove unused imports from tests whose ...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/836 MINOR: Remove unused imports from tests whose packages were fixed I missed this when reviewing: https://github.com/apache/kafka/commit/a58b459bddd5b1dcab224b53cda0196e947a5b09 You can merge t

Re: [DISCUSS] KIP-42: Add Producer and Consumer Interceptors

Neha, CRC is definitely an important type of metadata of a record. I am not arguing about that. But I think we should distinguish between two types of checksum here, 1) the checksum of user data. and 2) the checksum including system appended bytes. I completely agree that (1) is good to add. But

Re: [DISCUSS] KIP-42: Add Producer and Consumer Interceptors

Becket, In your scenario with one message from producer A and one message from producer B, those are two different messages, and they should be tracked as two different messages. So I would argue for using record CRC -- CRC that is actually used by the system + it will not require computing a diff

[jira] [Commented] (KAFKA-3171) min.insync.replicas not respected

[ https://issues.apache.org/jira/browse/KAFKA-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124197#comment-15124197 ] Grant Henke commented on KAFKA-3171: Can you try changing `props.put("ack", "all");` t

[jira] [Assigned] (KAFKA-3171) min.insync.replicas not respected

[ https://issues.apache.org/jira/browse/KAFKA-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-3171: -- Assignee: Grant Henke > min.insync.replicas not respected > - >

[GitHub] kafka pull request: MINOR: Remove unused imports from tests whose ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/836 --- 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: [DISCUSS] KIP-42: Add Producer and Consumer Interceptors

Joel, thanks for your feedback. I updated the wiki based on your comments about the wiki writeup. On Fri, Jan 29, 2016 at 11:50 AM, Anna Povzner wrote: > Becket, > > In your scenario with one message from producer A and one message from > producer B, those are two different messages, and they s

[GitHub] kafka pull request: KAFKA-2607: Review `Time` interface and its us...

GitHub user afine opened a pull request: https://github.com/apache/kafka/pull/837 KAFKA-2607: Review `Time` interface and its usage You can merge this pull request into a Git repository by running: $ git pull https://github.com/afine/kafka KAFKA-2607 Alternatively you can rev

[jira] [Commented] (KAFKA-2607) Review `Time` interface and its usage

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

[GitHub] kafka pull request: KAFKA-3164: Document client and mirrormaker up...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/838 KAFKA-3164: Document client and mirrormaker upgrade procedure/require… …ments You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/ka

Contributor List

Would it be possible to add me to the contributor list? My apache jira username is: abrahamfine Thanks, Abe

[jira] [Commented] (KAFKA-3164) Document client and mirrormaker upgrade procedure/requirements

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

[jira] [Updated] (KAFKA-3164) Document client and mirrormaker upgrade procedure/requirements

[ https://issues.apache.org/jira/browse/KAFKA-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3164: --- Status: Patch Available (was: Open) > Document client and mirrormaker upgrade procedure/requirements

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

See Changes: [wangguoz] MINOR: Remove unused imports from tests whose packages were fixed -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu

[jira] [Resolved] (KAFKA-3171) min.insync.replicas not respected

[ https://issues.apache.org/jira/browse/KAFKA-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Victor Serbu resolved KAFKA-3171. - Resolution: Invalid You are right, after I changed ack with "acks" producer raise error when ISR

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

See Changes: [wangguoz] MINOR: Remove unused imports from tests whose packages were fixed -- [...truncated 2793 lines...] kafka.log.LogTest > testTimeBasedLogRoll PASSED kafka.log.LogTest > te

[GitHub] kafka pull request: KAFKA-3121: Refactor KStream Aggregate to be L...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/839 KAFKA-3121: Refactor KStream Aggregate to be Lambda-able. You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka K3121s2 Altern

[jira] [Commented] (KAFKA-3121) KStream DSL API Improvement

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

Re: [DISCUSS] KIP-42: Add Producer and Consumer Interceptors

Hi Anna, I think there is value if CRC for only user bytes can be used. This will help when we have future protocol updates. Otherwise any protocol migration might break auditing if it largely relies on CRC including system bytes. I did some test to understand the performance overhead of having a

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

Flavio Junqueira created KAFKA-3173: --- Summary: Error while moving some partitions to OnlinePartition state Key: KAFKA-3173 URL: https://issues.apache.org/jira/browse/KAFKA-3173 Project: Kafka

[jira] [Created] (KAFKA-3174) Re-evaluate the CRC32 class performance.

Jiangjie Qin created KAFKA-3174: --- Summary: Re-evaluate the CRC32 class performance. Key: KAFKA-3174 URL: https://issues.apache.org/jira/browse/KAFKA-3174 Project: Kafka Issue Type: Improvement

[jira] [Updated] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3174: Affects Version/s: 0.9.0.0 Fix Version/s: 0.9.0.1 > Re-evaluate the CRC32 class performance.

Re: [DISCUSS] KIP-42: Add Producer and Consumer Interceptors

The rationale for the CRC covering the whole record was to check corruption in the full record contents as corruption there will equally prevent someone trying to consume the data. I think you could argue either way but let's definitely not end up with two different CRC calculations, that would jus

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124537#comment-15124537 ] Jay Kreps commented on KAFKA-3174: -- This is a great find. It looks like it did become an

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124555#comment-15124555 ] Ismael Juma commented on KAFKA-3174: Jay, I think you meant https://bugs.openjdk.java.

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124558#comment-15124558 ] Ismael Juma commented on KAFKA-3174: Becket, are you planning to do this one? I'll tak

[jira] [Commented] (KAFKA-2936) Socket server selector can stuck on one send in tight loop.

[ https://issues.apache.org/jira/browse/KAFKA-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124563#comment-15124563 ] Onur Karaman commented on KAFKA-2936: - Hi [~ijuma]. I actually forgot about this and h

[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 ] Flavio Junqueira updated KAFKA-3173: Description: We observed another instance of the problem reported in KAFKA-2300, but this t

[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 ] Flavio Junqueira updated KAFKA-3173: Description: We observed another instance of the problem reported in KAFKA-2300, but this t

[jira] [Created] (KAFKA-3175) topic not accessible after deletion even when delete.topic.enable is disabled

Jun Rao created KAFKA-3175: -- Summary: topic not accessible after deletion even when delete.topic.enable is disabled Key: KAFKA-3175 URL: https://issues.apache.org/jira/browse/KAFKA-3175 Project: Kafka

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124630#comment-15124630 ] Jiangjie Qin commented on KAFKA-3174: - [~ijuma] I just started writing the patch. Shou

[jira] [Updated] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3174: Description: We used org.apache.kafka.common.utils.CRC32 in clients because it has better performan

[jira] [Assigned] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-3174: --- Assignee: Jiangjie Qin > Re-evaluate the CRC32 class performance. > -

[jira] [Assigned] (KAFKA-3175) topic not accessible after deletion even when delete.topic.enable is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat reassigned KAFKA-3175: -- Assignee: Mayuresh Gharat > topic not accessible after deletion even when delete.topic.

[jira] [Commented] (KAFKA-3175) topic not accessible after deletion even when delete.topic.enable is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124643#comment-15124643 ] Jun Rao commented on KAFKA-3175: The issue is that during the controller failover, we call

[jira] [Commented] (KAFKA-3175) topic not accessible after deletion even when delete.topic.enable is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124681#comment-15124681 ] Mayuresh Gharat commented on KAFKA-3175: I am just thinking we have that check in

[jira] [Comment Edited] (KAFKA-3175) topic not accessible after deletion even when delete.topic.enable is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124681#comment-15124681 ] Mayuresh Gharat edited comment on KAFKA-3175 at 1/30/16 3:05 AM: ---

[jira] [Commented] (KAFKA-3175) topic not accessible after deletion even when delete.topic.enable is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124722#comment-15124722 ] Jun Rao commented on KAFKA-3175: It's already doing that. The problem is that initialTopic

[GitHub] kafka pull request: KAFKA-2522: ConsumerGroupCommand writes error ...

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

[jira] [Commented] (KAFKA-2522) ConsumerGroupCommand sends all output to STDOUT

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

[GitHub] kafka pull request: KAFKA-2522: ConsumerGroupCommand writes error ...

GitHub user melan opened a pull request: https://github.com/apache/kafka/pull/840 KAFKA-2522: ConsumerGroupCommand writes error messages to STDERR instead of STDOUT ConsumerGroupCommand sends errors and valuable output to different streams. It simplifies results parsing. @

[jira] [Commented] (KAFKA-2522) ConsumerGroupCommand sends all output to STDOUT

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

[GitHub] kafka pull request: KAFKA-3174: Change Crc32 to use java.util.zip....

GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/841 KAFKA-3174: Change Crc32 to use java.util.zip.CRC32 You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3174 Alternatively y

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

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

[jira] [Updated] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3174: Status: Patch Available (was: Open) > Re-evaluate the CRC32 class performance. > --

[jira] [Updated] (KAFKA-3029) Make class org.apache.kafka.common.TopicPartition Serializable

[ https://issues.apache.org/jira/browse/KAFKA-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3029: - Assignee: Praveen Devarao > Make class org.apache.kafka.common.TopicPartition Seri

[jira] [Updated] (KAFKA-3172) Consumer threads stay in 'Watiting' status and are blocked at consumer poll method

[ https://issues.apache.org/jira/browse/KAFKA-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dany Benjamin updated KAFKA-3172: - Priority: Blocker (was: Major) > Consumer threads stay in 'Watiting' status and are blocked at co

[jira] [Updated] (KAFKA-3172) Consumer threads stay in 'Watiting' status and are blocked at consumer poll method

[ https://issues.apache.org/jira/browse/KAFKA-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dany Benjamin updated KAFKA-3172: - Priority: Critical (was: Blocker) > Consumer threads stay in 'Watiting' status and are blocked at

<    1   2