[jira] [Commented] (KAFKA-3003) The fetch.wait.max.ms is not honored when new log segment rolled for low volume topics.

[ https://issues.apache.org/jira/browse/KAFKA-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208059#comment-15208059 ] James Cheng commented on KAFKA-3003: Would this cause large amounts of interbroker tra

[jira] [Created] (KAFKA-3449) Rename filterOut() to filterNot() to achieve better terminology

Michael Noll created KAFKA-3449: --- Summary: Rename filterOut() to filterNot() to achieve better terminology Key: KAFKA-3449 URL: https://issues.apache.org/jira/browse/KAFKA-3449 Project: Kafka

[jira] [Updated] (KAFKA-3449) Rename filterOut() to filterNot() to achieve better terminology

[ https://issues.apache.org/jira/browse/KAFKA-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Noll updated KAFKA-3449: Fix Version/s: 0.10.0.1 > Rename filterOut() to filterNot() to achieve better terminology >

[jira] [Commented] (KAFKA-3135) Unexpected delay before fetch response transmission

[ https://issues.apache.org/jira/browse/KAFKA-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208129#comment-15208129 ] Krzysiek Ciesielski commented on KAFKA-3135: [~hachikuji] Actually, this error

[jira] [Commented] (KAFKA-3449) Rename filterOut() to filterNot() to achieve better terminology

[ https://issues.apache.org/jira/browse/KAFKA-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208170#comment-15208170 ] Ismael Juma commented on KAFKA-3449: I know we have unstable annotations, but it seems

[jira] [Commented] (KAFKA-3296) All consumer reads hang indefinately

[ https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208201#comment-15208201 ] Simon Cooper commented on KAFKA-3296: - {code}Topic:__consumer_offsetsPartition

[jira] [Updated] (KAFKA-3296) All consumer reads hang indefinately

[ https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3296: --- Fix Version/s: 0.10.0.0 > All consumer reads hang indefinately >

[jira] [Updated] (KAFKA-3296) All consumer reads hang indefinately

[ https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3296: --- Fix Version/s: (was: 0.10.0.0) > All consumer reads hang indefinately > --

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

[ https://issues.apache.org/jira/browse/KAFKA-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3409: --- Reviewer: Guozhang Wang > Mirror maker hangs indefinitely due to commit > ---

Re: [VOTE] KIP-51 - List Connectors REST API

+1 (non-binding) Ismael On Tue, Mar 22, 2016 at 10:46 PM, Ewen Cheslack-Postava wrote: > Since it's pretty minimal, we'd like to squeeze it into 0.10 if possible, > and VOTE threads take 3 days, it was suggested it might make sense to just > kick off voting on this KIP immediately (and restart

Re: Jenkins job for 0.10.0

Thanks Gwen! A quick heads up, the job was slightly changed to match the branch name: https://builds.apache.org/job/kafka-0.10.0-jdk7/ Ismael On Tue, Mar 22, 2016 at 5:43 PM, Gwen Shapira wrote: > Hi Team Kafka, > > Just a quick update - I've created a Jenkins job to test the 0.10.0 branch, >

[jira] [Resolved] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3323. Resolution: Duplicate Closing as duplicate of KAFKA-2024 > Negative offsets in Log Segment Index fi

[jira] [Created] (KAFKA-3450) Producer blocks on send to topic that doesn't exist if auto create is disabled

Michal Turek created KAFKA-3450: --- Summary: Producer blocks on send to topic that doesn't exist if auto create is disabled Key: KAFKA-3450 URL: https://issues.apache.org/jira/browse/KAFKA-3450 Project: K

[jira] [Updated] (KAFKA-3450) Producer blocks on send to topic that doesn't exist if auto create is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Turek updated KAFKA-3450: Priority: Critical (was: Minor) Priority updated from minor to critical. I have just realized that

[jira] [Updated] (KAFKA-3425) Add missing notes to upgrade docs

[ https://issues.apache.org/jira/browse/KAFKA-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3425: --- Reviewer: Gwen Shapira > Add missing notes to upgrade docs > - > >

[jira] [Updated] (KAFKA-3425) Add missing notes to upgrade docs

[ https://issues.apache.org/jira/browse/KAFKA-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3425: --- Summary: Add missing notes to upgrade docs (was: Add KIP-45 note to upgrade docs) > Add missing note

[jira] [Updated] (KAFKA-3434) Add old ConsumerRecord constructor for compatibility

[ https://issues.apache.org/jira/browse/KAFKA-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3434: --- Reviewer: Jun Rao > Add old ConsumerRecord constructor for compatibility > ---

[jira] [Commented] (KAFKA-3450) Producer blocks on send to topic that doesn't exist if auto create is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208431#comment-15208431 ] Michal Turek commented on KAFKA-3450: - Hm, another update... workaround with {{max.blo

Messages corrupted in kafka

Hi I am seeing few messages getting corrupted in kafka, It is not happening frequently and percentage is also very very less (less than 0.1%). Basically i am publishing thrift events in byte array format to kafka topics(with out encoding like base64), and i also see more events than i publish (i c

Fwd: Need Help

Hi, I am trying to run this code for consumer. import java.io.UnsupportedEncodingException; import java.nio.ByteBuffer; import java.util.HashMap; import java.util.List; import java.util.Map; import java.util.Properties; import kafka.consumer.Consumer; import kafka.consumer.ConsumerConfig; import k

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

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

[jira] [Updated] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

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

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208459#comment-15208459 ] Jun Rao commented on KAFKA-3442: [~dana.powers], this issue is fixed now. Could you verify

[GitHub] kafka pull request: KAFKA-3442: Fix FileMessageSet iterator.

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1112 --- 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-3296) All consumer reads hang indefinately

[ https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208491#comment-15208491 ] Jun Rao commented on KAFKA-3296: [~thecoop1984], thanks for the results. We will need to f

[jira] [Updated] (KAFKA-3135) Unexpected delay before fetch response transmission

[ https://issues.apache.org/jira/browse/KAFKA-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3135: --- Fix Version/s: 0.10.0.1 > Unexpected delay before fetch response transmission > --

Re: Request for edit access to Kafka wiki

Hi, I'd also like write access to the wiki page. I have a Swift client I've been working on that I'd like to publish. My confluence user name is kellan.burket. Thanks, Kellan On Tue, Mar 22, 2016 at 9:58 PM, Ganesh Nikam < ganesh.ni...@gslab.com.invalid> wrote: > Hi All, > > > > I want to publi

[jira] [Commented] (KAFKA-3135) Unexpected delay before fetch response transmission

[ https://issues.apache.org/jira/browse/KAFKA-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208512#comment-15208512 ] Raghu Angadi commented on KAFKA-3135: - [~hachikuji], mine is also on Linux with Java8

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

[ https://issues.apache.org/jira/browse/KAFKA-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208531#comment-15208531 ] Tobias commented on KAFKA-3400: --- More research. I've now setup a completely new cluster usin

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

[ https://issues.apache.org/jira/browse/KAFKA-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208542#comment-15208542 ] Tobias commented on KAFKA-3400: --- I also checked the data directories and the only topic to h

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

[ https://issues.apache.org/jira/browse/KAFKA-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208542#comment-15208542 ] Tobias edited comment on KAFKA-3400 at 3/23/16 3:11 PM: I also che

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

See Changes: [junrao] KAFKA-3442; Fix FileMessageSet iterator. -- [...truncated 1591 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest > testCleanShutdownFile PASSED kafka

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

See Changes: [junrao] KAFKA-3442; Fix FileMessageSet iterator. -- [...truncated 1605 lines...] kafka.consumer.ZookeeperConsumerConnectorTest > testConsumerDecoder PASSED kafka.consumer.Zookeepe

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

[ https://issues.apache.org/jira/browse/KAFKA-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208642#comment-15208642 ] Tobias commented on KAFKA-3400: --- I tried building from trunk (0.10.1.0) and recreated the cl

[jira] [Commented] (KAFKA-960) Upgrade Metrics to 3.x

[ https://issues.apache.org/jira/browse/KAFKA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208671#comment-15208671 ] Xavier Stevens commented on KAFKA-960: -- We would be interested in having this still. L

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208721#comment-15208721 ] Dana Powers commented on KAFKA-3442: +1. verified test passes on trunk commit `7af67ce

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

See Changes: [junrao] KAFKA-3442; Fix FileMessageSet iterator. -- [...truncated 3133 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[17] PASSED kafka.log.BrokerCompressionT

[jira] [Updated] (KAFKA-3135) Unexpected delay before fetch response transmission

[ https://issues.apache.org/jira/browse/KAFKA-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3135: --- Priority: Critical (was: Major) > Unexpected delay before fetch response transmission > -

[jira] [Commented] (KAFKA-3135) Unexpected delay before fetch response transmission

[ https://issues.apache.org/jira/browse/KAFKA-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208740#comment-15208740 ] Jason Gustafson commented on KAFKA-3135: [~rangadi] [~kciesielski] Thanks for lett

[GitHub] kafka pull request: KAFKA-3409: handle CommitFailedException in Mi...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1115 --- 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-3409) Mirror maker hangs indefinitely due to commit

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

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208751#comment-15208751 ] Gwen Shapira commented on KAFKA-3442: - Perfect! Thank you [~dana.powers] for testing o

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

[ https://issues.apache.org/jira/browse/KAFKA-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3409. -- Resolution: Fixed Issue resolved by pull request 1115 [https://github.com/apache/kafka/pull/1115

[jira] [Commented] (KAFKA-3003) The fetch.wait.max.ms is not honored when new log segment rolled for low volume topics.

[ https://issues.apache.org/jira/browse/KAFKA-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208764#comment-15208764 ] Jiangjie Qin commented on KAFKA-3003: - In this particular case, the problem was due to

Re: [VOTE] KIP-51 - List Connectors REST API

Very large +1 on re-evaluating the KIP process. I was hoping we can do a meta-kip meeting after the release (Maybe even in-person at Kafka Summit?) to discuss. On Tue, Mar 22, 2016 at 7:59 PM, Grant Henke wrote: > +1 (non-binding) > > I am also a +1 to evaluating the KIP process and ways to mak

[jira] [Created] (KAFKA-3451) Add basic HTML coverage report generation to gradle

Grant Henke created KAFKA-3451: -- Summary: Add basic HTML coverage report generation to gradle Key: KAFKA-3451 URL: https://issues.apache.org/jira/browse/KAFKA-3451 Project: Kafka Issue Type: Sub

[GitHub] kafka pull request: KAFKA-3451: Add basic HTML coverage report gen...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1121 KAFKA-3451: Add basic HTML coverage report generation to gradle You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka coverage Al

[jira] [Commented] (KAFKA-3451) Add basic HTML coverage report generation to gradle

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

[jira] [Commented] (KAFKA-3451) Add basic HTML coverage report generation to gradle

[ https://issues.apache.org/jira/browse/KAFKA-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208786#comment-15208786 ] Grant Henke commented on KAFKA-3451: Attached sample report output. > Add basic HTML

[jira] [Updated] (KAFKA-3451) Add basic HTML coverage report generation to gradle

[ https://issues.apache.org/jira/browse/KAFKA-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3451: --- Status: Patch Available (was: Open) > Add basic HTML coverage report generation to gradle > -

[jira] [Updated] (KAFKA-3451) Add basic HTML coverage report generation to gradle

[ https://issues.apache.org/jira/browse/KAFKA-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3451: --- Attachment: Jacoco-html.zip scoverage.zip > Add basic HTML coverage report generation

Re: [VOTE] KIP-51 - List Connectors REST API

+1 (non-binding) On Wed, Mar 23, 2016 at 10:00 AM, Gwen Shapira wrote: > Very large +1 on re-evaluating the KIP process. > > I was hoping we can do a meta-kip meeting after the release (Maybe even > in-person at Kafka Summit?) to discuss. > > On Tue, Mar 22, 2016 at 7:59 PM, Grant Henke wrote:

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

See Changes: [wangguoz] KAFKA-3409: handle CommitFailedException in MirrorMaker -- [...truncated 1573 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[17] PASSED kafka.log.Br

[GitHub] kafka pull request: KAFKA-3441: 0.10.0 documentation still says "0...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1122 KAFKA-3441: 0.10.0 documentation still says "0.9.0" You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka docs-10 Alternatively y

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

See Changes: [wangguoz] KAFKA-3409: handle CommitFailedException in MirrorMaker -- [...truncated 3153 lines...] at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:947)

[jira] [Commented] (KAFKA-3441) 0.10.0 documentation still says "0.9.0"

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

[jira] [Created] (KAFKA-3452) Support session windows besides time interval windows

Guozhang Wang created KAFKA-3452: Summary: Support session windows besides time interval windows Key: KAFKA-3452 URL: https://issues.apache.org/jira/browse/KAFKA-3452 Project: Kafka Issue Typ

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

See Changes: [wangguoz] KAFKA-3409: handle CommitFailedException in MirrorMaker -- [...truncated 1555 lines...] kafka.integration.AutoOffsetResetTest > testResetToLatestWhenOffsetTooLow PASSED

Re: [VOTE] KIP-51 - List Connectors REST API

+1. On Wed, Mar 23, 2016 at 10:24 AM, Ashish Singh wrote: > +1 (non-binding) > > On Wed, Mar 23, 2016 at 10:00 AM, Gwen Shapira wrote: > > > Very large +1 on re-evaluating the KIP process. > > > > I was hoping we can do a meta-kip meeting after the release (Maybe even > > in-person at Kafka Sum

RE: [VOTE] KIP-51 - List Connectors REST API

+1 (non-binding) +1 for re-evaluating the KIP process. This one went through very quickly, but they can drag on sometimes. > Date: Wed, 23 Mar 2016 11:31:37 -0700 > Subject: Re: [VOTE] KIP-51 - List Connectors REST API > From: wangg...@gmail.com > To: dev

[ANN] Small change to release process

Hey Team Kafka, As you know, our current release process is: * Branch * Change version from 0.10.0.0-SNAPSHOT to 0.10.0.0 * Roll out a release candidate with version 0.10.0.0 * Fix bugs and keep rolling out release candidates * After vote passed and release was published, bump the branch to 0.10.0

[GitHub] kafka pull request: KAFKA-3434: add old constructor to ConsumerRec...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1123 KAFKA-3434: add old constructor to ConsumerRecord You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-3434 Alternatively yo

[jira] [Commented] (KAFKA-3434) Add old ConsumerRecord constructor for compatibility

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

[GitHub] kafka pull request: KAFKA-3441: 0.10.0 documentation still says "0...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1122 --- 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-3441) 0.10.0 documentation still says "0.9.0"

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

Re: [ANN] Small change to release process

Hi Gwen, Is the new release process already decided? If so you can ignore my question below. Since we are making a change to the process. What do you think about publishing release candidates using "RC" in the version? So instead of re-using the 0.10.0.0 tag and using 0.10.0.0-SNAPSHOT as the ver

[jira] [Created] (KAFKA-3453) Transient test failures due to MiniKDC port allocation strategy

Ewen Cheslack-Postava created KAFKA-3453: Summary: Transient test failures due to MiniKDC port allocation strategy Key: KAFKA-3453 URL: https://issues.apache.org/jira/browse/KAFKA-3453 Project

[jira] [Resolved] (KAFKA-3441) 0.10.0 documentation still says "0.9.0"

[ https://issues.apache.org/jira/browse/KAFKA-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KAFKA-3441. Resolution: Fixed > 0.10.0 documentation still says "0.9.0" > --

Re: [ANN] Small change to release process

It was decided (rather unilaterally by your humble release manager), but that doesn't mean decisions can't change :) 1. We can definitely have multiple tags for each separate RC. Actually I think this is better than moving the tag. 2. We can't change release artifacts after the vote, which mean th

Re: [ANN] Small change to release process

Works for me. Thanks for the quick response! On Wed, Mar 23, 2016 at 3:09 PM, Gwen Shapira wrote: > It was decided (rather unilaterally by your humble release manager), but > that doesn't mean decisions can't change :) > > 1. We can definitely have multiple tags for each separate RC. Actually I

[jira] [Updated] (KAFKA-3441) 0.10.0 documentation still says "0.9.0"

[ https://issues.apache.org/jira/browse/KAFKA-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3441: Fix Version/s: 0.10.1.0 > 0.10.0 documentation still says "0.9.0" >

[jira] [Created] (KAFKA-3454) Add Kafka Streams section in documentation

Guozhang Wang created KAFKA-3454: Summary: Add Kafka Streams section in documentation Key: KAFKA-3454 URL: https://issues.apache.org/jira/browse/KAFKA-3454 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-3455) Connect custom processors with the streams DSL

Jonathan Bender created KAFKA-3455: -- Summary: Connect custom processors with the streams DSL Key: KAFKA-3455 URL: https://issues.apache.org/jira/browse/KAFKA-3455 Project: Kafka Issue Type:

[GitHub] kafka pull request: KAFKA-3432; Cluster.update() thread-safety

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1118 --- 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-3432) Cluster.update() thread-safety

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

[jira] [Updated] (KAFKA-3432) Cluster.update() thread-safety

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

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

See Changes: [cshapi] KAFKA-3441: 0.10.0 documentation still says "0.9.0" [wangguoz] KAFKA-3432; Cluster.update() thread-safety -- [...truncated 1769 lines...] jdk1.7.0_51/jre/lib/amd64/libjfxw

[jira] [Updated] (KAFKA-3418) Add section on detecting consumer failures in new consumer javadoc

[ https://issues.apache.org/jira/browse/KAFKA-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3418: --- Description: There still seems to be a lot of confusion about the design of the poll() loop in

[jira] [Work started] (KAFKA-3418) Add section on detecting consumer failures in new consumer javadoc

[ https://issues.apache.org/jira/browse/KAFKA-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3418 started by Jason Gustafson. -- > Add section on detecting consumer failures in new consumer javadoc > --

[jira] [Updated] (KAFKA-3434) Add old ConsumerRecord constructor for compatibility

[ https://issues.apache.org/jira/browse/KAFKA-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3434: --- Status: Patch Available (was: In Progress) > Add old ConsumerRecord constructor for compatibi

[jira] [Work started] (KAFKA-3434) Add old ConsumerRecord constructor for compatibility

[ https://issues.apache.org/jira/browse/KAFKA-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3434 started by Jason Gustafson. -- > Add old ConsumerRecord constructor for compatibility >

[GitHub] kafka pull request: HOTFIX: fix NPE in changelogger

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/1124 HOTFIX: fix NPE in changelogger Fix NPE in StoreChangeLogger caused by a record out of window retention period. @guozhangwang You can merge this pull request into a Git repository by running:

[GitHub] kafka pull request: HOTFIX: fix NPE in changelogger

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

[GitHub] kafka pull request: MINOR: remove streams-smoke-test.sh

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/1125 MINOR: remove streams-smoke-test.sh @guozhangwang You can merge this pull request into a Git repository by running: $ git pull https://github.com/ymatsuda/kafka remove_smoketest_shell_script

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

See Changes: [cshapi] KAFKA-3441: 0.10.0 documentation still says "0.9.0" -- [...truncated 5274 lines...] org.apache.kafka.streams.processor.TopologyBuilderTest > testAddSinkWithSelfParent PASSE

[GitHub] kafka pull request: MINOR: remove streams-smoke-test.sh

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

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

See

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

Any update on this. Gwen since the KIP is adjusted to address the pluggable classes we should make a move on this. Rajini, Can you restart the voting thread. Thanks, Harsha On Wed, Mar 16, 2016, at 06:42 AM, Rajini Sivaram wrote: > As discussed in the KIP meeting yesterday, the scope

[GitHub] kafka pull request: MINOR: Revert 0.10.0 branch to SNAPSHOT per ch...

GitHub user gwenshap opened a pull request: https://github.com/apache/kafka/pull/1126 MINOR: Revert 0.10.0 branch to SNAPSHOT per change in release process You can merge this pull request into a Git repository by running: $ git pull https://github.com/gwenshap/kafka minor-rele

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

See Changes: [wangguoz] HOTFIX: fix NPE in changelogger [wangguoz] MINOR: remove streams-smoke-test.sh -- [...truncated 1557 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompressio

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

See Changes: [wangguoz] KAFKA-3432; Cluster.update() thread-safety [wangguoz] HOTFIX: fix NPE in changelogger -- [...truncated 4389 lines...] kafka.admin.AdminRackAwareTest > testRackAwareExpan

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

See Changes: [wangguoz] HOTFIX: fix NPE in changelogger -- [...truncated 5242 lines...] org.apache.kafka.streams.kstream.internals.KTableKTableOuterJoinTest > testNotSendingOldValue PASSED org

Re: Fallout from upgrading to kafka 0.9.0.0 from 0.8.2.1

More information about the issue: When the issue happens, the controller is always on the 0.9 version Kafka broker. In server.log of other brokers, we can see this kind of error: [2016-03-23 22:36:02,814] ERROR [ReplicaFetcherThread-0-5], Error for partition [topic,208] to broker 5:org.apache.kafka

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

Sorry! Got distracted by the impending release! +1 on the current revision of the KIP. On Wed, Mar 23, 2016 at 3:33 PM, Harsha wrote: > Any update on this. Gwen since the KIP is adjusted to address the > pluggable classes we should make a move on this. > > Rajini, >Can you restart t

[GitHub] kafka pull request: [WIP] KAFKA-3454: add Kafka Streams web docs

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1127 [WIP] KAFKA-3454: add Kafka Streams web docs You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka KStreamsDocs Alternatively

[jira] [Commented] (KAFKA-3454) Add Kafka Streams section in documentation

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

[jira] [Commented] (KAFKA-3453) Transient test failures due to MiniKDC port allocation strategy

[ https://issues.apache.org/jira/browse/KAFKA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209404#comment-15209404 ] Ismael Juma commented on KAFKA-3453: MiniKDC has recently received a fix for something

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

See Changes: [wangguoz] MINOR: remove streams-smoke-test.sh -- [...truncated 3089 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[3] PASSED kafka.log.BrokerCompressionTes

[jira] [Assigned] (KAFKA-3453) Transient test failures due to MiniKDC port allocation strategy

[ https://issues.apache.org/jira/browse/KAFKA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3453: -- Assignee: Ismael Juma > Transient test failures due to MiniKDC port allocation strategy > -

[jira] [Commented] (KAFKA-3453) Transient test failures due to MiniKDC port allocation strategy

[ https://issues.apache.org/jira/browse/KAFKA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209443#comment-15209443 ] Ismael Juma commented on KAFKA-3453: Plan is to update to MiniKDC 2.8.0 when it is rel

  1   2   >