[jira] [Comment Edited] (KAFKA-3980) JmxReporter uses excessive memory causing OutOfMemoryException

[ https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387185#comment-15387185 ] Andrew Jorgensen edited comment on KAFKA-3980 at 7/21/16 5:53 AM: -- As far

[jira] [Comment Edited] (KAFKA-3980) JmxReporter uses excessive memory causing OutOfMemoryException

[ https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387185#comment-15387185 ] Andrew Jorgensen edited comment on KAFKA-3980 at 7/21/16 5:52 AM: -- As far

[jira] [Comment Edited] (KAFKA-3980) JmxReporter uses excessive memory causing OutOfMemoryException

[ https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387185#comment-15387185 ] Andrew Jorgensen edited comment on KAFKA-3980 at 7/21/16 5:22 AM: -- As far

[jira] [Commented] (KAFKA-3980) JmxReporter uses excessive memory causing OutOfMemoryException

[ https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387185#comment-15387185 ] Andrew Jorgensen commented on KAFKA-3980: - As far as I know we are not restarting with different

[jira] [Commented] (KAFKA-3980) JmxReporter uses excessive memory causing OutOfMemoryException

[ https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387174#comment-15387174 ] Manikumar Reddy commented on KAFKA-3980: This may due to increasing in client quota metrics

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

See -- [...truncated 4454 lines...] kafka.utils.ByteBoundedBlockingQueueTest > testByteBoundedBlockingQueue STARTED kafka.utils.ByteBoundedBlockingQueueTest > testByteBoundedBlockingQueue PASSED

[GitHub] kafka pull request #1645: HOTFIX: Adding init file so streams benchmark is a...

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/1645 HOTFIX: Adding init file so streams benchmark is autodiscovered Without this file the benchmark does not run nightly. You can merge this pull request into a Git repository by running: $

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

See Changes: [ismael] MINOR: MetadataCache brokerId is not set on first run with generated [ismael] MINOR: Improve PartitionState logging and remove duplication of code -- [...truncated 6633

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

See -- [...truncated 4449 lines...] kafka.utils.SchedulerTest > testRestart PASSED kafka.utils.SchedulerTest > testReentrantTaskInMockScheduler STARTED kafka.utils.SchedulerTest >

[GitHub] kafka pull request #1609: Minor: Improve PartitionState logging and remove d...

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

[GitHub] kafka pull request #1632: MINOR: MetadataCache brokerId is not set on first ...

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

[GitHub] kafka pull request #1644: MINOR: Update to Gradle 2.14.1

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1644 MINOR: Update to Gradle 2.14.1 Better performance is always welcome: "The Gradle build itself has seen a 50% reduction in configuration time. You'll see the biggest impact on multi-project

[jira] [Created] (KAFKA-3981) Possible race condition between controller cache and ZK on topic delete

Matthias J. Sax created KAFKA-3981: -- Summary: Possible race condition between controller cache and ZK on topic delete Key: KAFKA-3981 URL: https://issues.apache.org/jira/browse/KAFKA-3981 Project:

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

See Changes: [wangguoz] KAFKA-3915; Don't convert messages from v0 to v1 during log compaction -- [...truncated 6645 lines...] kafka.utils.ZkUtilsTest > testAbortedConditionalDeletePath

[jira] [Updated] (KAFKA-3980) JmxReporter uses excessive memory causing OutOfMemoryException

[ https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Jorgensen updated KAFKA-3980: Description: I have some nodes in a kafka cluster that occasionally will run out of memory

[jira] [Updated] (KAFKA-3980) JmxReporter uses excessive memory causing OutOfMemoryException

[ https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Jorgensen updated KAFKA-3980: Summary: JmxReporter uses excessive memory causing OutOfMemoryException (was: JmxReporter

[jira] [Updated] (KAFKA-3980) JmxReporter uses an excessive memory causing OutOfMemoryException

[ https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Jorgensen updated KAFKA-3980: Description: I have some nodes in a kafka cluster that occasionally will run out of memory

[jira] [Updated] (KAFKA-3980) JmxReporter uses an excessive memory causing OutOfMemoryException

[ https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Jorgensen updated KAFKA-3980: Description: I have some nodes in a kafka cluster that occasionally will run out of memory

[jira] [Updated] (KAFKA-3980) JmxReporter uses an excessive memory causing OutOfMemoryException

[ https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Jorgensen updated KAFKA-3980: Summary: JmxReporter uses an excessive memory causing OutOfMemoryException (was:

[jira] [Updated] (KAFKA-3980) JmxReporter using excessive memory causing OutOfMemoryException

[ https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Jorgensen updated KAFKA-3980: Summary: JmxReporter using excessive memory causing OutOfMemoryException (was: JMXReport

[jira] [Updated] (KAFKA-3977) KafkaConsumer swallows exceptions raised from message deserializers

[ https://issues.apache.org/jira/browse/KAFKA-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3977: --- Fix Version/s: 0.10.0.1 > KafkaConsumer swallows exceptions raised from message deserializers

[jira] [Updated] (KAFKA-3977) KafkaConsumer swallows exceptions raised from message deserializers

[ https://issues.apache.org/jira/browse/KAFKA-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3977: --- Priority: Blocker (was: Critical) > KafkaConsumer swallows exceptions raised from message

[jira] [Created] (KAFKA-3980) JMXReport using excessive memory

Andrew Jorgensen created KAFKA-3980: --- Summary: JMXReport using excessive memory Key: KAFKA-3980 URL: https://issues.apache.org/jira/browse/KAFKA-3980 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-3915) LogCleaner IO buffers do not account for potential size difference due to message format change

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

[jira] [Commented] (KAFKA-3915) LogCleaner IO buffers do not account for potential size difference due to message format change

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

[GitHub] kafka pull request #1643: KAFKA-3915; Don't convert messages from v0 to v1 d...

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

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

Hey Vahid, Thanks for writing this up. This seems like a nice improvement over the existing somewhat surprising behavior. Currently if you have a consumer which changes subscriptions, then you will need to handle separately any cleanup for assigned partitions for topics which are no longer

[jira] [Commented] (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:comment-tabpanel=15385962#comment-15385962 ] Ismael Juma commented on KAFKA-3689: (I edited my previous comment as it contained some inaccuracies)

[jira] [Comment Edited] (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:comment-tabpanel=15383936#comment-15383936 ] Ismael Juma edited comment on KAFKA-3689 at 7/20/16 2:36 PM: - So, looking at

[jira] [Commented] (KAFKA-3979) Optimize memory used by replication process by using adaptive fetch message size

[ https://issues.apache.org/jira/browse/KAFKA-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385882#comment-15385882 ] Ismael Juma commented on KAFKA-3979: Thanks for the JIRA and PR. Since this introduces a new config,

[jira] [Updated] (KAFKA-3915) LogCleaner IO buffers do not account for potential size difference due to message format change

[ https://issues.apache.org/jira/browse/KAFKA-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3915: --- Status: Patch Available (was: In Progress) > LogCleaner IO buffers do not account for potential size

[jira] [Commented] (KAFKA-3979) Optimize memory used by replication process by using adaptive fetch message size

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

[jira] [Commented] (KAFKA-3915) LogCleaner IO buffers do not account for potential size difference due to message format change

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

[GitHub] kafka pull request #1643: KAFKA-3915; Don't convert messages from v0 to v1 d...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1643 KAFKA-3915; Don't convert messages from v0 to v1 during log compaction The conversion is unsafe as the converted message size may be greater than the message size limit. Updated

[GitHub] kafka pull request #1642: [KAFKA-3979] Optimize memory used by replication p...

GitHub user nepal opened a pull request: https://github.com/apache/kafka/pull/1642 [KAFKA-3979] Optimize memory used by replication process by using ada… …ptive fetch message size You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (KAFKA-3979) Optimize memory used by replication process by using adaptive fetch message size

Andrey Neporada created KAFKA-3979: -- Summary: Optimize memory used by replication process by using adaptive fetch message size Key: KAFKA-3979 URL: https://issues.apache.org/jira/browse/KAFKA-3979

[jira] [Updated] (KAFKA-3978) Cannot truncate to a negative offset (-1) exception at broker startup

[ https://issues.apache.org/jira/browse/KAFKA-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juho Mäkinen updated KAFKA-3978: Description: During broker startup sequence the broker server.log has this exception. Problem

[jira] [Updated] (KAFKA-3978) Cannot truncate to a negative offset (-1) exception at broker startup

[ https://issues.apache.org/jira/browse/KAFKA-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juho Mäkinen updated KAFKA-3978: Description: During broker startup sequence the broker server.log has this exception. Problem

[jira] [Created] (KAFKA-3978) Cannot truncate to a negative offset (-1) exception at broker startup

Juho Mäkinen created KAFKA-3978: --- Summary: Cannot truncate to a negative offset (-1) exception at broker startup Key: KAFKA-3978 URL: https://issues.apache.org/jira/browse/KAFKA-3978 Project: Kafka

Kafka Streaming Question : reset offset

Hi Experts, I have written Kafka Streaming app that just filters rows based on some condition and load it to MongoDB. The streaming process is working fine but due to some flaw in my code, I want to reprocess whole data again. One way is to do this - kill streaming app , change consumer group