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

[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

[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=15124558#comment-15124558 ] Ismael Juma commented on KAFKA-3174: Becket, are you planning to do this one? I'll take it, if you

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

[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=15124537#comment-15124537 ] Jay Kreps commented on KAFKA-3174: -- This is a great find. It looks like it did become an intrinsic in 1.8

[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

[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

[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

[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

[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

[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=15124563#comment-15124563 ] Onur Karaman commented on KAFKA-2936: - Hi [~ijuma]. I actually forgot about this and have too much on

[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=15124681#comment-15124681 ] Mayuresh Gharat edited comment on KAFKA-3175 at 1/30/16 3:05 AM: - I am

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

[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=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] [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

[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] [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

[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=15124681#comment-15124681 ] Mayuresh Gharat commented on KAFKA-3175: I am just thinking we have that check in the

[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

[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=15124630#comment-15124630 ] Jiangjie Qin commented on KAFKA-3174: - [~ijuma] I just started writing the patch. Should be able to

[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=15124643#comment-15124643 ] Jun Rao commented on KAFKA-3175: The issue is that during the controller failover, we call

[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

[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

[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=15124722#comment-15124722 ] Jun Rao commented on KAFKA-3175: It's already doing that. The problem is that initialTopicsToBeDeleted is

[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-2522) ConsumerGroupCommand sends all output to STDOUT

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

[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

[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

[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=15124555#comment-15124555 ] Ismael Juma commented on KAFKA-3174: Jay, I think you meant

[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

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

[jira] [Commented] (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:comment-tabpanel=15123994#comment-15123994 ] Dany Benjamin commented on KAFKA-3172: -- Even after the consumers are stopped (400) and new consumers

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

See Changes: [me] KAFKA-3029: Mark TopicPartition and OffsetAndMetadata as Serializable [wangguoz] KAFKA-2676: Fix incorrect package name in tests [wangguoz] MINOR: remove the init method from Serdes

[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: - Attachment: jstack.png > Consumer threads stay in 'Watiting' status and are blocked at consumer

[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: - Attachment: jmx_info.png > Consumer threads stay in 'Watiting' status and are blocked at consumer

[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: - Attachment: lagSample.png > Consumer threads stay in 'Watiting' status and are blocked at

[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 >

[jira] [Commented] (KAFKA-3093) Keep track of connector and task status info, expose it via the REST API

[ https://issues.apache.org/jira/browse/KAFKA-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123938#comment-15123938 ] Jason Gustafson commented on KAFKA-3093: [~jinxing6...@126.com] I've started looking at this task.

[jira] [Commented] (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:comment-tabpanel=15123956#comment-15123956 ] Jiangjie Qin commented on KAFKA-1464: - It looks our purpose is to minimize user impact during replica

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

Dany Benjamin created KAFKA-3172: Summary: Consumer threads stay in 'Watiting' status and are blocked at consumer poll method Key: KAFKA-3172 URL: https://issues.apache.org/jira/browse/KAFKA-3172

[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 >

[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

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

Jenkins build is back to normal : kafka_0.9.0_jdk7 #103

See

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

See

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

[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=15124197#comment-15124197 ] Grant Henke commented on KAFKA-3171: Can you try changing `props.put("ack", "all");` to

[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 > -

<    1   2