[jira] [Assigned] (KAFKA-8792) Default ZK configuration to disable AdminServer

[ https://issues.apache.org/jira/browse/KAFKA-8792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira reassigned KAFKA-8792: --- Assignee: Gwen Shapira > Default ZK configuration to disable AdminServer >

[jira] [Assigned] (KAFKA-7499) Extend ProductionExceptionHandler to cover serialization exceptions

[ https://issues.apache.org/jira/browse/KAFKA-7499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kamal Chandraprakash reassigned KAFKA-7499: --- Assignee: (was: Kamal Chandraprakash) > Extend

[jira] [Commented] (KAFKA-7499) Extend ProductionExceptionHandler to cover serialization exceptions

[ https://issues.apache.org/jira/browse/KAFKA-7499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905830#comment-16905830 ] ASF GitHub Bot commented on KAFKA-7499: --- kamalcph commented on pull request #5969: KAFKA-7499:

[jira] [Commented] (KAFKA-8792) Default ZK configuration to disable AdminServer

[ https://issues.apache.org/jira/browse/KAFKA-8792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905828#comment-16905828 ] ASF GitHub Bot commented on KAFKA-8792: --- gwenshap commented on pull request #7203: KAFKA-8792;

[jira] [Commented] (KAFKA-8792) Default ZK configuration to disable AdminServer

[ https://issues.apache.org/jira/browse/KAFKA-8792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905827#comment-16905827 ] Sönke Liebau commented on KAFKA-8792: - I agree, port 8080 tends to be one of the first ports software

[jira] [Created] (KAFKA-8792) Default ZK configuration to disable AdminServer

Gwen Shapira created KAFKA-8792: --- Summary: Default ZK configuration to disable AdminServer Key: KAFKA-8792 URL: https://issues.apache.org/jira/browse/KAFKA-8792 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-8522) Tombstones can survive forever

[ https://issues.apache.org/jira/browse/KAFKA-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905792#comment-16905792 ] Jun Rao commented on KAFKA-8522: [~Yohan123]: For upgrade, we can roughly do the following. If the new

[jira] [Commented] (KAFKA-8522) Tombstones can survive forever

[ https://issues.apache.org/jira/browse/KAFKA-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905747#comment-16905747 ] Richard Yu commented on KAFKA-8522: --- [~jagsancio] any thoughts? > Tombstones can survive forever >

[jira] [Updated] (KAFKA-8791) RocksDBTimestampedStore should open in regular mode for new stores

[ https://issues.apache.org/jira/browse/KAFKA-8791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-8791: --- Description:

[jira] [Updated] (KAFKA-8791) RocksDBTimestampedStore should open in regular mode for new stores

[ https://issues.apache.org/jira/browse/KAFKA-8791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-8791: --- Description:

[jira] [Updated] (KAFKA-8791) RocksDBTimestampedStore should open in regular mode for new stores

[ https://issues.apache.org/jira/browse/KAFKA-8791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-8791: --- Summary: RocksDBTimestampedStore should open in regular mode for new stores (was:

[jira] [Updated] (KAFKA-8774) Connect REST API exposes plaintext secrets in tasks endpoint if config value contains additional characters

[ https://issues.apache.org/jira/browse/KAFKA-8774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Satish updated KAFKA-8774: Summary: Connect REST API exposes plaintext secrets in tasks endpoint if config value contains

[jira] [Commented] (KAFKA-8791) RocksDBTimestampeStore should open in regular mode for new store

[ https://issues.apache.org/jira/browse/KAFKA-8791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905713#comment-16905713 ] ASF GitHub Bot commented on KAFKA-8791: --- mjsax commented on pull request #7201: KAFKA-8791:

[jira] [Updated] (KAFKA-8774) Connect REST API exposes plaintext secrets in tasks endpoint

[ https://issues.apache.org/jira/browse/KAFKA-8774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Satish updated KAFKA-8774: Description: I have configured a Connector to use externalized secrets, and the following

[jira] [Assigned] (KAFKA-8791) RocksDBTimestampeStore should open in regular mode for new store

[ https://issues.apache.org/jira/browse/KAFKA-8791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-8791: -- Assignee: Matthias J. Sax > RocksDBTimestampeStore should open in regular mode for

[jira] [Comment Edited] (KAFKA-8789) kafka-console-consumer timeout-ms setting behaves incorrectly with older client

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905510#comment-16905510 ] Raman Gupta edited comment on KAFKA-8789 at 8/12/19 11:11 PM: -- The problem

[jira] [Issue Comment Deleted] (KAFKA-8789) kafka-console-consumer timeout-ms setting behaves incorrectly with older client

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raman Gupta updated KAFKA-8789: --- Comment: was deleted (was: And the same behavior for the regular console consumer: {code:java}

[jira] [Comment Edited] (KAFKA-8789) kafka-console-consumer timeout-ms setting behaves incorrectly with older client

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905510#comment-16905510 ] Raman Gupta edited comment on KAFKA-8789 at 8/12/19 11:09 PM: -- I'm reopening

[jira] [Updated] (KAFKA-8789) kafka-console-consumer timeout-ms setting behaves incorrectly with older client

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raman Gupta updated KAFKA-8789: --- Description: I have a topic with about 20,000 events in it, running on a Kafka 2.3.0 broker. When I

[jira] [Issue Comment Deleted] (KAFKA-8789) kafka-console-consumer timeout-ms setting behaves incorrectly with older client

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raman Gupta updated KAFKA-8789: --- Comment: was deleted (was: UPDATE: The error message may be coming from the schema registry, which

[jira] [Updated] (KAFKA-8789) kafka-console-consumer timeout-ms setting behaves incorrectly with older client

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raman Gupta updated KAFKA-8789: --- Summary: kafka-console-consumer timeout-ms setting behaves incorrectly with older client (was:

[jira] [Commented] (KAFKA-8789) kafka-console-consumer needs bigger timeout-ms setting in order to work

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905652#comment-16905652 ] Raman Gupta commented on KAFKA-8789: And the same behavior for the regular console consumer:

[jira] [Commented] (KAFKA-8412) Still a nullpointer exception thrown on shutdown while flushing before closing producers

[ https://issues.apache.org/jira/browse/KAFKA-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905598#comment-16905598 ] Chris Pettitt commented on KAFKA-8412: -- Having played with this a bit more I think its best to go

[jira] [Commented] (KAFKA-8601) Producer Improvement: Sticky Partitioner

[ https://issues.apache.org/jira/browse/KAFKA-8601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905585#comment-16905585 ] Justine Olshan commented on KAFKA-8601: --- Just have one more PR for this (implementing the

[jira] [Commented] (KAFKA-8601) Producer Improvement: Sticky Partitioner

[ https://issues.apache.org/jira/browse/KAFKA-8601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905571#comment-16905571 ] ASF GitHub Bot commented on KAFKA-8601: --- jolshan commented on pull request #7199: KAFKA-8601:

[jira] [Updated] (KAFKA-4545) tombstone needs to be removed after delete.retention.ms has passed after it has been cleaned

[ https://issues.apache.org/jira/browse/KAFKA-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-4545: Priority: Minor (was: Major) > tombstone needs to be removed after delete.retention.ms has passed

[jira] [Updated] (KAFKA-8522) Tombstones can survive forever

[ https://issues.apache.org/jira/browse/KAFKA-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-8522: Issue Type: Improvement (was: Bug) > Tombstones can survive forever >

[jira] [Updated] (KAFKA-4545) tombstone needs to be removed after delete.retention.ms has passed after it has been cleaned

[ https://issues.apache.org/jira/browse/KAFKA-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-4545: Issue Type: Improvement (was: Bug) > tombstone needs to be removed after delete.retention.ms has

[jira] [Comment Edited] (KAFKA-8789) kafka-console-consumer needs bigger timeout-ms setting in order to work

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905510#comment-16905510 ] Raman Gupta edited comment on KAFKA-8789 at 8/12/19 7:49 PM: - I'm reopening

[jira] [Updated] (KAFKA-8789) kafka-console-consumer needs bigger timeout-ms setting in order to work

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raman Gupta updated KAFKA-8789: --- Summary: kafka-console-consumer needs bigger timeout-ms setting in order to work (was:

[jira] [Comment Edited] (KAFKA-8789) kafka-console-consumer performance regression

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905510#comment-16905510 ] Raman Gupta edited comment on KAFKA-8789 at 8/12/19 7:23 PM: - I'm reopening

[jira] [Comment Edited] (KAFKA-8789) kafka-console-consumer performance regression

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905510#comment-16905510 ] Raman Gupta edited comment on KAFKA-8789 at 8/12/19 7:22 PM: - I'm reopening

[jira] [Commented] (KAFKA-8789) kafka-console-consumer performance regression

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905510#comment-16905510 ] Raman Gupta commented on KAFKA-8789: I'm reopening this. The problem does not appear to be with the

[jira] [Commented] (KAFKA-8790) [kafka-connect] KafkaBaseLog.WorkThread not recoverable

[ https://issues.apache.org/jira/browse/KAFKA-8790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905506#comment-16905506 ] Qinghui Xu commented on KAFKA-8790: --- [~pgwhalen] Thanks for the hint, I'll have a look at your PR. >

[jira] [Comment Edited] (KAFKA-8789) kafka-console-consumer performance regression

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905343#comment-16905343 ] Raman Gupta edited comment on KAFKA-8789 at 8/12/19 7:03 PM: - UPDATE: The

[jira] [Updated] (KAFKA-8789) kafka-console-consumer performance regression

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raman Gupta updated KAFKA-8789: --- Summary: kafka-console-consumer performance regression (was: kafka-avro-console-consumer works with

[jira] [Reopened] (KAFKA-8789) kafka-avro-console-consumer works with 2.0.x, but not 2.3.x

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raman Gupta reopened KAFKA-8789: > kafka-avro-console-consumer works with 2.0.x, but not 2.3.x >

[jira] [Commented] (KAFKA-8790) [kafka-connect] KafkaBaseLog.WorkThread not recoverable

[ https://issues.apache.org/jira/browse/KAFKA-8790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905460#comment-16905460 ] Paul Whalen commented on KAFKA-8790: Looks like KAFKA-7941. My team is running a fork of 2.0.0 with

[jira] [Commented] (KAFKA-8412) Still a nullpointer exception thrown on shutdown while flushing before closing producers

[ https://issues.apache.org/jira/browse/KAFKA-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905459#comment-16905459 ] Chris Pettitt commented on KAFKA-8412: -- I'm able to repro this and [~mjsax]'s solution should fix

[jira] [Comment Edited] (KAFKA-7149) Reduce assignment data size to improve kafka streams scalability

[ https://issues.apache.org/jira/browse/KAFKA-7149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905430#comment-16905430 ] Vinoth Chandar edited comment on KAFKA-7149 at 8/12/19 5:47 PM: While

[jira] [Commented] (KAFKA-7149) Reduce assignment data size to improve kafka streams scalability

[ https://issues.apache.org/jira/browse/KAFKA-7149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905430#comment-16905430 ] Vinoth Chandar commented on KAFKA-7149: --- While looking at changes to detect topology changes,

[jira] [Commented] (KAFKA-8041) Flaky Test LogDirFailureTest#testIOExceptionDuringLogRoll

[ https://issues.apache.org/jira/browse/KAFKA-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905426#comment-16905426 ] Sophie Blee-Goldman commented on KAFKA-8041: h3. java.util.concurrent.ExecutionException:

[jira] [Comment Edited] (KAFKA-8789) kafka-avro-console-consumer works with 2.0.x, but not 2.3.x

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905343#comment-16905343 ] Raman Gupta edited comment on KAFKA-8789 at 8/12/19 5:06 PM: - UPDATE: The

[jira] [Commented] (KAFKA-8558) KIP-479 - Add Materialized Overload to KStream#Join

[ https://issues.apache.org/jira/browse/KAFKA-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905380#comment-16905380 ] Bill Bejeck commented on KAFKA-8558: [~apurva] > Bill, where are we with fixing this? I've started

[jira] [Commented] (KAFKA-8522) Tombstones can survive forever

[ https://issues.apache.org/jira/browse/KAFKA-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905377#comment-16905377 ] Richard Yu commented on KAFKA-8522: --- [~junrao] A thought just occurred to me. Wouldn't we need to

[jira] [Created] (KAFKA-8790) [kafka-connect] KafkaBaseLog.WorkThread not recoverable

Qinghui Xu created KAFKA-8790: - Summary: [kafka-connect] KafkaBaseLog.WorkThread not recoverable Key: KAFKA-8790 URL: https://issues.apache.org/jira/browse/KAFKA-8790 Project: Kafka Issue Type:

[jira] [Comment Edited] (KAFKA-8789) kafka-avro-console-consumer works with 2.0.x, but not 2.3.x

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905343#comment-16905343 ] Raman Gupta edited comment on KAFKA-8789 at 8/12/19 4:16 PM: - UPDATE: The

[jira] [Comment Edited] (KAFKA-8789) kafka-avro-console-consumer works with 2.0.x, but not 2.3.x

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905343#comment-16905343 ] Raman Gupta edited comment on KAFKA-8789 at 8/12/19 4:16 PM: - UPDATE: The

[jira] [Resolved] (KAFKA-8789) kafka-avro-console-consumer works with 2.0.x, but not 2.3.x

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raman Gupta resolved KAFKA-8789. Resolution: Invalid UPDATE: The error message may be coming from the schema registry, which would

[jira] [Updated] (KAFKA-8789) kafka-avro-console-consumer works with 2.0.x, but not 2.3.x

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raman Gupta updated KAFKA-8789: --- Description: I have a topic with about 20,000 events in it. When I run the following tools command

[jira] [Created] (KAFKA-8789) kafka-avro-console-consumer works with confluent 5.0.3, but not 5.3.0

Raman Gupta created KAFKA-8789: -- Summary: kafka-avro-console-consumer works with confluent 5.0.3, but not 5.3.0 Key: KAFKA-8789 URL: https://issues.apache.org/jira/browse/KAFKA-8789 Project: Kafka

[jira] [Updated] (KAFKA-8789) kafka-avro-console-consumer works with 2.0.x, but not 2.3.x

[ https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raman Gupta updated KAFKA-8789: --- Summary: kafka-avro-console-consumer works with 2.0.x, but not 2.3.x (was: