[jira] [Commented] (KAFKA-6185) java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243482#comment-16243482 ] Ismael Juma commented on KAFKA-6185: [~brettrann], the 0.11.0.1 brokers don't have the

[jira] [Commented] (KAFKA-6184) report a metric of the lag between the consumer offset and the start offset of the log

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

[jira] [Updated] (KAFKA-6185) java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6185: --- Priority: Blocker (was: Major) > java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on dis

[jira] [Updated] (KAFKA-6185) java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6185: --- Fix Version/s: 1.0.1 > java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and > co

[jira] [Commented] (KAFKA-6185) java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243511#comment-16243511 ] Brett Rann commented on KAFKA-6185: --- [~ijuma] that's right, the 0.11.0.1 brokers are the

[jira] [Comment Edited] (KAFKA-6185) java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243511#comment-16243511 ] Brett Rann edited comment on KAFKA-6185 at 11/8/17 8:20 AM: [~

[jira] [Comment Edited] (KAFKA-6185) java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243511#comment-16243511 ] Brett Rann edited comment on KAFKA-6185 at 11/8/17 8:23 AM: [~

[jira] [Assigned] (KAFKA-6184) report a metric of the lag between the consumer offset and the start offset of the log

[ https://issues.apache.org/jira/browse/KAFKA-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-6184: - Assignee: huxihx (was: Vahid Hashemian) > report a metric of the lag between the consumer offset and the

[jira] [Assigned] (KAFKA-6185) java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-6185: -- Assignee: Ismael Juma > java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk a

[jira] [Assigned] (KAFKA-6185) java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-6185: -- Assignee: Rajini Sivaram (was: Ismael Juma) > java.lang.OutOfMemoryError memory leak on 1.0.0

[jira] [Commented] (KAFKA-6185) java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243580#comment-16243580 ] Ismael Juma commented on KAFKA-6185: [~brett_s_r], two questions: 1. Seems like compre

[jira] [Commented] (KAFKA-6185) java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243630#comment-16243630 ] Ismael Juma commented on KAFKA-6185: One more question: no quotas are set, right? > j

[jira] [Commented] (KAFKA-5716) Connect: When SourceTask.commit it is possible not everthing from SourceTask.poll has been sent

[ https://issues.apache.org/jira/browse/KAFKA-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243639#comment-16243639 ] Per Steffensen commented on KAFKA-5716: --- Please comment! Is the PR OK, or do you wa

[jira] [Commented] (KAFKA-6185) java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243653#comment-16243653 ] Rajini Sivaram commented on KAFKA-6185: --- [~brettrann] Can you enable heap dump on OO

[jira] [Commented] (KAFKA-6180) AbstractConfig.getList() should never return null

[ https://issues.apache.org/jira/browse/KAFKA-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243710#comment-16243710 ] Charly Molter commented on KAFKA-6180: -- I don't have the Jira access to assign myself

[jira] [Created] (KAFKA-6186) RocksDB based WindowStore fail to create db file on Windows OS

James Wu created KAFKA-6186: --- Summary: RocksDB based WindowStore fail to create db file on Windows OS Key: KAFKA-6186 URL: https://issues.apache.org/jira/browse/KAFKA-6186 Project: Kafka Issue Typ

[jira] [Resolved] (KAFKA-6186) RocksDB based WindowStore fail to create db file on Windows OS

[ https://issues.apache.org/jira/browse/KAFKA-6186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-6186. --- Resolution: Duplicate > RocksDB based WindowStore fail to create db file on Windows OS > -

[jira] [Created] (KAFKA-6187) Remove the Logging class in favor of LazyLogging in scala-logging

Viktor Somogyi created KAFKA-6187: - Summary: Remove the Logging class in favor of LazyLogging in scala-logging Key: KAFKA-6187 URL: https://issues.apache.org/jira/browse/KAFKA-6187 Project: Kafka

[jira] [Updated] (KAFKA-6187) Remove the Logging class in favor of LazyLogging in scala-logging

[ https://issues.apache.org/jira/browse/KAFKA-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi updated KAFKA-6187: -- Description: In KAFKA-1044 we removed the hard dependency on junit and enabled users to exclude

[jira] [Created] (KAFKA-6188) Broker fails with FATAL Shutdown - log dirs have failed

Valentina Baljak created KAFKA-6188: --- Summary: Broker fails with FATAL Shutdown - log dirs have failed Key: KAFKA-6188 URL: https://issues.apache.org/jira/browse/KAFKA-6188 Project: Kafka I

[jira] [Updated] (KAFKA-6188) Broker fails with FATAL Shutdown - log dirs have failed

[ https://issues.apache.org/jira/browse/KAFKA-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentina Baljak updated KAFKA-6188: Description: Just started with version 1.0.0 after a 4-5 months of using 0.10.2.1. The test

[jira] [Commented] (KAFKA-6188) Broker fails with FATAL Shutdown - log dirs have failed

[ https://issues.apache.org/jira/browse/KAFKA-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243984#comment-16243984 ] Ismael Juma commented on KAFKA-6188: Thanks for the report. Might be related to the fa

[jira] [Updated] (KAFKA-6185) Selector memory leak with high likelihood of OOM if down conversion

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6185: --- Summary: Selector memory leak with high likelihood of OOM if down conversion (was: java.lang.OutOfMem

[jira] [Updated] (KAFKA-6185) Selector memory leak with high likelihood of OOM in case of down conversion

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6185: --- Summary: Selector memory leak with high likelihood of OOM in case of down conversion (was: Selector m

[jira] [Commented] (KAFKA-6188) Broker fails with FATAL Shutdown - log dirs have failed

[ https://issues.apache.org/jira/browse/KAFKA-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244015#comment-16244015 ] Valentina Baljak commented on KAFKA-6188: - Thank you for the response. When you sa

[jira] [Updated] (KAFKA-6185) Selector memory leak with high likelihood of OOM in case of down conversion

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6185: --- Labels: regression (was: regresion) > Selector memory leak with high likelihood of OOM in case of dow

[jira] [Updated] (KAFKA-6185) Selector memory leak with high likelihood of OOM in case of down conversion

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6185: --- Labels: regresion (was: ) > Selector memory leak with high likelihood of OOM in case of down conversi

[jira] [Commented] (KAFKA-6185) Selector memory leak with high likelihood of OOM in case of down conversion

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244022#comment-16244022 ] Ismael Juma commented on KAFKA-6185: [~rsivaram] and I have been looking at this and t

[jira] [Commented] (KAFKA-6188) Broker fails with FATAL Shutdown - log dirs have failed

[ https://issues.apache.org/jira/browse/KAFKA-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244063#comment-16244063 ] Ismael Juma commented on KAFKA-6188: We recommend Linux and macOS as we test under tho

[jira] [Commented] (KAFKA-6185) Selector memory leak with high likelihood of OOM in case of down conversion

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244158#comment-16244158 ] Manikumar commented on KAFKA-6185: -- @ijuma Heap histogram is also contains large number

[jira] [Commented] (KAFKA-6185) Selector memory leak with high likelihood of OOM in case of down conversion

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244167#comment-16244167 ] Ismael Juma commented on KAFKA-6185: Yes, a heap dump provided by Brett is how we came

[jira] [Updated] (KAFKA-6189) Loosing messages while getting OFFSET_OUT_OF_RANGE error in consumer

[ https://issues.apache.org/jira/browse/KAFKA-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey updated KAFKA-6189: -- Summary: Loosing messages while getting OFFSET_OUT_OF_RANGE error in consumer (was: Loosing messages while gett

[jira] [Created] (KAFKA-6189) Loosing messages while getting OFFSET_OUT_OF_RANGE eror in consumer

Andrey created KAFKA-6189: - Summary: Loosing messages while getting OFFSET_OUT_OF_RANGE eror in consumer Key: KAFKA-6189 URL: https://issues.apache.org/jira/browse/KAFKA-6189 Project: Kafka Issue Ty

[jira] [Updated] (KAFKA-6189) Loosing messages while getting OFFSET_OUT_OF_RANGE eror in consumer

[ https://issues.apache.org/jira/browse/KAFKA-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey updated KAFKA-6189: -- Description: Steps to reproduce: * Setup test: ** producer sends messages constantly. If cluster not available,

[jira] [Updated] (KAFKA-6189) Loosing messages on OFFSET_OUT_OF_RANGE error in consumer

[ https://issues.apache.org/jira/browse/KAFKA-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey updated KAFKA-6189: -- Summary: Loosing messages on OFFSET_OUT_OF_RANGE error in consumer (was: Loosing messages while getting OFFSET_

[jira] [Commented] (KAFKA-6184) report a metric of the lag between the consumer offset and the start offset of the log

[ https://issues.apache.org/jira/browse/KAFKA-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244198#comment-16244198 ] Vahid Hashemian commented on KAFKA-6184: [~huxi_2b] For next time, could you pleas

[jira] [Commented] (KAFKA-6185) Selector memory leak with high likelihood of OOM in case of down conversion

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

[jira] [Commented] (KAFKA-6184) report a metric of the lag between the consumer offset and the start offset of the log

[ https://issues.apache.org/jira/browse/KAFKA-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244270#comment-16244270 ] Jun Rao commented on KAFKA-6184: [~huxi_2b], thanks for your the patch. Since this is a pu

[jira] [Assigned] (KAFKA-6096) Add concurrent tests to exercise all paths in group/transaction managers

[ https://issues.apache.org/jira/browse/KAFKA-6096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-6096: -- Assignee: Rajini Sivaram (was: Jason Gustafson) > Add concurrent tests to exercise all paths i

[jira] [Commented] (KAFKA-2605) Replace `catch: Throwable` clauses with `NonFatal` or `NonControl`

[ https://issues.apache.org/jira/browse/KAFKA-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244333#comment-16244333 ] Mike Hurley commented on KAFKA-2605: This isn't just a problem in the scala code. The

[jira] [Commented] (KAFKA-5645) Use async ZookeeperClient in SimpleAclAuthorizer

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

[jira] [Commented] (KAFKA-5646) Use async ZookeeperClient for DynamicConfigManager

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

[jira] [Commented] (KAFKA-5811) Trogdor should handle injecting disk faults

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

[jira] [Resolved] (KAFKA-6179) RecordQueue.clear() does not clear MinTimestampTracker's maintained list

[ https://issues.apache.org/jira/browse/KAFKA-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6179. -- Resolution: Fixed Fix Version/s: 0.11.0.2 1.1.0 1.0.

[jira] [Commented] (KAFKA-6179) RecordQueue.clear() does not clear MinTimestampTracker's maintained list

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

[jira] [Created] (KAFKA-6190) GlobalKTable never finishes restoring when consuming transactional messages

Alex Good created KAFKA-6190: Summary: GlobalKTable never finishes restoring when consuming transactional messages Key: KAFKA-6190 URL: https://issues.apache.org/jira/browse/KAFKA-6190 Project: Kafka

[jira] [Commented] (KAFKA-6190) GlobalKTable never finishes restoring when consuming transactional messages

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

[jira] [Updated] (KAFKA-6190) GlobalKTable never finishes restoring when consuming transactional messages

[ https://issues.apache.org/jira/browse/KAFKA-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Good updated KAFKA-6190: - Flags: Patch External issue URL: https://github.com/apache/kafka/pull/4197 > GlobalKTable

[jira] [Updated] (KAFKA-6190) GlobalKTable never finishes restoring when consuming transactional messages

[ https://issues.apache.org/jira/browse/KAFKA-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6190: --- Affects Version/s: 0.11.0.1 1.0.0 > GlobalKTable never finishes restori

[jira] [Updated] (KAFKA-6190) GlobalKTable never finishes restoring when consuming transactional messages

[ https://issues.apache.org/jira/browse/KAFKA-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6190: --- Fix Version/s: 1.0.1 0.11.0.2 > GlobalKTable never finishes restoring when

[jira] [Updated] (KAFKA-6190) GlobalKTable never finishes restoring when consuming transactional messages

[ https://issues.apache.org/jira/browse/KAFKA-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6190: --- Component/s: (was: clients) streams > GlobalKTable never finishes restori

[jira] [Updated] (KAFKA-6190) GlobalKTable never finishes restoring when consuming transactional messages

[ https://issues.apache.org/jira/browse/KAFKA-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6190: --- Fix Version/s: 1.1.0 > GlobalKTable never finishes restoring when consuming transactional mess

[jira] [Commented] (KAFKA-6185) Selector memory leak with high likelihood of OOM in case of down conversion

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244999#comment-16244999 ] Brett Rann commented on KAFKA-6185: --- Moved this to slack last night to make the most of

[jira] [Commented] (KAFKA-6185) Selector memory leak with high likelihood of OOM in case of down conversion

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245005#comment-16245005 ] Ismael Juma commented on KAFKA-6185: [~brettrann], you can either try Rajini's branch

[jira] [Comment Edited] (KAFKA-6185) Selector memory leak with high likelihood of OOM in case of down conversion

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244999#comment-16244999 ] Brett Rann edited comment on KAFKA-6185 at 11/9/17 12:34 AM: -

[jira] [Updated] (KAFKA-6190) GlobalKTable never finishes restoring when consuming transactional messages

[ https://issues.apache.org/jira/browse/KAFKA-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-6190: - Priority: Blocker (was: Major) > GlobalKTable never finishes restoring when consuming transaction

[jira] [Assigned] (KAFKA-6190) GlobalKTable never finishes restoring when consuming transactional messages

[ https://issues.apache.org/jira/browse/KAFKA-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-6190: Assignee: Alex Good > GlobalKTable never finishes restoring when consuming transactional me

[jira] [Assigned] (KAFKA-5029) cleanup javadocs and logging

[ https://issues.apache.org/jira/browse/KAFKA-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5029: -- Assignee: Ismael Juma (was: Onur Karaman) > cleanup javadocs and logging > ---

[jira] [Commented] (KAFKA-6146) minimize the number of triggers enqueuing PreferredReplicaLeaderElection events

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

[jira] [Resolved] (KAFKA-6146) minimize the number of triggers enqueuing PreferredReplicaLeaderElection events

[ https://issues.apache.org/jira/browse/KAFKA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6146. Resolution: Fixed > minimize the number of triggers enqueuing PreferredReplicaLeaderElection > even

[jira] [Resolved] (KAFKA-6066) Use of SimpleDateFormat in RocksDBWindowStore may not be Threadsafe

[ https://issues.apache.org/jira/browse/KAFKA-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Sundarrajan resolved KAFKA-6066. - Resolution: Not A Problem Thanks. Marking this as closed > Use of SimpleDateForma

[jira] [Commented] (KAFKA-6184) report a metric of the lag between the consumer offset and the start offset of the log

[ https://issues.apache.org/jira/browse/KAFKA-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245146#comment-16245146 ] huxihx commented on KAFKA-6184: --- [~vahid] It's kind of weird. The assignee was empty when I

[jira] [Assigned] (KAFKA-6184) report a metric of the lag between the consumer offset and the start offset of the log

[ https://issues.apache.org/jira/browse/KAFKA-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-6184: - Assignee: Vahid Hashemian (was: huxihx) > report a metric of the lag between the consumer offset and the

[jira] [Commented] (KAFKA-3554) Generate actual data with specific compression ratio and add multi-thread support in the ProducerPerformance tool.

[ https://issues.apache.org/jira/browse/KAFKA-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245266#comment-16245266 ] Chen He commented on KAFKA-3554: This is a great feature, [~becket_qin]. What can I do for

[jira] [Commented] (KAFKA-6165) Kafka Brokers goes down with outOfMemoryError.

[ https://issues.apache.org/jira/browse/KAFKA-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245321#comment-16245321 ] kaushik srinivas commented on KAFKA-6165: - Hi Huxihx, Thanks for the feedback. w

[jira] [Updated] (KAFKA-6165) Kafka Brokers goes down with outOfMemoryError.

[ https://issues.apache.org/jira/browse/KAFKA-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kaushik srinivas updated KAFKA-6165: Attachment: config.json kafkaServer-gc-agent06.7z map_counts_