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

See Changes: [jason] KAFKA-4387; KafkaConsumer should properly handle interrupts -- [...truncated 8000 lines...] kafka.integration.SaslPlaintextTopicMetadataTest > testGetAllTopicMetadata PASSE

[jira] [Updated] (KAFKA-4470) Exception (java.lang.RuntimeException) encountered during startup: org.codehaus.jackson.JsonParseException:

[ https://issues.apache.org/jira/browse/KAFKA-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JianwenSun updated KAFKA-4470: -- Priority: Blocker (was: Major) > Exception (java.lang.RuntimeException) encountered during startup: >

[jira] [Created] (KAFKA-4470) Exception (java.lang.RuntimeException) encountered during startup: org.codehaus.jackson.JsonParseException:

JianwenSun created KAFKA-4470: - Summary: Exception (java.lang.RuntimeException) encountered during startup: org.codehaus.jackson.JsonParseException: Key: KAFKA-4470 URL: https://issues.apache.org/jira/browse/KAFKA-44

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707668#comment-15707668 ] James Cheng commented on KAFKA-3042: If KAFKA-4443 in fact solves this issue, then I'm

Re: [DISCUSS] 0.10.1.1 Plan

Hi Guozhang, My suggestion was to not add kafka_2.12-0.10.1.0.tgz to downloads.html but to still run the build to generate the maven artefacts for 2.12 and still publish those to maven central. That would allow projects with binary dependencies on kafka to obtain the required jars but hide awa

Re: [VOTE] KIP-93: Improve invalid timestamp handling in Kafka Streams

+1 (binding). Also, see my notes in discussion thread around future compatibility discussions for breaking plugin interface changes like this. -Ewen On Tue, Nov 29, 2016 at 3:54 PM, Guozhang Wang wrote: > +1. > > On Tue, Nov 29, 2016 at 11:05 AM, Bill Bejeck wrote: > > > +1 (non-binding) > >

Re: [DISCUSS] KIP-93: Improve invalid timestamp handling in Kafka Streams

I think this looks reasonable, but just a more general note on compatibility -- I think it's worth trying to clarify what types of compatibility we're trying to achieve. Guozhang's 1 & 2 give an important breakdown (compile vs runtime compatibility). For the type of change described here, I think i

Re: [DISCUSS] 0.10.1.1 Plan

@Ignacio Solis The commit you mentioned was not intended for 0.10.1 but only for trunk (and there is a related KIP for this API change), but mistakenly gets leaked in and was already reverted. @Bernard Leach Could you elaborate on "instead simply publish the artifacts to maven central"? Currentl

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

See

[GitHub] kafka pull request #2191: KAFKA-4447: Controller resigned but it also acts a...

GitHub user xiguantiaozhan opened a pull request: https://github.com/apache/kafka/pull/2191 KAFKA-4447: Controller resigned but it also acts as a controller for a long time You can merge this pull request into a Git repository by running: $ git pull https://github.com/xiguant

[jira] [Commented] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time

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

Re: [DISCUSS] KIP-95: Incremental Batch Processing for Kafka Streams

Thanks for your input. To clarify: the main reason to add the metadata topic is to cope with subtopologies that are connected via intermediate topic (either user-defined via through() or internally created for data repartitioning). Without this handling, the behavior would be odd and user experie

[jira] [Resolved] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-3042. - Resolution: Duplicate Assignee: Dong Lin The problem may have been solved in KAFKA-4443. > updateIs

[jira] [Updated] (KAFKA-4463) Setup travis-ci integration for ducktape tests

[ https://issues.apache.org/jira/browse/KAFKA-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4463: - Fix Version/s: (was: 0.10.1.1) 0.10.2.0 > Setup travis-ci integration for d

[jira] [Updated] (KAFKA-4466) Add support to ducktape to run only a part of all tests

[ https://issues.apache.org/jira/browse/KAFKA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4466: - Fix Version/s: (was: 0.10.1.1) 0.10.2.0 > Add support to ducktape to run on

[jira] [Updated] (KAFKA-4467) Run tests on travis-ci using docker

[ https://issues.apache.org/jira/browse/KAFKA-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4467: - Fix Version/s: (was: 0.10.1.1) 0.10.2.0 > Run tests on travis-ci using dock

[jira] [Updated] (KAFKA-4465) Create docker image and scripts for running tests locally

[ https://issues.apache.org/jira/browse/KAFKA-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4465: - Fix Version/s: (was: 0.10.1.1) 0.10.2.0 > Create docker image and scripts f

[jira] [Updated] (KAFKA-4387) KafkaConsumer will enter an infinite loop if the polling thread is interrupted, and either commitSync or committed is called

[ https://issues.apache.org/jira/browse/KAFKA-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4387: --- Resolution: Fixed Fix Version/s: 0.10.2.0 Status: Resolved (was: Patch Avail

[jira] [Commented] (KAFKA-4387) KafkaConsumer will enter an infinite loop if the polling thread is interrupted, and either commitSync or committed is called

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

[GitHub] kafka pull request #2110: KAFKA-4387: Fix KafkaConsumer not responding corre...

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

Re: [DISCUSS] KIP-96 - Add per partition metrics for in-sync and assigned replica count

This seems useful, +1 On Tue, Nov 29, 2016 at 5:39 AM Ismael Juma wrote: > Hi Xavier, > > Thanks for the KIP. Sounds good to me. > > Ismael > > On Tue, Nov 29, 2016 at 12:40 AM, Xavier Léauté > wrote: > > > Hi, > > > > I created KIP-96 to propose per partition in-sync / assigned replica > > met

Re: [DISCUSS] KIP-95: Incremental Batch Processing for Kafka Streams

Thanks for initiating this. I think this is a good first step towards unifying batch and stream processing in Kafka. I understood this capability to be simple yet very useful; it allows a Streams program to process a log, in batch, in arbitrary windows defined by the difference between the HW and

Re: [VOTE] KIP-85: Dynamic JAAS configuration for Kafka clients

Super useful, thanks Rajini. +1 On Tue, Nov 29, 2016 at 8:11 AM Rajini Sivaram wrote: > I have added this to the KIP. > > Thanks, > > Rajini > > On Tue, Nov 29, 2016 at 12:14 PM, Ismael Juma wrote: > > > One more thing: we are using the PASSWORD config type to avoid exposing > > passwords. This

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707407#comment-15707407 ] Dong Lin commented on KAFKA-3042: - We recently made a fix in Kafka that may have the addre

[jira] [Commented] (KAFKA-4403) Update KafkaBasedLog to use new endOffsets consumer API

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

[jira] [Resolved] (KAFKA-4403) Update KafkaBasedLog to use new endOffsets consumer API

[ https://issues.apache.org/jira/browse/KAFKA-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-4403. Resolution: Fixed Fix Version/s: 0.10.2.0 Issue resolved by pull request 2176 [https:

[GitHub] kafka pull request #2176: KAFKA-4403 Update KafkaBasedLog to use new endOffs...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2176 --- 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] [Updated] (KAFKA-3893) Kafka Broker ID disappears from /brokers/ids

[ https://issues.apache.org/jira/browse/KAFKA-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rekha Joshi updated KAFKA-3893: --- Summary: Kafka Broker ID disappears from /brokers/ids (was: Kafka Broker ID disappears from /borkers/

[jira] [Updated] (KAFKA-3893) Kafka Broker ID disappears from /borkers/ids

[ https://issues.apache.org/jira/browse/KAFKA-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rekha Joshi updated KAFKA-3893: --- Summary: Kafka Broker ID disappears from /borkers/ids (was: Kafka Borker ID disappears from /borkers/

[jira] [Comment Edited] (KAFKA-3893) Kafka Borker ID disappears from /borkers/ids

[ https://issues.apache.org/jira/browse/KAFKA-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15616914#comment-15616914 ] Rekha Joshi edited comment on KAFKA-3893 at 11/30/16 2:58 AM: --

[jira] [Comment Edited] (KAFKA-4443) Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest during failover

[ https://issues.apache.org/jira/browse/KAFKA-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707330#comment-15707330 ] Dong Lin edited comment on KAFKA-4443 at 11/30/16 2:55 AM: --- [~ju

[jira] [Commented] (KAFKA-4443) Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest during failover

[ https://issues.apache.org/jira/browse/KAFKA-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707330#comment-15707330 ] Dong Lin commented on KAFKA-4443: - [~junrao] Sure. I just updated the description to corre

[jira] [Commented] (KAFKA-4469) Consumer throughput regression caused by decrease in max.poll.records

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

[GitHub] kafka pull request #2190: KAFKA-4469: Fix consumer performance regression fr...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/2190 KAFKA-4469: Fix consumer performance regression from unneeded list copy You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707226#comment-15707226 ] Brady Vidovic commented on KAFKA-1194: -- I have downloaded the build and will test it

[jira] [Comment Edited] (KAFKA-4405) Kafka consumer improperly send prefetch request

[ https://issues.apache.org/jira/browse/KAFKA-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707215#comment-15707215 ] ysysberserk edited comment on KAFKA-4405 at 11/30/16 1:52 AM: --

[jira] [Commented] (KAFKA-4405) Kafka consumer improperly send prefetch request

[ https://issues.apache.org/jira/browse/KAFKA-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707215#comment-15707215 ] ysysberserk commented on KAFKA-4405: Oh, I am sorry that I only read the code and did

[jira] [Created] (KAFKA-4469) Consumer throughput regression caused by decrease in max.poll.records

Jason Gustafson created KAFKA-4469: -- Summary: Consumer throughput regression caused by decrease in max.poll.records Key: KAFKA-4469 URL: https://issues.apache.org/jira/browse/KAFKA-4469 Project: Kafk

Re: [DISCUSS] 0.10.1.1 Plan

Sorry for my misunderstanding, I assumed the request to include the keyword removal came from you. And it is always good to know what versions LinkedIn are running, you guys always serve as somewhat of a gold standard to the community :) On Tue, Nov 29, 2016 at 5:32 PM, Ignacio Solis wrote: > I

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

See Changes: [me] KAFKA-4397: Refactor Connect backing stores for thread safety -- [...truncated 12181 lines...] org.apache.kafka.common.record.RecordTest > testChecksum[190] PASSED org.apache.

Re: [DISCUSS] 0.10.1.1 Plan

I don't think anybody from LinkedIn asked for features on this release. We just jumped in at the discussion of including a patch which was not a bug fix and whether it mattered. Having said that, the internal release we're working on came off the 0.10.1 branch with a few internal hotfix patches a

Re: [DISCUSS] 0.10.1.1 Plan

btw. is LinkedIn no longer running from trunk? I'm not used to LinkedIn employees requesting specific patches to be included in a bugfix release. Any discussion on the content of any release is obviously welcome, I'm just wondering if there was a change in policy. On Tue, Nov 29, 2016 at 2:17 PM,

[jira] [Commented] (KAFKA-4468) Correctly calculate the window end timestamp after read from state stores

[ https://issues.apache.org/jira/browse/KAFKA-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707119#comment-15707119 ] Bill Bejeck commented on KAFKA-4468: Picking this one up. > Correctly calculate the w

[jira] [Assigned] (KAFKA-4468) Correctly calculate the window end timestamp after read from state stores

[ https://issues.apache.org/jira/browse/KAFKA-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck reassigned KAFKA-4468: -- Assignee: Bill Bejeck > Correctly calculate the window end timestamp after read from state stor

Re: [DISCUSS] KIP-97: Improved Kafka Client RPC Compatibility Policy

On Tue, Nov 29, 2016 at 4:11 PM, Colin McCabe wrote: > On Tue, Nov 29, 2016, at 11:39, Ashish Singh wrote: > > Hello Colin, > > > > In the KIP you mentioned that currently the client uses supported api > > versions information to check if the server supports its desired > > versions. > > Not sure

[jira] [Updated] (KAFKA-4443) Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest during failover

[ https://issues.apache.org/jira/browse/KAFKA-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4443: Description: Currently in onControllerFailover(), controller will startup replicaStatemachine and partition

Re: [DISCUSS] KIP-97: Improved Kafka Client RPC Compatibility Policy

On Tue, Nov 29, 2016, at 11:39, Ashish Singh wrote: > Hello Colin, > > In the KIP you mentioned that currently the client uses supported api > versions information to check if the server supports its desired > versions. > Not sure, if that is true. I had put together a PR for KAFKA-3600, to do > t

[jira] [Created] (KAFKA-4468) Correctly calculate the window end timestamp after read from state stores

Guozhang Wang created KAFKA-4468: Summary: Correctly calculate the window end timestamp after read from state stores Key: KAFKA-4468 URL: https://issues.apache.org/jira/browse/KAFKA-4468 Project: Kafk

Re: [VOTE] KIP-93: Improve invalid timestamp handling in Kafka Streams

+1. On Tue, Nov 29, 2016 at 11:05 AM, Bill Bejeck wrote: > +1 (non-binding) > > Thanks, > > Bill > > On Tue, Nov 29, 2016 at 1:34 PM, Matthias J. Sax > wrote: > > > I’d like to start the voting process for KIP-93: > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > > 93%3A+Improve+

Re: [DISCUSS] KIP-94: Session Windows

Very nice KIP! Couple of comments: 1) Current window API is as follows: > JoinWindows.of(timeDifference).before(timeDifference).after(timeDifference) > TimeWindows.of(size).advanceBy(interval) > UnlimitedWindow.of().startOn(start) To align with this scheme, I think it would be better to use th

[jira] [Commented] (KAFKA-4397) Refactor Connect backing stores for thread-safety

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

[GitHub] kafka pull request #2123: KAFKA-4397: Refactor Connect backing stores for th...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2123 --- 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] [Resolved] (KAFKA-4397) Refactor Connect backing stores for thread-safety

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

[jira] [Commented] (KAFKA-4443) Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest during failover

[ https://issues.apache.org/jira/browse/KAFKA-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706867#comment-15706867 ] Ismael Juma commented on KAFKA-4443: The fix version should be 0.10.2.0, right? The PR

[jira] [Resolved] (KAFKA-4415) Reduce time to create and send MetadataUpdateRequest

[ https://issues.apache.org/jira/browse/KAFKA-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-4415. - Resolution: Fixed > Reduce time to create and send MetadataUpdateRequest > ---

[jira] [Updated] (KAFKA-4415) Reduce time to create and send MetadataUpdateRequest

[ https://issues.apache.org/jira/browse/KAFKA-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4415: Affects Version/s: 0.10.1.0 Fix Version/s: 0.10.1.1 > Reduce time to create and send Metadat

[jira] [Updated] (KAFKA-4443) Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest during failover

[ https://issues.apache.org/jira/browse/KAFKA-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4443: Affects Version/s: 0.10.1.0 Fix Version/s: 0.10.1.1 > Controller should send UpdateMetadataR

[jira] [Resolved] (KAFKA-4443) Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest during failover

[ https://issues.apache.org/jira/browse/KAFKA-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-4443. - Resolution: Fixed > Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest > d

Re: [DISCUSS] 0.10.1.1 Plan

OK, so it seems like there are no changes that break compatibility in the 0.10.1 branch since we offer no compatibility guarantees for logging output. That's good. :) About the removal of final, it happened in trunk and it doesn't seem like anyone is still asking for it to be included in the 0.10.

[jira] [Commented] (KAFKA-4271) The console consumer fails on Windows with new consumer is used

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

[jira] [Updated] (KAFKA-4271) The console consumer fails on Windows with new consumer is used

[ https://issues.apache.org/jira/browse/KAFKA-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-4271: --- Status: Patch Available (was: Open) > The console consumer fails on Windows with new consumer

[jira] [Assigned] (KAFKA-4271) The console consumer fails on Windows with new consumer is used

[ https://issues.apache.org/jira/browse/KAFKA-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-4271: -- Assignee: Vahid Hashemian > The console consumer fails on Windows with new consumer is

[GitHub] kafka pull request #2189: KAFKA-4271: Fix the server start script for Window...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/2189 KAFKA-4271: Fix the server start script for Windows to run normally on a 32-bit OS Without this fix the new consumer fails to run on a 32-bit Windows OS. You can merge this pull request into

Re: [DISCUSS] 0.10.1.1 Plan

The commit you mentioned was corrupted and corrected via https://git-wip-us.apache.org/repos/asf?p=kafka.git;a=commit;h=cc62b4f844ca16eee974e75b736af87b7532de0d The code change got reverted. -Matthias On 11/29/16 1:35 PM, Ignacio Solis wrote: > Sorry, that was a hasty reply. There are also vari

Re: [DISCUSS] 0.10.1.1 Plan

Sorry, that was a hasty reply. There are also various logging things that change format. This could break parsers. None of them are important, my only argument is that the final keyword removal is not important either. Nacho On Tue, Nov 29, 2016 at 1:25 PM, Ignacio Solis wrote: > https://git

Re: [DISCUSS] 0.10.1.1 Plan

https://git-wip-us.apache.org/repos/asf?p=kafka.git;a=commit;h=10cfc1628df024f7596d3af5c168fa90f59035ca On Tue, Nov 29, 2016 at 1:24 PM, Ismael Juma wrote: > Which changes break compatibility in the 0.10.1 branch? It would be good to > fix before the release goes out. > > Ismael > > On 29 Nov 20

Re: [DISCUSS] 0.10.1.1 Plan

Which changes break compatibility in the 0.10.1 branch? It would be good to fix before the release goes out. Ismael On 29 Nov 2016 9:09 pm, "Ignacio Solis" wrote: > Some of the changes in the 0.10.1 branch already are not bug fixes. Some > break compatibility. > > Having said that, at this leve

Re: [DISCUSS] 0.10.1.1 Plan

Some of the changes in the 0.10.1 branch already are not bug fixes. Some break compatibility. Having said that, at this level we should maintain a stable API and leave any changes for real version bumps. This should be only a bugfix release. Nacho On Tue, Nov 29, 2016 at 8:35 AM, Ismael Juma

[jira] [Assigned] (KAFKA-4458) Add per partition metrics for in-sync and assigned replica count

[ https://issues.apache.org/jira/browse/KAFKA-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté reassigned KAFKA-4458: Assignee: Xavier Léauté > Add per partition metrics for in-sync and assigned replica count

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

See Changes: [wangguoz] KAFKA-4427: Skip topic groups with no tasks [me] MINOR: Make release notes script check resolutions to avoid spurious [becket.qin] KAFKA-4415; Reduce time to create and send UpdateMetadataRequest

[jira] [Commented] (KAFKA-4271) The console consumer fails on Windows with new consumer is used

[ https://issues.apache.org/jira/browse/KAFKA-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706513#comment-15706513 ] Vahid Hashemian commented on KAFKA-4271: [~yuyan] Thanks for the pointer. I can co

Re: [DISCUSS] KIP-82 - Add Record Headers

I'm ok with 32 bit keys and leaving the interpretation out of this discussion/KIP. Nacho On Tue, Nov 29, 2016 at 3:35 AM, Michael Pearce wrote: > I assume, that after a period of a week, that there is no concerns now > with points 1, and 2 and now we have agreement that headers are useful and >

[jira] [Commented] (KAFKA-4415) Reduce time to create and send MetadataUpdateRequest

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

[GitHub] kafka pull request #2169: KAFKA-4415; Reduce time to create and send Metadat...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2169 --- 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-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:comment-tabpanel&focusedCommentId=15706415#comment-15706415 ] Soumyajit Sahu commented on KAFKA-3123: --- I am closing this previously opened (and no

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15706410#comment-15706410 ] ASF GitHub Bot commented on KAFKA-3123: --- Github user soumyajit-sahu closed the pull

[GitHub] kafka pull request #1028: KAFKA-3123: Follower Broker cannot start if offset...

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

Re: [DISCUSS] KIP-97: Improved Kafka Client RPC Compatibility Policy

Hello Colin, In the KIP you mentioned that currently the client uses supported api versions information to check if the server supports its desired versions. Not sure, if that is true. I had put together a PR for KAFKA-3600, to do that, but it never went in. Also, I could not find how you plan to

[GitHub] kafka pull request #2174: MINOR: Make release notes script check resolutions...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2174 --- 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] [Created] (KAFKA-4467) Run tests on travis-ci using docker

Raghav Kumar Gautam created KAFKA-4467: -- Summary: Run tests on travis-ci using docker Key: KAFKA-4467 URL: https://issues.apache.org/jira/browse/KAFKA-4467 Project: Kafka Issue Type: Sub

[jira] [Created] (KAFKA-4466) Add support to ducktape to run only a part of all tests

Raghav Kumar Gautam created KAFKA-4466: -- Summary: Add support to ducktape to run only a part of all tests Key: KAFKA-4466 URL: https://issues.apache.org/jira/browse/KAFKA-4466 Project: Kafka

[jira] [Commented] (KAFKA-4464) Clean shutdown of broker fails due to controller error

[ https://issues.apache.org/jira/browse/KAFKA-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706283#comment-15706283 ] Xavier Lange commented on KAFKA-4464: - Here is my kafka broker config: {code} kafka@8

[jira] [Created] (KAFKA-4465) Create docker image and scripts for running tests locally

Raghav Kumar Gautam created KAFKA-4465: -- Summary: Create docker image and scripts for running tests locally Key: KAFKA-4465 URL: https://issues.apache.org/jira/browse/KAFKA-4465 Project: Kafka

[jira] [Updated] (KAFKA-4462) Improved Kafka Client Compatibility Policy

[ https://issues.apache.org/jira/browse/KAFKA-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-4462: --- Description: A proposal to improve the compatibility policy of the Kafka client by supporting

[jira] [Updated] (KAFKA-4464) Clean shutdown of broker fails due to controller error

[ https://issues.apache.org/jira/browse/KAFKA-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Lange updated KAFKA-4464: Affects Version/s: 0.10.1.0 > Clean shutdown of broker fails due to controller error > -

[jira] [Created] (KAFKA-4464) Clean shutdown of broker fails due to controller error

Xavier Lange created KAFKA-4464: --- Summary: Clean shutdown of broker fails due to controller error Key: KAFKA-4464 URL: https://issues.apache.org/jira/browse/KAFKA-4464 Project: Kafka Issue Type

[jira] [Commented] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706252#comment-15706252 ] Onur Karaman commented on KAFKA-4447: - Hey [~guozhang]. I've been working on a detaile

[jira] [Created] (KAFKA-4463) Setup travis-ci integration for ducktape tests

Raghav Kumar Gautam created KAFKA-4463: -- Summary: Setup travis-ci integration for ducktape tests Key: KAFKA-4463 URL: https://issues.apache.org/jira/browse/KAFKA-4463 Project: Kafka Issu

[jira] [Resolved] (KAFKA-4427) Skip topicGroups with no tasks

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

Re: [VOTE] KIP-93: Improve invalid timestamp handling in Kafka Streams

+1 (non-binding) Thanks, Bill On Tue, Nov 29, 2016 at 1:34 PM, Matthias J. Sax wrote: > I’d like to start the voting process for KIP-93: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 93%3A+Improve+invalid+timestamp+handling+in+Kafka+Streams > > -Matthias > >

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706222#comment-15706222 ] Soumyajit Sahu commented on KAFKA-1194: --- Thanks for confirming that [~haraldk]. Glad

Re: [DISCUSS] KIP-97: Improved Kafka Client RPC Compatibility Policy

Sorry, that link should be: https://cwiki.apache.org/confluence/display/KAFKA/KIP-97%3A+Improved+Kafka+Client+RPC+Compatibility+Policy On Tue, Nov 29, 2016, at 11:04, Colin McCabe wrote: > Hi all, > > I've been thinking about a KIP to improve the Kafka client's > compatibility policy. If you'r

[DISCUSS] KIP-97: Improved Kafka Client RPC Compatibility Policy

Hi all, I've been thinking about a KIP to improve the Kafka client's compatibility policy. If you're interested, please check out: https://cwiki.apache.org/confluence/display/KAFKA/KIP-97%3A+Improved+Kafka+Compatibility+Policy cheers, Colin

[jira] [Commented] (KAFKA-1696) Kafka should be able to generate Hadoop delegation tokens

[ https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706209#comment-15706209 ] Ashish K Singh commented on KAFKA-1696: --- [~omkreddy] would you be able to provide an

[jira] [Commented] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706205#comment-15706205 ] Guozhang Wang commented on KAFKA-4447: -- About the controller re-write: I do not know

[jira] [Commented] (KAFKA-1696) Kafka should be able to generate Hadoop delegation tokens

[ https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706194#comment-15706194 ] Sriharsha Chintalapani commented on KAFKA-1696: --- [~singhashish] [~omkreddy]

[jira] [Resolved] (KAFKA-4448) Add missing licenses to ducktape related files

[ https://issues.apache.org/jira/browse/KAFKA-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raghav Kumar Gautam resolved KAFKA-4448. Resolution: Invalid The problematic patch has been reverted, so the issue is no long

[jira] [Updated] (KAFKA-4462) Improved Kafka Client Compatibility Policy

[ https://issues.apache.org/jira/browse/KAFKA-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-4462: --- Description: A proposal to improve the compatibility policy of the Kafka client by supporting

[jira] [Commented] (KAFKA-4405) Kafka consumer improperly send prefetch request

[ https://issues.apache.org/jira/browse/KAFKA-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706166#comment-15706166 ] Guozhang Wang commented on KAFKA-4405: -- Thanks [~enothereska]. > Kafka consumer impr

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

See

  1   2   >