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

See Changes: [wangguoz] KAFKA-5273: Make KafkaConsumer.committed query the server for all -- [...truncated 898.98 KB...] kafka.log.ProducerStateManagerTest > testNonTrans

[GitHub] kafka pull request #3133: MINOR: GroupCoordinator can append with group lock

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3133 MINOR: GroupCoordinator can append with group lock You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka minor-replica-manager-appe

Re: [Vote] KIP-150 - Kafka-Streams Cogroup

+1 to what Xavier said On Wed, 24 May 2017 at 06:45 Xavier Léauté wrote: > I don't think we should wait for entries from each stream, since that might > limit the usefulness of the cogroup operator. There are instances where it > can be useful to compute something based on data from one or more

Re: [Vote] KIP-150 - Kafka-Streams Cogroup

Also, +1 for the KIP On Wed, 24 May 2017 at 08:57 Damian Guy wrote: > +1 to what Xavier said > > On Wed, 24 May 2017 at 06:45 Xavier Léauté wrote: > >> I don't think we should wait for entries from each stream, since that >> might >> limit the usefulness of the cogroup operator. There are insta

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

See

[GitHub] kafka pull request #3134: Kafka-5315: should not subtract for empty key is K...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/3134 Kafka-5315: should not subtract for empty key is KTable.aggregate/reduce You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka kafka-5315-f

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

See

[jira] [Updated] (KAFKA-5315) Streams exception w/ partially processed record corrupts state store

[ https://issues.apache.org/jira/browse/KAFKA-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5315: --- Status: Patch Available (was: Open) PR: https://github.com/apache/kafka/pull/3134 > Streams

[GitHub] kafka pull request #3021: KAFKA-5006: change exception path

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

[jira] [Commented] (KAFKA-5006) KeyValueStore.put may throw exception unrelated to the current put attempt

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

[jira] [Updated] (KAFKA-5006) KeyValueStore.put may throw exception unrelated to the current put attempt

[ https://issues.apache.org/jira/browse/KAFKA-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-5006: Resolution: Fixed Status: Resolved (was: Patch Available) > KeyValueStore.put may throw exc

[GitHub] kafka pull request #3135: KAFKA-5314: exception handling and cleanup for sta...

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/3135 KAFKA-5314: exception handling and cleanup for state stores You can merge this pull request into a Git repository by running: $ git pull https://github.com/enothereska/kafka exceptions-sto

[jira] [Commented] (KAFKA-5314) Improve exception handling for state stores

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

[GitHub] kafka pull request #3127: Add sleep between empty polls to avoid burning CPU

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

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

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

[jira] [Created] (KAFKA-5319) Add a tool to make cluster replica and leader balance

Ma Tianchi created KAFKA-5319: - Summary: Add a tool to make cluster replica and leader balance Key: KAFKA-5319 URL: https://issues.apache.org/jira/browse/KAFKA-5319 Project: Kafka Issue Type: Imp

[GitHub] kafka pull request #3136: KAFKA-5319 Add a tool to make cluster replica and ...

GitHub user MarkTcMA opened a pull request: https://github.com/apache/kafka/pull/3136 KAFKA-5319 Add a tool to make cluster replica and leader balance As [KAFKA-5319](https://issues.apache.org/jira/browse/KAFKA-5319) describes Kafka does not have tools to make replica or leader num

[jira] [Commented] (KAFKA-5319) Add a tool to make cluster replica and leader balance

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

[jira] [Resolved] (KAFKA-5319) Add a tool to make cluster replica and leader balance

[ https://issues.apache.org/jira/browse/KAFKA-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ma Tianchi resolved KAFKA-5319. --- Resolution: Resolved > Add a tool to make cluster replica and leader balance > ---

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

I allow defining a single window/sessionwindow one time when you make the cogroup call from a KGroupedStream. From then on you are using the cogroup call from with in CogroupedKStream which doesnt accept any additional windows/sessionwindows. Is this what you meant by your question or did I misund

[jira] [Commented] (KAFKA-5319) Add a tool to make cluster replica and leader balance

[ https://issues.apache.org/jira/browse/KAFKA-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022695#comment-16022695 ] Michal Borowiecki commented on KAFKA-5319: -- [~markTC], shouldn't this be in "Patc

[jira] [Created] (KAFKA-5320) Update produce/fetch throttle time metrics for any request throttle

Rajini Sivaram created KAFKA-5320: - Summary: Update produce/fetch throttle time metrics for any request throttle Key: KAFKA-5320 URL: https://issues.apache.org/jira/browse/KAFKA-5320 Project: Kafka

[jira] [Reopened] (KAFKA-5319) Add a tool to make cluster replica and leader balance

[ https://issues.apache.org/jira/browse/KAFKA-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ma Tianchi reopened KAFKA-5319: --- > Add a tool to make cluster replica and leader balance >

[jira] [Commented] (KAFKA-5320) Update produce/fetch throttle time metrics for any request throttle

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

[GitHub] kafka pull request #3137: KAFKA-5320: Include all request throttling in clie...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/3137 KAFKA-5320: Include all request throttling in client throttle metrics You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivaram/kafka

[jira] [Updated] (KAFKA-5319) Add a tool to make cluster replica and leader balance

[ https://issues.apache.org/jira/browse/KAFKA-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ma Tianchi updated KAFKA-5319: -- Attachment: (was: ClusterBalanceCommand.scala) > Add a tool to make cluster replica and leader balan

[jira] [Updated] (KAFKA-5319) Add a tool to make cluster replica and leader balance

[ https://issues.apache.org/jira/browse/KAFKA-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ma Tianchi updated KAFKA-5319: -- Status: Reopened (was: Reopened) > Add a tool to make cluster replica and leader balance >

[jira] [Commented] (KAFKA-4740) Using new consumer API with a Deserializer that throws SerializationException can lead to infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022828#comment-16022828 ] Eno Thereska commented on KAFKA-4740: - I mentioned in KAFKA-5211 that such a change sh

[jira] [Commented] (KAFKA-5211) KafkaConsumer should not skip a corrupted record after throwing an exception.

[ https://issues.apache.org/jira/browse/KAFKA-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022824#comment-16022824 ] Eno Thereska commented on KAFKA-5211: - [~becket_qin] I think this change needs a KIP.

[jira] [Updated] (KAFKA-4857) Use AdminClient in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4857: Summary: Use AdminClient in Kafka Streams (was: Improve Client handling) > Use AdminClient in Kafka

Re: [Vote] KIP-150 - Kafka-Streams Cogroup

+1 for the KIP and +1 what Xavier said as well. On Wed, May 24, 2017 at 3:57 AM, Damian Guy wrote: > Also, +1 for the KIP > > On Wed, 24 May 2017 at 08:57 Damian Guy wrote: > > > +1 to what Xavier said > > > > On Wed, 24 May 2017 at 06:45 Xavier Léauté wrote: > > > >> I don't think we should

Kafka Read Data from All Partition Using Key or Timestamp

Hi All , We have been using Kafka for our Use Case which helps in delivering real time raw logs.. I have a requirement to fetch data from Kafka by using offset .. DataSet Example : {"access_date":"2017-05-24 13:57:45.044","format":"json","start":"1490296463.031"} {"access_date":"2017-05-24 13:57:

[jira] [Reopened] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Edenhill reopened KAFKA-4340: > Change the default value of log.message.timestamp.difference.max.ms to the > same as log.rete

[jira] [Commented] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022945#comment-16022945 ] Magnus Edenhill commented on KAFKA-4340: While the idea behind this JIRA is good (

[GitHub] kafka pull request #2046: MINOR: Improve the help doc of consumer group comm...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2046 --- 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-5315) Streams exception w/ partially processed record corrupts state store

[ https://issues.apache.org/jira/browse/KAFKA-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023155#comment-16023155 ] Eno Thereska commented on KAFKA-5315: - [~mjsax] isn't this a fundamental problem that

[jira] [Updated] (KAFKA-5063) Flaky ResetIntegrationTest.testReprocessingFromScratchAfterResetWithIntermediateUserTopic

[ https://issues.apache.org/jira/browse/KAFKA-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5063: --- Status: Reopened (was: Reopened) > Flaky > ResetIntegrationTest.testReprocessingFromScratchA

[jira] [Resolved] (KAFKA-5063) Flaky ResetIntegrationTest.testReprocessingFromScratchAfterResetWithIntermediateUserTopic

[ https://issues.apache.org/jira/browse/KAFKA-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-5063. Resolution: Fixed We got a new JIRA for the new stack trace: https://issues.apache.org/jira

[jira] [Reopened] (KAFKA-5063) Flaky ResetIntegrationTest.testReprocessingFromScratchAfterResetWithIntermediateUserTopic

[ https://issues.apache.org/jira/browse/KAFKA-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reopened KAFKA-5063: > Flaky > ResetIntegrationTest.testReprocessingFromScratchAfterResetWithIntermediateUserTopic >

[jira] [Commented] (KAFKA-5315) Streams exception w/ partially processed record corrupts state store

[ https://issues.apache.org/jira/browse/KAFKA-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023185#comment-16023185 ] Matthias J. Sax commented on KAFKA-5315: EOS will fix this automatically. But we c

[jira] [Updated] (KAFKA-5156) Options for handling exceptions in streams

[ https://issues.apache.org/jira/browse/KAFKA-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-5156: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Options for handling exceptions in

Re: [DISCUSS] KIP-148: Add a connect timeout for client

On Tue, May 23, 2017, at 19:07, Guozhang Wang wrote: > I think using a single config to cover end-to-end latency with connecting > and request round-trip may not be best appropriate since 1) some request > may need much more time than others since they are parked (fetch request > with long polling,

[GitHub] kafka pull request #3138: KAFKA-5017: Record batch first offset remains accu...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3138 KAFKA-5017: Record batch first offset remains accurate after compaction You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-

[jira] [Commented] (KAFKA-5017) Consider making baseOffset the first offset in message format v2

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

[jira] [Updated] (KAFKA-5017) Consider making baseOffset the first offset in message format v2

[ https://issues.apache.org/jira/browse/KAFKA-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5017: --- Assignee: Jason Gustafson Status: Patch Available (was: Open) > Consider making baseOff

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

Hi Michal, Thanks for your comments. I see your point and I agree with it. However, I don't have a better idea for naming. I checked MR source code. There it is used JobConfigurable and Closable, two different interfaces. Maybe we can rename RichFunction as Configurable? Cheers, Jeyhun On Tue,

[jira] [Created] (KAFKA-5321) MemoryRecords.filterTo can return corrupt data if output buffer is not large enough

Jason Gustafson created KAFKA-5321: -- Summary: MemoryRecords.filterTo can return corrupt data if output buffer is not large enough Key: KAFKA-5321 URL: https://issues.apache.org/jira/browse/KAFKA-5321

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

Kyle, Thanks for the explanations, my previous read on the wiki examples was wrong. So I guess my motivation should be "reduced" to: can we move the window specs param from "KGroupedStream#cogroup(..)" to "CogroupedKStream#aggregate(..)", and my motivations are: 1. minor: we can reduce the #.gen

[jira] [Updated] (KAFKA-5251) Producer should drop queued sends when transaction is aborted

[ https://issues.apache.org/jira/browse/KAFKA-5251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5251: Priority: Blocker (was: Major) > Producer should drop queued sends when transaction is aborted > --

[jira] [Commented] (KAFKA-5251) Producer should drop queued sends when transaction is aborted

[ https://issues.apache.org/jira/browse/KAFKA-5251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023603#comment-16023603 ] Apurva Mehta commented on KAFKA-5251: - Raising this to blocker status. Currently, if t

[jira] [Commented] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023619#comment-16023619 ] Jiangjie Qin commented on KAFKA-4340: - [~edenhill] I think one of the well established

[jira] [Commented] (KAFKA-5211) KafkaConsumer should not skip a corrupted record after throwing an exception.

[ https://issues.apache.org/jira/browse/KAFKA-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023641#comment-16023641 ] Jiangjie Qin commented on KAFKA-5211: - [~enothereska] I think a KIP is only required i

[jira] [Created] (KAFKA-5322) Resolve AddPartitions response error code inconsistency

Jason Gustafson created KAFKA-5322: -- Summary: Resolve AddPartitions response error code inconsistency Key: KAFKA-5322 URL: https://issues.apache.org/jira/browse/KAFKA-5322 Project: Kafka Iss

[jira] [Commented] (KAFKA-3821) Allow Kafka Connect source tasks to produce offset without writing to topics

[ https://issues.apache.org/jira/browse/KAFKA-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023654#comment-16023654 ] kyle k commented on KAFKA-3821: --- [~rhauch], I agree with your point. I was thinking of the m

[jira] [Commented] (KAFKA-5211) KafkaConsumer should not skip a corrupted record after throwing an exception.

[ https://issues.apache.org/jira/browse/KAFKA-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023656#comment-16023656 ] Ismael Juma commented on KAFKA-5211: This particular JIRA doesn't need a KIP because i

[jira] [Commented] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023668#comment-16023668 ] Magnus Edenhill commented on KAFKA-4340: Generally I would agree, but in this case

[jira] [Created] (KAFKA-5323) AdminUtils.createTopic should check topic existence upfront

Onur Karaman created KAFKA-5323: --- Summary: AdminUtils.createTopic should check topic existence upfront Key: KAFKA-5323 URL: https://issues.apache.org/jira/browse/KAFKA-5323 Project: Kafka Issu

[GitHub] kafka pull request #3139: MINOR: fix flakiness in testDeleteAcls

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/3139 MINOR: fix flakiness in testDeleteAcls This call to isCompletedExceptionally introduced a race condition because the future might not have been completed. assertFutureError checks that the e

[jira] [Resolved] (KAFKA-2060) Async onCompletion callback may not be called

[ https://issues.apache.org/jira/browse/KAFKA-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Sobel resolved KAFKA-2060. --- Resolution: Fixed Fix Version/s: 0.9.0.2 Per notes this was fixed with the later Kafka libs >

[GitHub] kafka pull request #3140: KAFKA-5309: Stores not queryable after one thread ...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/3140 KAFKA-5309: Stores not queryable after one thread died - introduces a new thread state DEAD - ignores DEAD threads when querying You can merge this pull request into a Git repository by running:

[jira] [Commented] (KAFKA-5309) Stores not queryable after one thread died

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

[jira] [Updated] (KAFKA-5309) Stores not queryable after one thread died

[ https://issues.apache.org/jira/browse/KAFKA-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5309: --- Fix Version/s: 0.11.0.0 Status: Patch Available (was: Open) > Stores not queryable

[jira] [Updated] (KAFKA-5259) TransactionalId authorization should imply ProducerId authorization

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

[GitHub] kafka pull request #3075: KAFKA-5259: TransactionalId auth implies ProducerI...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3075 --- 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-5259) TransactionalId authorization should imply ProducerId authorization

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

[jira] [Work started] (KAFKA-5226) NullPointerException (NPE) in SourceNodeRecordDeserializer.deserialize

[ https://issues.apache.org/jira/browse/KAFKA-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5226 started by Bill Bejeck. -- > NullPointerException (NPE) in SourceNodeRecordDeserializer.deserialize > --

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

Jeyhun, I was just wondering if you did look into the key-deep-copy idea we discussed. I am curious to see what the impact might be. -Matthias On 5/20/17 2:03 AM, Jeyhun Karimov wrote: > Hi, > > Thanks for your comments. I rethink about including rich functions into > this KIP. > I think once

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

I confess, the term is borrowed from Flink :) Personally, I never thought about it, but I tend to agree with Michal. I also want to clarify, that the main purpose is the ability to access record metadata. Thus, it might even be sufficient to only have "init". An alternative would of course be, to

[jira] [Created] (KAFKA-5324) AdminClient: add close with timeout, fix some timeout bugs

Colin P. McCabe created KAFKA-5324: -- Summary: AdminClient: add close with timeout, fix some timeout bugs Key: KAFKA-5324 URL: https://issues.apache.org/jira/browse/KAFKA-5324 Project: Kafka

[jira] [Assigned] (KAFKA-5324) AdminClient: add close with timeout, fix some timeout bugs

[ https://issues.apache.org/jira/browse/KAFKA-5324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe reassigned KAFKA-5324: -- Assignee: Colin P. McCabe > AdminClient: add close with timeout, fix some timeout bugs

[jira] [Updated] (KAFKA-5324) AdminClient: add close with timeout, fix some timeout bugs

[ https://issues.apache.org/jira/browse/KAFKA-5324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-5324: --- Affects Version/s: 0.11.0.0 Component/s: admin > AdminClient: add close with timeout

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

One more question: Should we add any of - InitizialierWithKey - ReducerWithKey - ValueTransformerWithKey To get consistent/complete API, it might be a good idea. Any thoughts? -Matthias On 5/24/17 3:47 PM, Matthias J. Sax wrote: > Jeyhun, > > I was just wondering if you did look into the

[GitHub] kafka pull request #3141: KAFKA-5324: AdminClient: add close with timeout, f...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/3141 KAFKA-5324: AdminClient: add close with timeout, fix some timeout bugs You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka KAFKA-5324

[jira] [Commented] (KAFKA-5324) AdminClient: add close with timeout, fix some timeout bugs

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

[jira] [Commented] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023862#comment-16023862 ] Jun Rao commented on KAFKA-4340: [~edenhill], as Jiangjie said, currently, the broker take

[jira] [Updated] (KAFKA-4785) Records from internal repartitioning topics should always use RecordMetadataTimestampExtractor

[ https://issues.apache.org/jira/browse/KAFKA-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4785: --- Fix Version/s: 0.11.0.0 Status: Patch Available (was: Open) > Records from interna

[GitHub] kafka pull request #3142: KAFKA-5316: LogCleaner should account for larger r...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3142 KAFKA-5316: LogCleaner should account for larger record sets after cleaning You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KA

[jira] [Commented] (KAFKA-5316) Log cleaning can increase message size and cause cleaner to crash with buffer overflow

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

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

Yea I really like that idea I'll see what I can do to update the kip and my pr when I have some time. I'm not sure how well creating the kstreamaggregates will go though because at that point I will have thrown away the type of the values. It will be type safe I just may need to do a little forcing

[GitHub] kafka pull request #3109: KAFKA-4144: Allow per stream/table timestamp extra...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3109 --- 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-4144) Allow per stream/table timestamp extractor

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

[jira] [Commented] (KAFKA-5319) Add a tool to make cluster replica and leader balance

[ https://issues.apache.org/jira/browse/KAFKA-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024047#comment-16024047 ] Ma Tianchi commented on KAFKA-5319: --- [~mih...@wp.pl]you are right,I am a green hand to u

[jira] [Commented] (KAFKA-5211) KafkaConsumer should not skip a corrupted record after throwing an exception.

[ https://issues.apache.org/jira/browse/KAFKA-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024066#comment-16024066 ] Jason Gustafson commented on KAFKA-5211: [~enothereska] Looking toward the future,

[jira] [Comment Edited] (KAFKA-5211) KafkaConsumer should not skip a corrupted record after throwing an exception.

[ https://issues.apache.org/jira/browse/KAFKA-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024066#comment-16024066 ] Jason Gustafson edited comment on KAFKA-5211 at 5/25/17 2:21 AM: ---

[jira] [Resolved] (KAFKA-4562) deadlock heartbeat, metadata-manager, request-handler

[ https://issues.apache.org/jira/browse/KAFKA-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-4562. Resolution: Duplicate Pretty sure this was fixed in KAFKA-3994. > deadlock heartbeat, metad

[GitHub] kafka pull request #3133: MINOR: GroupCoordinator can append with group lock

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3133 --- 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-5319) Add a tool to make cluster replica and leader balance

[ https://issues.apache.org/jira/browse/KAFKA-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ma Tianchi updated KAFKA-5319: -- Issue Type: New Feature (was: Improvement) > Add a tool to make cluster replica and leader balance > --

[jira] [Commented] (KAFKA-5323) AdminUtils.createTopic should check topic existence upfront

[ https://issues.apache.org/jira/browse/KAFKA-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024223#comment-16024223 ] Onur Karaman commented on KAFKA-5323: - This can have a larger impact than one might in

[jira] [Updated] (KAFKA-5319) Add a tool to make cluster replica and leader balance

[ https://issues.apache.org/jira/browse/KAFKA-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ma Tianchi updated KAFKA-5319: -- Attachment: ArithmeticDescription.png > Add a tool to make cluster replica and leader balance >

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

See Changes: [jason] MINOR: GroupCoordinator can append with group lock -- [...truncated 2.47 MB...] org.apache.kafka.common.security.scram.ScramMessagesTest > validServe

[jira] [Commented] (KAFKA-5319) Add a tool to make cluster replica and leader balance

[ https://issues.apache.org/jira/browse/KAFKA-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024279#comment-16024279 ] LiangHong commented on KAFKA-5319: -- Attachment 不错 > Add a tool to make cluster replica a