[jira] [Updated] (KAFKA-3851) Add references to important installation/upgrade notes to release notes

[ https://issues.apache.org/jira/browse/KAFKA-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3851: --- Status: Patch Available (was: Open) > Add references to important installation/upgrade notes to relea

[jira] [Commented] (KAFKA-3789) Upgrade Snappy to fix snappy decompression errors

[ https://issues.apache.org/jira/browse/KAFKA-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395336#comment-15395336 ] Benoit Sigoure commented on KAFKA-3789: --- When is Kafka 0.10.0.1 going to be released

[jira] [Commented] (KAFKA-3789) Upgrade Snappy to fix snappy decompression errors

[ https://issues.apache.org/jira/browse/KAFKA-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395376#comment-15395376 ] Ismael Juma commented on KAFKA-3789: [~tsuna], please see http://search-hadoop.com/m/u

[jira] [Commented] (KAFKA-3789) Upgrade Snappy to fix snappy decompression errors

[ https://issues.apache.org/jira/browse/KAFKA-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395441#comment-15395441 ] Benoit Sigoure commented on KAFKA-3789: --- Thanks, I'm not on kafka-dev so I hadn't se

[jira] [Commented] (KAFKA-3705) Support non-key joining in KTable

[ https://issues.apache.org/jira/browse/KAFKA-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395478#comment-15395478 ] Jan Filipiak commented on KAFKA-3705: - Something that starts happening to us is that f

[jira] [Comment Edited] (KAFKA-3705) Support non-key joining in KTable

[ https://issues.apache.org/jira/browse/KAFKA-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395478#comment-15395478 ] Jan Filipiak edited comment on KAFKA-3705 at 7/27/16 11:24 AM: -

[jira] [Created] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

Alexey Ozeritskiy created KAFKA-3997: Summary: Halting because log truncation is not allowed and suspicious logging Key: KAFKA-3997 URL: https://issues.apache.org/jira/browse/KAFKA-3997 Project: K

[jira] [Updated] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

[ https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-3997: - Description: When follower wants to truncate partition and it is not allowed it print the

[jira] [Updated] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

[ https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-3997: - Description: When follower wants to truncate partition and it is not allowed it print the

[jira] [Updated] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

[ https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-3997: - Status: Patch Available (was: Open) > Halting because log truncation is not allowed and s

[jira] [Updated] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

[ https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-3997: - Attachment: KAFKA-3997.patch > Halting because log truncation is not allowed and suspiciou

[jira] [Updated] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

[ https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-3997: - Description: When follower wants to truncate partition and it is not allowed it print the

[jira] [Updated] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

[ https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-3997: - Description: When follower wants to truncate partition and it is not allowed it prints the

Kafka Streams for Remote Server

Hello, I’ve a simplest ever kafka streams application which just reads from one kafka topic A and write to another topic B. When I run it on my local environment (local zk, local kafka broker, local kafka streams app) everything works fine, topic B created and filled with messages from A If I

[jira] [Updated] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

[ https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-3997: - Issue Type: Improvement (was: Bug) > Halting because log truncation is not allowed and su

Synchronized block in StreamTask

Hi, I've a simple technical question about kafka streams and I don't know if I should use us...@kafka.apache.org or this mailing list. In class org.apache.kafka.streams.processor.internals.StreamTask, the method "process" use a synchronized block but I don't see why, the method doesn't seem to be

[GitHub] kafka pull request #1669: KAFKA-3996: ByteBufferMessageSet.writeTo() should ...

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

[jira] [Commented] (KAFKA-3996) ByteBufferMessageSet.writeTo() should be non-blocking

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

[jira] [Updated] (KAFKA-3996) ByteBufferMessageSet.writeTo() should be non-blocking

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

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395821#comment-15395821 ] William Yu commented on KAFKA-2729: --- We are also seeing this in our production cluster:

[GitHub] kafka pull request #1634: KAFKA-3924: Replacing halt with exit upon LEO mism...

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

[jira] [Commented] (KAFKA-3924) Data loss due to halting when LEO is larger than leader's LEO

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

[jira] [Updated] (KAFKA-3924) Data loss due to halting when LEO is larger than leader's LEO

[ https://issues.apache.org/jira/browse/KAFKA-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3924: --- Resolution: Fixed Fix Version/s: 0.10.0.1 Status: Resolved (was: Patch Available) Issue res

[jira] [Created] (KAFKA-3998) reuse connection to join group lead to not aware other members

Jerome Xue created KAFKA-3998: - Summary: reuse connection to join group lead to not aware other members Key: KAFKA-3998 URL: https://issues.apache.org/jira/browse/KAFKA-3998 Project: Kafka Issue

Build failed in Jenkins: kafka-0.10.0-jdk7 #164

See Changes: [junrao] KAFKA-3996; ByteBufferMessageSet.writeTo() should be non-blocking -- [...truncated 1700 lines...] kafka.KafkaTest > testGetKafkaConfigFromArgsWrongSetValue PASSED kafka.K

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395915#comment-15395915 ] James Carnegie commented on KAFKA-2729: --- That's our experience, though the only othe

[jira] [Commented] (KAFKA-2630) Add Namespaces to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395933#comment-15395933 ] Vahid Hashemian commented on KAFKA-2630: [~singhashish] I am wondering what the st

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395953#comment-15395953 ] Kane Kim commented on KAFKA-2729: - This is hitting us badly on kafka 0.10.0.0, it doesn't

[jira] [Created] (KAFKA-3999) Consumer bytes-fetched metric uses decompressed message size

Jason Gustafson created KAFKA-3999: -- Summary: Consumer bytes-fetched metric uses decompressed message size Key: KAFKA-3999 URL: https://issues.apache.org/jira/browse/KAFKA-3999 Project: Kafka

[jira] [Created] (KAFKA-4000) Consumer per-topic metrics do not aggregate partitions from the same topic

Jason Gustafson created KAFKA-4000: -- Summary: Consumer per-topic metrics do not aggregate partitions from the same topic Key: KAFKA-4000 URL: https://issues.apache.org/jira/browse/KAFKA-4000 Project:

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

See Changes: [junrao] KAFKA-3996; ByteBufferMessageSet.writeTo() should be non-blocking [junrao] KAFKA-3924; Replacing halt with exit upon LEO mismatch to trigger gra��� -- [...truncated 12971

Re: [DISCUSS] KIP-70: Revise Partition Assignment Semantics on New Consumer's Subscription Change

Ismael, I sent a message to user mailing lists of Spark and Storm a couple of days ago and have received one response so far. Thread on Spark mailing list: https://www.mail-archive.com/user@spark.apache.org/msg54309.html Thread on Storm mailing list: https://www.mail-archive.com/user@storm.apac

Re: [DISCUSS] KIP-70: Revise Partition Assignment Semantics on New Consumer's Subscription Change

Sounds good Vahid, thanks for doing this. :) Ismael On Wed, Jul 27, 2016 at 6:29 PM, Vahid S Hashemian < vahidhashem...@us.ibm.com> wrote: > Ismael, > > I sent a message to user mailing lists of Spark and Storm a couple of days > ago and have received one response so far. > Thread on Spark maili

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

See Changes: [junrao] KAFKA-3996; ByteBufferMessageSet.writeTo() should be non-blocking -- [...truncated 1727 lines...] kafka.api.SslProducerSendTest > testSendCompressedMessageWithCreateTime STA

Jenkins build is back to normal : kafka-0.10.0-jdk7 #165

See

[jira] [Created] (KAFKA-4001) Improving join semantics in Kafka Stremas

Matthias J. Sax created KAFKA-4001: -- Summary: Improving join semantics in Kafka Stremas Key: KAFKA-4001 URL: https://issues.apache.org/jira/browse/KAFKA-4001 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-3590) KafkaConsumer fails with "Messages are rejected since there are fewer in-sync replicas than required." when polling

[ https://issues.apache.org/jira/browse/KAFKA-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Cote updated KAFKA-3590: --- Component/s: (was: clients) consumer > KafkaConsumer fails with "Messages are rej

[jira] [Commented] (KAFKA-3590) KafkaConsumer fails with "Messages are rejected since there are fewer in-sync replicas than required." when polling

[ https://issues.apache.org/jira/browse/KAFKA-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396213#comment-15396213 ] Dustin Cote commented on KAFKA-3590: [~salaev] it looks like this is occurring in a Sy

[jira] [Assigned] (KAFKA-3590) KafkaConsumer fails with "Messages are rejected since there are fewer in-sync replicas than required." when polling

[ https://issues.apache.org/jira/browse/KAFKA-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Cote reassigned KAFKA-3590: -- Assignee: Dustin Cote > KafkaConsumer fails with "Messages are rejected since there are fewer i

Jenkins build is back to normal : kafka-trunk-jdk8 #779

See

[GitHub] kafka pull request #1636: KAFKA-3185: Allow users to cleanup internal Kafka ...

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

[jira] [Commented] (KAFKA-3185) Allow users to cleanup internal data

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

[jira] [Updated] (KAFKA-3185) Allow users to cleanup internal data

[ https://issues.apache.org/jira/browse/KAFKA-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3185: - Resolution: Fixed Fix Version/s: (was: 0.10.1.0) 0.10.0.1

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

[ https://issues.apache.org/jira/browse/KAFKA-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-3290: Assignee: Ewen Cheslack-Postava (was: Jason Gustafson) > WorkerSourceTask

[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&focusedCommentId=15396402#comment-15396402 ] Ewen Cheslack-Postava commented on KAFKA-3290: -- Going to close this as it has

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

[ https://issues.apache.org/jira/browse/KAFKA-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3290. -- Resolution: Fixed > WorkerSourceTask testCommit transient failure >

[jira] [Commented] (KAFKA-3705) Support non-key joining in KTable

[ https://issues.apache.org/jira/browse/KAFKA-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396491#comment-15396491 ] Guozhang Wang commented on KAFKA-3705: -- We are fixing this issue right now on the con

[jira] [Comment Edited] (KAFKA-3705) Support non-key joining in KTable

[ https://issues.apache.org/jira/browse/KAFKA-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396491#comment-15396491 ] Guozhang Wang edited comment on KAFKA-3705 at 7/27/16 10:03 PM:

[jira] [Commented] (KAFKA-3705) Support non-key joining in KTable

[ https://issues.apache.org/jira/browse/KAFKA-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396498#comment-15396498 ] Jan Filipiak commented on KAFKA-3705: - The change doesn't seem to be in all the places

[jira] [Assigned] (KAFKA-3994) Deadlock between consumer heartbeat expiration and offset commit.

[ https://issues.apache.org/jira/browse/KAFKA-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-3994: -- Assignee: Jason Gustafson > Deadlock between consumer heartbeat expiration and offset c

[jira] [Commented] (KAFKA-3705) Support non-key joining in KTable

[ https://issues.apache.org/jira/browse/KAFKA-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396508#comment-15396508 ] Guozhang Wang commented on KAFKA-3705: -- Yeah currently we do not have a windowed-stre

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

See Changes: [wangguoz] KAFKA-3185: Allow users to cleanup internal Kafka Streams data -- [...truncated 9062 lines...] kafka.log.LogCleanerIntegrationTest > cleanerTest[2] PASSED kafka.log.LogC

[GitHub] kafka pull request #1671: KAFKA-3185: [Streams] Added Kafka Streams Applicat...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/1671 KAFKA-3185: [Streams] Added Kafka Streams Application Reset Tool You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka resetTool-0.10.0.1 A

[jira] [Commented] (KAFKA-3185) Allow users to cleanup internal data

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

Re: Kafka Streams for Remote Server

Misha, Did you pre-create the sink topic before starting your application or you are relying on the broker-side auto-create for that topic? If you are relying on auto-create, then there is a transient period where the topic is created but the metadata has not been propagated to the brokers so the

Re: Synchronized block in StreamTask

Hello Pierre, Thanks for pointing this out. Good question actually, I think it is safe to remove the synchronization block. Mind filing a one-liner PR? Guozhang On Wed, Jul 27, 2016 at 2:48 AM, Pierre Coquentin < pierre.coquen...@gmail.com> wrote: > Hi, > > I've a simple technical question abo

[GitHub] kafka pull request #1670: KAFKA-3851: Automate release notes and include lin...

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

[jira] [Commented] (KAFKA-3851) Add references to important installation/upgrade notes to release notes

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

[jira] [Updated] (KAFKA-3851) Add references to important installation/upgrade notes to release notes

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

[GitHub] kafka pull request #1671: KAFKA-3185: [Streams] Added Kafka Streams Applicat...

Github user mjsax closed the pull request at: https://github.com/apache/kafka/pull/1671 --- 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-3185) Allow users to cleanup internal data

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

[jira] [Created] (KAFKA-4002) task.open() should be invoked in case that 0 partitions is assigned to task.

Liquan Pei created KAFKA-4002: - Summary: task.open() should be invoked in case that 0 partitions is assigned to task. Key: KAFKA-4002 URL: https://issues.apache.org/jira/browse/KAFKA-4002 Project: Kafka

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

See Changes: [wangguoz] KAFKA-3185: Allow users to cleanup internal Kafka Streams data -- [...truncated 2629 lines...] kafka.api.PlaintextConsumerTest > testCommitMetadata FAILED java.lang.O

[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 ] Ewen Cheslack-Postava updated KAFKA-3190: - Fix Version/s: (was: 0,10.0.2) 0.10.0.2 > KafkaProducer sho

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

See Changes: [ismael] KAFKA-3851; Automate release notes and include links to upgrade notes -- [...truncated 11689 lines...] org.apache.kafka.streams.state.internals.RocksDBWindowStoreTest > t

[jira] [Updated] (KAFKA-3987) Allow configuration of the hash algorithm used by the LogCleaner's offset map

[ https://issues.apache.org/jira/browse/KAFKA-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luciano Afranllie updated KAFKA-3987: - Reviewer: Shikhar Bhushan Status: Patch Available (was: Open) > Allow configuration

Build failed in Jenkins: kafka-0.10.0-jdk7 #166

See Changes: [wangguoz] KAFKA-3185: [Streams] Added Kafka Streams Application Reset Tool [ismael] KAFKA-3851; Automate release notes and include links to upgrade notes -- [...truncated 843 line