[jira] [Resolved] (KAFKA-4362) Consumer can fail after reassignment of the offsets topic partition

[ https://issues.apache.org/jira/browse/KAFKA-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4362. Resolution: Fixed > Consumer can fail after reassignment of the offsets topic partition > --

Re: [DISCUSS] Deprecating the old consumers in trunk

Some coworkers may have had issues seeing my earlier post so reposting under a different email: So my earlier stated suboptimal migration plans and Joel's idea all suffer from either downtime or dual partition ownership and consumption. But I think there's a bigger problem: they assume users are

[GitHub] kafka pull request #2161: KAFKA-4307 Inconsistent parameters between console...

GitHub user baluchicken opened a pull request: https://github.com/apache/kafka/pull/2161 KAFKA-4307 Inconsistent parameters between console producer and consumer @gwenshap please review You can merge this pull request into a Git repository by running: $ git pull https://github.

[jira] [Commented] (KAFKA-4307) Inconsistent parameters between console producer and consumer

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

[jira] [Assigned] (KAFKA-4307) Inconsistent parameters between console producer and consumer

[ https://issues.apache.org/jira/browse/KAFKA-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balint Molnar reassigned KAFKA-4307: Assignee: Balint Molnar (was: Manasvi Gupta) > Inconsistent parameters between console pro

[GitHub] kafka pull request #2162: Fixed kafka stop error

GitHub user muliliao opened a pull request: https://github.com/apache/kafka/pull/2162 Fixed kafka stop error when user want to stop the zookeeper or kafka server, they will exec the script kafka-server-stop.sh or kafka-server-stop.sh. In kafka-server-stop.sh and kaf

[jira] [Issue Comment Deleted] (KAFKA-4425) Topic created with CreateTopic command, does not list partitions in metadata

[ https://issues.apache.org/jira/browse/KAFKA-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4425: --- Comment: was deleted (was: You have to pass `null` to get all topics. An empty list returns no topics

[jira] [Commented] (KAFKA-4425) Topic created with CreateTopic command, does not list partitions in metadata

[ https://issues.apache.org/jira/browse/KAFKA-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689570#comment-15689570 ] Ismael Juma commented on KAFKA-4425: Is `delete.topic.enable=true`? If so, what happen

[GitHub] kafka pull request #2120: KAFKA-4395: Break static initialization order depe...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2120 --- 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-4395) KafkaConfig and LogConfig should not have static initialization order dependencies

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

[jira] [Resolved] (KAFKA-4395) KafkaConfig and LogConfig should not have static initialization order dependencies

[ https://issues.apache.org/jira/browse/KAFKA-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4395. Resolution: Fixed Fix Version/s: 0.10.2.0 Issue resolved by pull request 2120 [https://github

[GitHub] kafka pull request #2162: Fixed kafka stop error

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

[GitHub] kafka pull request #2163: fix issue: stop kafka or zookeeper failed when ful...

GitHub user muliliao opened a pull request: https://github.com/apache/kafka/pull/2163 fix issue: stop kafka or zookeeper failed when full command length reach 4096 bytes when user want to stop the zookeeper or kafka server, they will exec the script kafka-server-stop.sh or kafka-se

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

See

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

See

[jira] [Created] (KAFKA-4434) KafkaProducer configuration is logged twice

Ruben de Gooijer created KAFKA-4434: --- Summary: KafkaProducer configuration is logged twice Key: KAFKA-4434 URL: https://issues.apache.org/jira/browse/KAFKA-4434 Project: Kafka Issue Type: B

[jira] [Updated] (KAFKA-4434) KafkaProducer configuration is logged twice

[ https://issues.apache.org/jira/browse/KAFKA-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruben de Gooijer updated KAFKA-4434: Description: The constructor of org.apache.kafka.clients.producer.KafkaProducer accepts a P

[jira] [Updated] (KAFKA-4434) KafkaProducer configuration is logged twice

[ https://issues.apache.org/jira/browse/KAFKA-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4434: --- Fix Version/s: 0.10.2.0 > KafkaProducer configuration is logged twice > --

[jira] [Commented] (KAFKA-4434) KafkaProducer configuration is logged twice

[ https://issues.apache.org/jira/browse/KAFKA-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690203#comment-15690203 ] Ismael Juma commented on KAFKA-4434: Good catch. Would you like to contribute a fix?

RE: Kafka consumers are not equally distributed

No, that is not the reason. Initially all the partitions were assigned the messages and those were processed very fast and sit idle even other partitions are having a lot of messages to be processed. So I was under impression that rebalance should be triggered and messages will be re-distribut

[jira] [Updated] (KAFKA-4302) Simplify KTableSource

[ https://issues.apache.org/jira/browse/KAFKA-4302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4302: - Fix Version/s: 0.10.1.1 > Simplify KTableSource > - > > Key: K

[jira] [Updated] (KAFKA-4269) Multiple KStream instances with at least one Regex source causes NPE when using multiple consumers

[ https://issues.apache.org/jira/browse/KAFKA-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4269: - Fix Version/s: 0.10.1.1 > Multiple KStream instances with at least one Regex source causes NPE whe

[jira] [Updated] (KAFKA-4352) Failure in org.apache.kafka.streams.integration.ResetIntegrationTest.testReprocessingFromScratchAfterReset

[ https://issues.apache.org/jira/browse/KAFKA-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4352: - Fix Version/s: 0.10.1.1 > Failure in > org.apache.kafka.streams.integration.ResetIntegrationTest.

[jira] [Updated] (KAFKA-4275) Check of State-Store-assignment to Processor-Nodes is not enabled

[ https://issues.apache.org/jira/browse/KAFKA-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4275: - Fix Version/s: (was: 0.10.1.0) 0.10.1.1 > Check of State-Store-assignment t

[jira] [Updated] (KAFKA-4331) Kafka Streams resetter is slow because it joins the same group for each topic

[ https://issues.apache.org/jira/browse/KAFKA-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4331: - Fix Version/s: 0.10.1.1 > Kafka Streams resetter is slow because it joins the same group for each

[jira] [Updated] (KAFKA-4361) Streams does not respect user configs for "default" params

[ https://issues.apache.org/jira/browse/KAFKA-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4361: - Fix Version/s: 0.10.1.1 > Streams does not respect user configs for "default" params > ---

[jira] [Updated] (KAFKA-4311) Multi layer cache eviction causes forwarding to incorrect ProcessorNode

[ https://issues.apache.org/jira/browse/KAFKA-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4311: - Fix Version/s: 0.10.1.1 > Multi layer cache eviction causes forwarding to incorrect ProcessorNode

[jira] [Updated] (KAFKA-4355) StreamThread intermittently dies with "Topic not found during partition assignment" when broker restarted

[ https://issues.apache.org/jira/browse/KAFKA-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4355: - Fix Version/s: 0.10.1.1 > StreamThread intermittently dies with "Topic not found during partition

[jira] [Updated] (KAFKA-4379) Remove caching of dirty and removed keys from StoreChangeLogger

[ https://issues.apache.org/jira/browse/KAFKA-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4379: - Fix Version/s: 0.10.1.1 > Remove caching of dirty and removed keys from StoreChangeLogger > --

A strange controller log in Kafka 0.9.0.1

Hi, We have a cluster of kafka 0.9.0.1 with 3 nodes, and we found a strange controller log as below. [2016-11-07 03:14:48,575] INFO [SessionExpirationListener on 100], ZK expired; shut down all controller components and try to re-elect (kafka.controller.KafkaController$SessionExpiration

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

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] derek updated KAFKA-2729: - Comment: was deleted (was: I'm on 0.10.1.0 and seeing the same thing. Maybe related to [~cmolter] is saying above

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

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690421#comment-15690421 ] derek commented on KAFKA-2729: -- I'm on 0.10.1.0 and seeing the same thing. Maybe related to [

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

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690420#comment-15690420 ] derek commented on KAFKA-2729: -- I'm on 0.10.1.0 and seeing the same thing. Maybe related to [

[jira] [Commented] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690654#comment-15690654 ] Matthias Bechtold commented on KAFKA-4424: -- Thank you for your feedback, I can to

[jira] [Resolved] (KAFKA-1429) Yet another deadlock in controller shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-1429. Resolution: Duplicate Assignee: (was: Neha Narkhede) This is already fixed by KAFKA-4360. > Yet a

[jira] [Comment Edited] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690654#comment-15690654 ] Matthias Bechtold edited comment on KAFKA-4424 at 11/23/16 4:50 PM:

[jira] [Commented] (KAFKA-4430) Broker logging "Topic and partition to exceptions: [topic,6] -> kafka.common.MessageSizeTooLargeException"

[ https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690723#comment-15690723 ] Srinivas Dhruvakumar commented on KAFKA-4430: - I am a tad bit confused why wou

[jira] [Updated] (KAFKA-4393) Improve invalid/negative TS handling

[ https://issues.apache.org/jira/browse/KAFKA-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4393: --- Status: Patch Available (was: In Progress) > Improve invalid/negative TS handling > -

[jira] [Updated] (KAFKA-3213) [CONNECT] It looks like we are not backing off properly when reconfiguring tasks

[ https://issues.apache.org/jira/browse/KAFKA-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3213: - Fix Version/s: (was: 0.10.1.1) 0.10.2.0 > [CONNECT] It looks like we are no

[jira] [Commented] (KAFKA-4399) Deadlock between cleanupGroupMetadata and offset commit

[ https://issues.apache.org/jira/browse/KAFKA-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691085#comment-15691085 ] Guozhang Wang commented on KAFKA-4399: -- [~hachikuji] [~ijuma] Do you think it should

[jira] [Updated] (KAFKA-4401) Change the KafkaServerTestHarness and IntegrationTestHarness from trait to abstract class.

[ https://issues.apache.org/jira/browse/KAFKA-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4401: - Fix Version/s: (was: 0.10.1.1) 0.10.2.0 > Change the KafkaServerTestHarness

[jira] [Commented] (KAFKA-4384) ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted message

[ https://issues.apache.org/jira/browse/KAFKA-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691093#comment-15691093 ] Guozhang Wang commented on KAFKA-4384: -- [~junrao] [~ijuma] Do you think it should be

[jira] [Updated] (KAFKA-4182) Move the change logger our of RocksDB stores

[ https://issues.apache.org/jira/browse/KAFKA-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4182: - Fix Version/s: (was: 0.10.1.1) 0.10.2.0 > Move the change logger our of Roc

[jira] [Updated] (KAFKA-4184) Test failure in ReplicationQuotasTest.shouldBootstrapTwoBrokersWithFollowerThrottle

[ https://issues.apache.org/jira/browse/KAFKA-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4184: - Fix Version/s: (was: 0.10.1.1) 0.10.2.0 > Test failure in > ReplicationQuo

[jira] [Updated] (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 ] Guozhang Wang updated KAFKA-4340: - Fix Version/s: (was: 0.10.1.1) 0.10.2.0 > Change the default value of log.m

[jira] [Resolved] (KAFKA-4186) Transient failure in KStreamAggregationIntegrationTest.shouldGroupByKey

[ https://issues.apache.org/jira/browse/KAFKA-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4186. -- Resolution: Not A Problem > Transient failure in KStreamAggregationIntegrationTest.shouldGroupBy

[jira] [Commented] (KAFKA-4178) Replication Throttling: Consolidate Rate Classes

[ https://issues.apache.org/jira/browse/KAFKA-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691096#comment-15691096 ] Guozhang Wang commented on KAFKA-4178: -- [~benstopford] [~ijuma] Does it need to be in

[jira] [Updated] (KAFKA-3832) Kafka Connect's JSON Converter never outputs a null value

[ https://issues.apache.org/jira/browse/KAFKA-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3832: - Fix Version/s: (was: 0.10.1.1) 0.10.2.0 > Kafka Connect's JSON Converter ne

[jira] [Updated] (KAFKA-3986) completedReceives can contain closed channels

[ https://issues.apache.org/jira/browse/KAFKA-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3986: - Fix Version/s: (was: 0.10.1.1) (was: 0.10.0.2) 0.10.2

[jira] [Updated] (KAFKA-3875) Transient test failure: kafka.api.SslProducerSendTest.testSendNonCompressedMessageWithCreateTime

[ https://issues.apache.org/jira/browse/KAFKA-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3875: - Fix Version/s: (was: 0.10.1.1) 0.10.2.0 > Transient test failure: > kafka.

[jira] [Resolved] (KAFKA-1573) Transient test failures on LogTest.testCorruptLog

[ https://issues.apache.org/jira/browse/KAFKA-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-1573. -- Resolution: Not A Problem > Transient test failures on LogTest.testCorruptLog >

[jira] [Updated] (KAFKA-3689) Exception when attempting to decrease connection count for address with no connections

[ https://issues.apache.org/jira/browse/KAFKA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3689: - Fix Version/s: (was: 0.10.1.1) (was: 0.10.0.2) 0.10.2

[jira] [Updated] (KAFKA-2363) ProducerSendTest.testCloseWithZeroTimeoutFromCallerThread Transient Failure

[ https://issues.apache.org/jira/browse/KAFKA-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2363: - Fix Version/s: (was: 0.10.1.1) 0.10.2.0 > ProducerSendTest.testCloseWithZer

[jira] [Commented] (KAFKA-1377) transient unit test failure in LogOffsetTest

[ https://issues.apache.org/jira/browse/KAFKA-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691106#comment-15691106 ] Guozhang Wang commented on KAFKA-1377: -- [~ijuma] Is this still an issue? I cannot rem

[jira] [Commented] (KAFKA-4384) ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted message

[ https://issues.apache.org/jira/browse/KAFKA-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691103#comment-15691103 ] Ismael Juma commented on KAFKA-4384: I think so, the PR is close. > ReplicaFetcherThr

[jira] [Commented] (KAFKA-4178) Replication Throttling: Consolidate Rate Classes

[ https://issues.apache.org/jira/browse/KAFKA-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1569#comment-1569 ] Ismael Juma commented on KAFKA-4178: [~guozhang], I'd say this can be pushed to 0.10.2

[jira] [Updated] (KAFKA-4178) Replication Throttling: Consolidate Rate Classes

[ https://issues.apache.org/jira/browse/KAFKA-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4178: --- Fix Version/s: (was: 0.10.1.1) 0.10.2.0 > Replication Throttling: Consolidate R

[jira] [Updated] (KAFKA-1377) transient unit test failure in LogOffsetTest

[ https://issues.apache.org/jira/browse/KAFKA-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1377: --- Fix Version/s: (was: 0.10.1.1) > transient unit test failure in LogOffsetTest > --

[jira] [Resolved] (KAFKA-1377) transient unit test failure in LogOffsetTest

[ https://issues.apache.org/jira/browse/KAFKA-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-1377. Resolution: Fixed I haven't seen it, so closing it since the original reporter said it was fixed. >

[jira] [Updated] (KAFKA-1377) transient unit test failure in LogOffsetTest

[ https://issues.apache.org/jira/browse/KAFKA-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1377: --- Status: Reopened (was: Reopened) > transient unit test failure in LogOffsetTest > ---

[jira] [Commented] (KAFKA-4039) Exit Strategy: using exceptions instead of inline invocation of exit/halt

[ https://issues.apache.org/jira/browse/KAFKA-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691142#comment-15691142 ] Guozhang Wang commented on KAFKA-4039: -- [~hachikuji] [~ijuma] If you guys feel it is

[jira] [Created] (KAFKA-4435) Improve storage overhead of group metadata

Jason Gustafson created KAFKA-4435: -- Summary: Improve storage overhead of group metadata Key: KAFKA-4435 URL: https://issues.apache.org/jira/browse/KAFKA-4435 Project: Kafka Issue Type: Impr

[jira] [Commented] (KAFKA-4435) Improve storage overhead of group metadata

[ https://issues.apache.org/jira/browse/KAFKA-4435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691169#comment-15691169 ] Jason Gustafson commented on KAFKA-4435: cc [~onurkaraman] > Improve storage over

[jira] [Commented] (KAFKA-4178) Replication Throttling: Consolidate Rate Classes

[ https://issues.apache.org/jira/browse/KAFKA-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691178#comment-15691178 ] Ben Stopford commented on KAFKA-4178: - Yes, that should be fine. > Replication Throt

[DISCUSS] 0.10.1.1 Plan

Hi everyone, We have resolved 15 JIRAs including a few critical bugs in the 0.10.1 branch since 0.10.1.0 was released so I'd like to propose to release 0.10.1.1 soon: https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.10.

FOSDEM 2017 HPC, Bigdata and Data Science DevRoom CFP is closing soon

Hi! apologies for the extra wide distribution (this exhausts my once a year ASF mail-to-all-bigdata-projects quota ;-)) but I wanted to suggest that all of you should consider submitting talks to FOSDEM 2017 HPC, Bigdata and Data Science DevRoom: https://hpc-bigdata-fosdem17.github.io/ It was

[jira] [Created] (KAFKA-4436) Provide builder pattern for StreamsConfig

Matthias J. Sax created KAFKA-4436: -- Summary: Provide builder pattern for StreamsConfig Key: KAFKA-4436 URL: https://issues.apache.org/jira/browse/KAFKA-4436 Project: Kafka Issue Type: Impro

Data (re)processing with Kafka (new wiki page)

Hi, we added a new wiki page that is supposed to collect data (re)processing scenario with Kafka: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Streams+Data+(Re)Processing+Scenarios We added already a couple of scenarios we think might be common and want to invite all of you to add mor

[jira] [Commented] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691571#comment-15691571 ] Michael Andre Pearce (IG) commented on KAFKA-4424: -- Hi Matthias, When we

[jira] [Comment Edited] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691571#comment-15691571 ] Michael Andre Pearce (IG) edited comment on KAFKA-4424 at 11/23/16 10:57 PM: ---

[jira] [Comment Edited] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691571#comment-15691571 ] Michael Andre Pearce (IG) edited comment on KAFKA-4424 at 11/23/16 11:01 PM: ---

[jira] [Comment Edited] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691571#comment-15691571 ] Michael Andre Pearce (IG) edited comment on KAFKA-4424 at 11/23/16 11:12 PM: ---

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

Thanks for the feedback. I updated the KIP for (1) and (2). However not for (3): Why should it be required to reset an application? If user processed "good" data with valid timestamps, behavior does not change. If user tried to process "bad" data with invalid timestamps, the application does fail

[jira] [Comment Edited] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691571#comment-15691571 ] Michael Andre Pearce (IG) edited comment on KAFKA-4424 at 11/23/16 11:22 PM: ---

[jira] [Comment Edited] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691571#comment-15691571 ] Michael Andre Pearce (IG) edited comment on KAFKA-4424 at 11/23/16 11:23 PM: ---

[jira] [Comment Edited] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691571#comment-15691571 ] Michael Andre Pearce (IG) edited comment on KAFKA-4424 at 11/23/16 11:28 PM: ---

[jira] [Comment Edited] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691571#comment-15691571 ] Michael Andre Pearce (IG) edited comment on KAFKA-4424 at 11/23/16 11:30 PM: ---

[jira] [Created] (KAFKA-4437) Incremental Batch Processing for Kafka Streams

Matthias J. Sax created KAFKA-4437: -- Summary: Incremental Batch Processing for Kafka Streams Key: KAFKA-4437 URL: https://issues.apache.org/jira/browse/KAFKA-4437 Project: Kafka Issue Type:

Re: [VOTE] KIP-72 - Allow putting a bound on memory consumed by Incoming requests

Hi Jun, I've added the sensor you requested (or at least I think I did ) On Fri, Nov 18, 2016 at 12:37 PM, Jun Rao wrote: > KafkaRequestHandlerPool

[jira] [Commented] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691736#comment-15691736 ] Michael Andre Pearce (IG) commented on KAFKA-4424: -- Just reading the link

[jira] [Comment Edited] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691736#comment-15691736 ] Michael Andre Pearce (IG) edited comment on KAFKA-4424 at 11/24/16 12:12 AM: ---

[jira] [Comment Edited] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691736#comment-15691736 ] Michael Andre Pearce (IG) edited comment on KAFKA-4424 at 11/24/16 12:12 AM: ---

[jira] [Issue Comment Deleted] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Andre Pearce (IG) updated KAFKA-4424: - Comment: was deleted (was: Just reading the link you reference. Virtual c

[jira] [Commented] (KAFKA-4430) Broker logging "Topic and partition to exceptions: [topic,6] -> kafka.common.MessageSizeTooLargeException"

[ https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691773#comment-15691773 ] Srinivas Dhruvakumar commented on KAFKA-4430: - I figured out the issue. The pa

[jira] [Updated] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Andre Pearce (IG) updated KAFKA-4424: - Attachment: FinalTestReversed.java FinalTest.java > Make s

[jira] [Created] (KAFKA-4438) BACKPORT - Add scala 2.12 support

Bernard Leach created KAFKA-4438: Summary: BACKPORT - Add scala 2.12 support Key: KAFKA-4438 URL: https://issues.apache.org/jira/browse/KAFKA-4438 Project: Kafka Issue Type: Improvement

[jira] [Updated] (KAFKA-4438) BACKPORT - Add scala 2.12 support

[ https://issues.apache.org/jira/browse/KAFKA-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernard Leach updated KAFKA-4438: - Fix Version/s: (was: 0.10.2.0) 0.10.1.1 > BACKPORT - Add scala 2.12 support

[GitHub] kafka pull request #2164: KAFKA-4438; Cross compile to Scala 2.12.0

GitHub user leachbj opened a pull request: https://github.com/apache/kafka/pull/2164 KAFKA-4438; Cross compile to Scala 2.12.0 (cherry picked from commit f3aad3b54b7cbc5109d8398829a31100fd82b3e0) You can merge this pull request into a Git repository by running: $ git pull https

[jira] [Commented] (KAFKA-4438) BACKPORT - Add scala 2.12 support

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

[GitHub] kafka pull request #1603: KAFKA-1429: Yet another deadlock in controller shu...

Github user pengwei-li closed the pull request at: https://github.com/apache/kafka/pull/1603 --- 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-1429) Yet another deadlock in controller shutdown

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

[jira] [Commented] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691817#comment-15691817 ] Michael Andre Pearce (IG) commented on KAFKA-4424: -- The link you referenc

[jira] [Comment Edited] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691817#comment-15691817 ] Michael Andre Pearce (IG) edited comment on KAFKA-4424 at 11/24/16 12:54 AM: ---

[jira] [Comment Edited] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691817#comment-15691817 ] Michael Andre Pearce (IG) edited comment on KAFKA-4424 at 11/24/16 12:55 AM: ---

[jira] [Comment Edited] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691817#comment-15691817 ] Michael Andre Pearce (IG) edited comment on KAFKA-4424 at 11/24/16 12:57 AM: ---

[jira] [Comment Edited] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691817#comment-15691817 ] Michael Andre Pearce (IG) edited comment on KAFKA-4424 at 11/24/16 12:59 AM: ---

[jira] [Comment Edited] (KAFKA-4424) Make serializer classes final

[ https://issues.apache.org/jira/browse/KAFKA-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691817#comment-15691817 ] Michael Andre Pearce (IG) edited comment on KAFKA-4424 at 11/24/16 1:03 AM:

[GitHub] kafka pull request #2138: KAFKA-4331: Kafka Streams resetter is slow because...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2138 --- 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-4331) Kafka Streams resetter is slow because it joins the same group for each topic

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

[jira] [Created] (KAFKA-4439) Add a builder to NetworkClient

Colin P. McCabe created KAFKA-4439: -- Summary: Add a builder to NetworkClient Key: KAFKA-4439 URL: https://issues.apache.org/jira/browse/KAFKA-4439 Project: Kafka Issue Type: Improvement

  1   2   >