[jira] [Updated] (KAFKA-7560) Client Quota - system test failure

[ https://issues.apache.org/jira/browse/KAFKA-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-7560: Priority: Blocker (was: Major) > Client Quota - system test failure > -- >

[jira] [Commented] (KAFKA-7560) Client Quota - system test failure

[ https://issues.apache.org/jira/browse/KAFKA-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676512#comment-16676512 ] Dong Lin commented on KAFKA-7560: - Initially I thought the test failure is related to quo

[jira] [Commented] (KAFKA-5503) Idempotent producer ignores shutdown while fetching ProducerId

[ https://issues.apache.org/jira/browse/KAFKA-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676621#comment-16676621 ] ASF GitHub Bot commented on KAFKA-5503: --- layfe closed pull request #5881: KAFKA-550

[jira] [Commented] (KAFKA-5503) Idempotent producer ignores shutdown while fetching ProducerId

[ https://issues.apache.org/jira/browse/KAFKA-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676622#comment-16676622 ] ASF GitHub Bot commented on KAFKA-5503: --- layfe opened a new pull request #5881: KAF

[jira] [Created] (KAFKA-7597) Trogdor - Support transactions in ProduceBenchWorker

Stanislav Kozlovski created KAFKA-7597: -- Summary: Trogdor - Support transactions in ProduceBenchWorker Key: KAFKA-7597 URL: https://issues.apache.org/jira/browse/KAFKA-7597 Project: Kafka

[jira] [Commented] (KAFKA-5503) Idempotent producer ignores shutdown while fetching ProducerId

[ https://issues.apache.org/jira/browse/KAFKA-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676715#comment-16676715 ] ASF GitHub Bot commented on KAFKA-5503: --- layfe opened a new pull request #5881: KAF

[jira] [Commented] (KAFKA-5503) Idempotent producer ignores shutdown while fetching ProducerId

[ https://issues.apache.org/jira/browse/KAFKA-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676714#comment-16676714 ] ASF GitHub Bot commented on KAFKA-5503: --- layfe closed pull request #5881: KAFKA-550

[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&focusedCommentId=16676724#comment-16676724 ] Jin Tianfan commented on KAFKA-3980: [~ijuma] [~rsivaram] I meet the same problem.My

[jira] [Commented] (KAFKA-7595) Kafka Streams: KTrable to KTable join introduces duplicates in downstream KTable

[ https://issues.apache.org/jira/browse/KAFKA-7595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676728#comment-16676728 ] Damian Guy commented on KAFKA-7595: --- [~vvcephei] your reasoning seems valid to me > Ka

[jira] [Created] (KAFKA-7598) SIGSEGV on scala library Set

Antoine Tran created KAFKA-7598: --- Summary: SIGSEGV on scala library Set Key: KAFKA-7598 URL: https://issues.apache.org/jira/browse/KAFKA-7598 Project: Kafka Issue Type: Bug Components

[jira] [Commented] (KAFKA-7597) Trogdor - Support transactions in ProduceBenchWorker

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

[jira] [Commented] (KAFKA-7598) SIGSEGV on scala library Set

[ https://issues.apache.org/jira/browse/KAFKA-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676816#comment-16676816 ] Ismael Juma commented on KAFKA-7598: This is a JVM bug and you should report it to th

[jira] [Commented] (KAFKA-5503) Idempotent producer ignores shutdown while fetching ProducerId

[ https://issues.apache.org/jira/browse/KAFKA-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676834#comment-16676834 ] ASF GitHub Bot commented on KAFKA-5503: --- layfe closed pull request #5881: KAFKA-550

[jira] [Commented] (KAFKA-5503) Idempotent producer ignores shutdown while fetching ProducerId

[ https://issues.apache.org/jira/browse/KAFKA-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676835#comment-16676835 ] ASF GitHub Bot commented on KAFKA-5503: --- layfe opened a new pull request #5881: KAF

[jira] [Created] (KAFKA-7599) Trogdor - Allow configuration for not throttling Benchmark Workers and expose messages per second

Stanislav Kozlovski created KAFKA-7599: -- Summary: Trogdor - Allow configuration for not throttling Benchmark Workers and expose messages per second Key: KAFKA-7599 URL: https://issues.apache.org/jira/browse/K

[jira] [Updated] (KAFKA-7599) Trogdor - Allow configuration for not throttling Benchmark Workers and expose messages per second in task status

[ https://issues.apache.org/jira/browse/KAFKA-7599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski updated KAFKA-7599: --- Summary: Trogdor - Allow configuration for not throttling Benchmark Workers and expos

[jira] [Created] (KAFKA-7600) Provide capability to rename cluster id

Yeva Byzek created KAFKA-7600: - Summary: Provide capability to rename cluster id Key: KAFKA-7600 URL: https://issues.apache.org/jira/browse/KAFKA-7600 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-5503) Idempotent producer ignores shutdown while fetching ProducerId

[ https://issues.apache.org/jira/browse/KAFKA-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676895#comment-16676895 ] ASF GitHub Bot commented on KAFKA-5503: --- layfe closed pull request #5881: KAFKA-550

[jira] [Commented] (KAFKA-5503) Idempotent producer ignores shutdown while fetching ProducerId

[ https://issues.apache.org/jira/browse/KAFKA-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676896#comment-16676896 ] ASF GitHub Bot commented on KAFKA-5503: --- layfe opened a new pull request #5881: KAF

[jira] [Commented] (KAFKA-7280) ConcurrentModificationException in FetchSessionHandler in heartbeat thread

[ https://issues.apache.org/jira/browse/KAFKA-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676909#comment-16676909 ] Rajini Sivaram commented on KAFKA-7280: --- [~sachinu] The fix is available in 2.0.1 w

[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&focusedCommentId=16676940#comment-16676940 ] Rajini Sivaram commented on KAFKA-3980: --- [~jintianfan] Do you have quotas enabled?

[jira] [Commented] (KAFKA-7593) Infinite restart loop when failed to store big config for task

[ https://issues.apache.org/jira/browse/KAFKA-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676944#comment-16676944 ] Randall Hauch commented on KAFKA-7593: -- [~olkuznsmith], have you tried manually sett

[jira] [Commented] (KAFKA-6890) Add connector level configurability for producer/consumer client configs

[ https://issues.apache.org/jira/browse/KAFKA-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677049#comment-16677049 ] Allen Tang commented on KAFKA-6890: --- I really appreciate your input, Randall! The KIP

[jira] [Created] (KAFKA-7601) Handle message format downgrades during upgrade of message format version

Jason Gustafson created KAFKA-7601: -- Summary: Handle message format downgrades during upgrade of message format version Key: KAFKA-7601 URL: https://issues.apache.org/jira/browse/KAFKA-7601 Project:

[jira] [Updated] (KAFKA-7601) Handle message format downgrades during upgrade of message format version

[ https://issues.apache.org/jira/browse/KAFKA-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-7601: --- Description: During an upgrade of the message format, there is a short time during which the

[jira] [Updated] (KAFKA-7601) Handle message format downgrades during upgrade of message format version

[ https://issues.apache.org/jira/browse/KAFKA-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-7601: --- Description: During an upgrade of the message format, there is a short time during which the

[jira] [Commented] (KAFKA-7560) Client Quota - system test failure

[ https://issues.apache.org/jira/browse/KAFKA-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677126#comment-16677126 ] Dong Lin commented on KAFKA-7560: - Never mind. I just found the issue. > Client Quota -

[jira] [Commented] (KAFKA-7599) Trogdor - Allow configuration for not throttling Benchmark Workers and expose messages per second in task status

[ https://issues.apache.org/jira/browse/KAFKA-7599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677128#comment-16677128 ] Colin P. McCabe commented on KAFKA-7599: bq. I propose we allow for unbounded `ta

[jira] [Commented] (KAFKA-7531) NPE NullPointerException at TransactionCoordinator handleEndTransaction

[ https://issues.apache.org/jira/browse/KAFKA-7531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677148#comment-16677148 ] Jason Gustafson commented on KAFKA-7531: [~spuzon] Thanks for the extra info. Yea

[jira] [Updated] (KAFKA-7560) PushHttpMetricsReporter should not convert metric value to double

[ https://issues.apache.org/jira/browse/KAFKA-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-7560: Description: Currently metricValue   The test under `kafkatest.tests.client.quota_test.QuotaTest.test_quo

[jira] [Updated] (KAFKA-7560) PushHttpMetricsReporter should not convert metric value to double

[ https://issues.apache.org/jira/browse/KAFKA-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-7560: Summary: PushHttpMetricsReporter should not convert metric value to double (was: Client Quota - system tes

[jira] [Resolved] (KAFKA-7595) Kafka Streams: KTrable to KTable join introduces duplicates in downstream KTable

[ https://issues.apache.org/jira/browse/KAFKA-7595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-7595. Resolution: Not A Bug > Kafka Streams: KTrable to KTable join introduces duplicates in down

[jira] [Commented] (KAFKA-7595) Kafka Streams: KTrable to KTable join introduces duplicates in downstream KTable

[ https://issues.apache.org/jira/browse/KAFKA-7595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677173#comment-16677173 ] Matthias J. Sax commented on KAFKA-7595: Just read [~vvcephei] comments. This is

[jira] [Updated] (KAFKA-7560) PushHttpMetricsReporter should not convert metric value to double

[ https://issues.apache.org/jira/browse/KAFKA-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-7560: Description: Currently PushHttpMetricsReporter will convert value from KafkaMetric.metricValue() to double

[jira] [Commented] (KAFKA-7560) PushHttpMetricsReporter should not convert metric value to double

[ https://issues.apache.org/jira/browse/KAFKA-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677207#comment-16677207 ] ASF GitHub Bot commented on KAFKA-7560: --- lindong28 opened a new pull request #5886:

[jira] [Commented] (KAFKA-6522) Retrying leaderEpoch request for partition xxx as the leader reported an error: UNKNOWN_SERVER_ERROR

[ https://issues.apache.org/jira/browse/KAFKA-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677217#comment-16677217 ] Jaume M commented on KAFKA-6522: Same happens to me by the end of this tutorial if I foll

[jira] [Comment Edited] (KAFKA-6522) Retrying leaderEpoch request for partition xxx as the leader reported an error: UNKNOWN_SERVER_ERROR

[ https://issues.apache.org/jira/browse/KAFKA-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677217#comment-16677217 ] Jaume M edited comment on KAFKA-6522 at 11/6/18 7:33 PM: - Same ha

[jira] [Updated] (KAFKA-7559) ConnectStandaloneFileTest system tests do not pass

[ https://issues.apache.org/jira/browse/KAFKA-7559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-7559: Fix Version/s: 2.1.0 2.0.1 > ConnectStandaloneFileTest system tests do not pass > --

[jira] [Resolved] (KAFKA-7559) ConnectStandaloneFileTest system tests do not pass

[ https://issues.apache.org/jira/browse/KAFKA-7559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-7559. - Resolution: Fixed > ConnectStandaloneFileTest system tests do not pass >

[jira] [Updated] (KAFKA-7313) StopReplicaRequest should attempt to remove future replica for the partition only if future replica exists

[ https://issues.apache.org/jira/browse/KAFKA-7313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-7313: Fix Version/s: (was: 2.1.1) 2.1.0 2.0.1 > StopReplicaRequest shou

[jira] [Commented] (KAFKA-7313) StopReplicaRequest should attempt to remove future replica for the partition only if future replica exists

[ https://issues.apache.org/jira/browse/KAFKA-7313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677229#comment-16677229 ] ASF GitHub Bot commented on KAFKA-7313: --- lindong28 closed pull request #5533: KAFKA

[jira] [Commented] (KAFKA-6522) Retrying leaderEpoch request for partition xxx as the leader reported an error: UNKNOWN_SERVER_ERROR

[ https://issues.apache.org/jira/browse/KAFKA-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677302#comment-16677302 ] Jaume M commented on KAFKA-6522: I believe this is happening to me because there were som

[jira] [Commented] (KAFKA-6812) Async ConsoleProducer exits with 0 status even after data loss

[ https://issues.apache.org/jira/browse/KAFKA-6812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677312#comment-16677312 ] Kamal Kang commented on KAFKA-6812: --- [~enether], sure, I can write KIP for this issue.

[jira] [Assigned] (KAFKA-7481) Consider options for safer upgrade of offset commit value schema

[ https://issues.apache.org/jira/browse/KAFKA-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin reassigned KAFKA-7481: --- Assignee: Jason Gustafson > Consider options for safer upgrade of offset commit value schema > -

[jira] [Commented] (KAFKA-7481) Consider options for safer upgrade of offset commit value schema

[ https://issues.apache.org/jira/browse/KAFKA-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677334#comment-16677334 ] ASF GitHub Bot commented on KAFKA-7481: --- lindong28 closed pull request #5857: KAFKA

[jira] [Reopened] (KAFKA-7481) Consider options for safer upgrade of offset commit value schema

[ https://issues.apache.org/jira/browse/KAFKA-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin reopened KAFKA-7481: - > Consider options for safer upgrade of offset commit value schema >

[jira] [Resolved] (KAFKA-7481) Consider options for safer upgrade of offset commit value schema

[ https://issues.apache.org/jira/browse/KAFKA-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-7481. - Resolution: Fixed > Consider options for safer upgrade of offset commit value schema > --

[jira] [Created] (KAFKA-7602) Improve usage of @see tag in Streams JavaDocs

Matthias J. Sax created KAFKA-7602: -- Summary: Improve usage of @see tag in Streams JavaDocs Key: KAFKA-7602 URL: https://issues.apache.org/jira/browse/KAFKA-7602 Project: Kafka Issue Type: I

[jira] [Commented] (KAFKA-7537) Only include live brokers in the UpdateMetadataRequest sent to existing brokers if there is no change in the partition states

[ https://issues.apache.org/jira/browse/KAFKA-7537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677407#comment-16677407 ] ASF GitHub Bot commented on KAFKA-7537: --- junrao closed pull request #5869: KAFKA-7

[jira] [Resolved] (KAFKA-7537) Only include live brokers in the UpdateMetadataRequest sent to existing brokers if there is no change in the partition states

[ https://issues.apache.org/jira/browse/KAFKA-7537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-7537. Resolution: Fixed Fix Version/s: 2.2.0 Merged the PR to trunk. > Only include live brokers in the U

[jira] [Updated] (KAFKA-7481) Consider options for safer upgrade of offset commit value schema

[ https://issues.apache.org/jira/browse/KAFKA-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-7481: Fix Version/s: (was: 2.1.0) 2.2.0 > Consider options for safer upgrade of offset com

[jira] [Resolved] (KAFKA-7313) StopReplicaRequest should attempt to remove future replica for the partition only if future replica exists

[ https://issues.apache.org/jira/browse/KAFKA-7313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-7313. - Resolution: Fixed > StopReplicaRequest should attempt to remove future replica for the partition > only

[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 ] Jin Tianfan updated KAFKA-3980: --- Attachment: heap_img.png > JmxReporter uses excessive memory causing OutOfMemoryException > -

[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&focusedCommentId=16677601#comment-16677601 ] Jin Tianfan commented on KAFKA-3980: [~rsivaram]  Unfortunately，we did not open jmx p

[jira] [Comment Edited] (KAFKA-7593) Infinite restart loop when failed to store big config for task

[ https://issues.apache.org/jira/browse/KAFKA-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677704#comment-16677704 ] Oleg Kuznetsov edited comment on KAFKA-7593 at 11/7/18 5:23 AM: ---

[jira] [Commented] (KAFKA-7593) Infinite restart loop when failed to store big config for task

[ https://issues.apache.org/jira/browse/KAFKA-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677704#comment-16677704 ] Oleg Kuznetsov commented on KAFKA-7593: --- [~rhauch] Sure, workaround is clear, but t

[jira] [Comment Edited] (KAFKA-7593) Infinite restart loop when failed to store big config for task

[ https://issues.apache.org/jira/browse/KAFKA-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677704#comment-16677704 ] Oleg Kuznetsov edited comment on KAFKA-7593 at 11/7/18 5:27 AM: ---