[jira] [Commented] (KAFKA-5904) Create Connect metrics for worker rebalances

[ https://issues.apache.org/jira/browse/KAFKA-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190826#comment-16190826 ] Randall Hauch commented on KAFKA-5904: -- The changes for this issue were included in the PR for

[jira] [Commented] (KAFKA-5903) Create Connect metrics for workers

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

[jira] [Updated] (KAFKA-5993) Kafka Admin Client throws a warning for sasl.jaas.config

[ https://issues.apache.org/jira/browse/KAFKA-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Maarek updated KAFKA-5993: --- Summary: Kafka Admin Client throws a warning for sasl.jaas.config (was: Kafka AdminClient

[jira] [Comment Edited] (KAFKA-5993) Kafka AdminClient does not support standard security settings

[ https://issues.apache.org/jira/browse/KAFKA-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190808#comment-16190808 ] Stephane Maarek edited comment on KAFKA-5993 at 10/4/17 4:52 AM: - [~ijuma]

[jira] [Commented] (KAFKA-5993) Kafka AdminClient does not support standard security settings

[ https://issues.apache.org/jira/browse/KAFKA-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190808#comment-16190808 ] Stephane Maarek commented on KAFKA-5993: [~ijuma] Indeed it does support security settings. The

[jira] [Updated] (KAFKA-5991) Change Consumer per partition lag metrics to put topic-partition-id in tags instead of metric name

[ https://issues.apache.org/jira/browse/KAFKA-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Lu updated KAFKA-5991: Component/s: metrics > Change Consumer per partition lag metrics to put topic-partition-id in tags >

[jira] [Commented] (KAFKA-5758) Reassigning a topic's partitions can adversely impact other topics

[ https://issues.apache.org/jira/browse/KAFKA-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190609#comment-16190609 ] Jun Rao commented on KAFKA-5758: [~dwvangeest], thanks for the info. > Reassigning a topic's partitions

[jira] [Created] (KAFKA-6007) Connect can't validate against transforms in plugins.path

Stephane Maarek created KAFKA-6007: -- Summary: Connect can't validate against transforms in plugins.path Key: KAFKA-6007 URL: https://issues.apache.org/jira/browse/KAFKA-6007 Project: Kafka

[jira] [Commented] (KAFKA-5902) Create Connect metrics for sink tasks

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

[jira] [Resolved] (KAFKA-5902) Create Connect metrics for sink tasks

[ https://issues.apache.org/jira/browse/KAFKA-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5902. -- Resolution: Fixed Issue resolved by pull request 3975

[jira] [Commented] (KAFKA-4108) Improve DumpLogSegments offsets-decoder output format

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

[jira] [Commented] (KAFKA-5758) Reassigning a topic's partitions can adversely impact other topics

[ https://issues.apache.org/jira/browse/KAFKA-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190025#comment-16190025 ] David van Geest commented on KAFKA-5758: [~junrao] yeah, I'm not 100% sure either that it's the

[jira] [Commented] (KAFKA-5909) Remove source jars from classpath while executing CLI tools

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

[jira] [Commented] (KAFKA-5909) Remove source jars from classpath while executing CLI tools

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

[jira] [Updated] (KAFKA-6006) Default replication factor for all topics/partitions should be set in server.properties

[ https://issues.apache.org/jira/browse/KAFKA-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin M updated KAFKA-6006: Description: The replication factor should be set globally in server.properties such that it can be

[jira] [Commented] (KAFKA-6000) streams 0.10.2.1 - kafka 0.11.0.1 state restore not working

[ https://issues.apache.org/jira/browse/KAFKA-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189947#comment-16189947 ] Ted Yu commented on KAFKA-6000: --- I wonder if the following had something to do with the problem: {code}

[jira] [Commented] (KAFKA-6003) Replication Fetcher thread for a partition with no data fails to start

[ https://issues.apache.org/jira/browse/KAFKA-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189937#comment-16189937 ] Apurva Mehta commented on KAFKA-6003: - Unfortunately your summary is correct :( We have tests which

[jira] [Commented] (KAFKA-4201) Add an --assignment-strategy option to new-consumer-based Mirror Maker

[ https://issues.apache.org/jira/browse/KAFKA-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189903#comment-16189903 ] Vahid Hashemian commented on KAFKA-4201: [~ijuma] It wasn't brought up during an earlier

[jira] [Commented] (KAFKA-6005) Reject JoinGroup request from first member with empty protocol type/protocol list

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

[jira] [Resolved] (KAFKA-6005) Reject JoinGroup request from first member with empty protocol type/protocol list

[ https://issues.apache.org/jira/browse/KAFKA-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6005. Resolution: Fixed Issue resolved by pull request 3957

[jira] [Updated] (KAFKA-6006) Default replication factor for all topics should be set in server.properties

[ https://issues.apache.org/jira/browse/KAFKA-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin M updated KAFKA-6006: Summary: Default replication factor for all topics should be set in server.properties (was: Default

[jira] [Updated] (KAFKA-6006) Default replication factor for all topics/partitions should be set in server.properties

[ https://issues.apache.org/jira/browse/KAFKA-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin M updated KAFKA-6006: Summary: Default replication factor for all topics/partitions should be set in server.properties (was:

[jira] [Updated] (KAFKA-6006) Default replication factor for all topics/partitions should be set in server.properties

[ https://issues.apache.org/jira/browse/KAFKA-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin M updated KAFKA-6006: Description: The replication factor should be set globally in server.properties such that it can be

[jira] [Updated] (KAFKA-6006) Default replication factor should be set in server.properties for all topics

[ https://issues.apache.org/jira/browse/KAFKA-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin M updated KAFKA-6006: Summary: Default replication factor should be set in server.properties for all topics (was: Default

[jira] [Updated] (KAFKA-6000) streams 0.10.2.1 - kafka 0.11.0.1 state restore not working

[ https://issues.apache.org/jira/browse/KAFKA-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart Vercammen updated KAFKA-6000: -- Attachment: failed-restore.log correct-restore.log I added 2 log-files : -

[jira] [Updated] (KAFKA-6006) Default replication factor should be set in server.properties

[ https://issues.apache.org/jira/browse/KAFKA-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin M updated KAFKA-6006: Description: The replication factor should be set globally in server.properties such that it can be

[jira] [Created] (KAFKA-6006) Default replication factor should be set in server.properties

Martin M created KAFKA-6006: --- Summary: Default replication factor should be set in server.properties Key: KAFKA-6006 URL: https://issues.apache.org/jira/browse/KAFKA-6006 Project: Kafka Issue

[jira] [Comment Edited] (KAFKA-6003) Replication Fetcher thread for a partition with no data fails to start

[ https://issues.apache.org/jira/browse/KAFKA-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189731#comment-16189731 ] Stanislav Chizhov edited comment on KAFKA-6003 at 10/3/17 1:53 PM: --- So

[jira] [Comment Edited] (KAFKA-6003) Replication Fetcher thread for a partition with no data fails to start

[ https://issues.apache.org/jira/browse/KAFKA-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189731#comment-16189731 ] Stanislav Chizhov edited comment on KAFKA-6003 at 10/3/17 1:53 PM: --- So

[jira] [Updated] (KAFKA-4879) KafkaConsumer.position may hang forever when deleting a topic

[ https://issues.apache.org/jira/browse/KAFKA-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4879: --- Fix Version/s: (was: 1.0.0) 1.1.0 > KafkaConsumer.position may hang forever

[jira] [Commented] (KAFKA-4879) KafkaConsumer.position may hang forever when deleting a topic

[ https://issues.apache.org/jira/browse/KAFKA-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189600#comment-16189600 ] Ismael Juma commented on KAFKA-4879: This needs a KIP, so pushing to the next release. >

[jira] [Updated] (KAFKA-4665) Inconsistent handling of non-existing topics in offset fetch handling

[ https://issues.apache.org/jira/browse/KAFKA-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4665: --- Fix Version/s: (was: 1.0.0) 1.1.0 > Inconsistent handling of non-existing

[jira] [Commented] (KAFKA-4201) Add an --assignment-strategy option to new-consumer-based Mirror Maker

[ https://issues.apache.org/jira/browse/KAFKA-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189599#comment-16189599 ] Ismael Juma commented on KAFKA-4201: Was a KIP done for this? > Add an --assignment-strategy option

[jira] [Commented] (KAFKA-6005) Reject JoinGroup request from first member with empty protocol type/protocol list

[ https://issues.apache.org/jira/browse/KAFKA-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189591#comment-16189591 ] Ismael Juma commented on KAFKA-6005: [~hachikuji], is this something that we need to do for 1.0.0 or

[jira] [Commented] (KAFKA-4972) Kafka 0.10.0 Found a corrupted index file during Kafka broker startup

[ https://issues.apache.org/jira/browse/KAFKA-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189588#comment-16189588 ] Ismael Juma commented on KAFKA-4972: I am not sure if it's the root cause, but it's a good observation

[jira] [Comment Edited] (KAFKA-4740) Using new consumer API with a Deserializer that throws SerializationException can lead to infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189567#comment-16189567 ] Chang Liu edited comment on KAFKA-4740 at 10/3/17 11:27 AM: I am wondering

[jira] [Commented] (KAFKA-4740) Using new consumer API with a Deserializer that throws SerializationException can lead to infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189567#comment-16189567 ] Chang Liu commented on KAFKA-4740: -- I am wondering what is the current solution? Is following the way

[jira] [Commented] (KAFKA-5843) Mx4jLoader.maybeLoad should only be executed if kafka_mx4jenable is set to true

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

[jira] [Resolved] (KAFKA-4946) Evaluation of kafka_mx4jenable is inverted

[ https://issues.apache.org/jira/browse/KAFKA-4946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4946. Resolution: Duplicate Marking as duplicate of KAFKA-5843 as that had a PR. Credited Ralph as well

[jira] [Commented] (KAFKA-6005) Reject JoinGroup request from first member with empty protocol type/protocol list

[ https://issues.apache.org/jira/browse/KAFKA-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189475#comment-16189475 ] Manikumar commented on KAFKA-6005: -- PR: https://github.com/apache/kafka/pull/3957 > Reject JoinGroup

[jira] [Created] (KAFKA-6005) Reject JoinGroup request from first member with empty protocol type/protocol list

Manikumar created KAFKA-6005: Summary: Reject JoinGroup request from first member with empty protocol type/protocol list Key: KAFKA-6005 URL: https://issues.apache.org/jira/browse/KAFKA-6005 Project: