[jira] [Updated] (KAFKA-4321) Make client.id available to MetricReporter and (De)Serializers in clients
[ https://issues.apache.org/jira/browse/KAFKA-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Arrawatia updated KAFKA-4321: --- Description: Currently, only the interceptors get the default client.id (which is generated if client.id is not set by the users) in configure(...) method. It is useful to pass the default client.id for the MetricReporters and (De)Serializers too. (was: Currently, only the interceptors get the client.id in configure(...) method. It is useful to pass the client.id for the MetricReporters and (De)Serializers too.) > Make client.id available to MetricReporter and (De)Serializers in clients > - > > Key: KAFKA-4321 > URL: https://issues.apache.org/jira/browse/KAFKA-4321 > Project: Kafka > Issue Type: Improvement > Components: clients >Reporter: Sumit Arrawatia >Assignee: Sumit Arrawatia >Priority: Minor > > Currently, only the interceptors get the default client.id (which is > generated if client.id is not set by the users) in configure(...) method. It > is useful to pass the default client.id for the MetricReporters and > (De)Serializers too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KAFKA-4321) Make client.id available to MetricReporter and (De)Serializers in clients
Sumit Arrawatia created KAFKA-4321: -- Summary: Make client.id available to MetricReporter and (De)Serializers in clients Key: KAFKA-4321 URL: https://issues.apache.org/jira/browse/KAFKA-4321 Project: Kafka Issue Type: Improvement Components: clients Reporter: Sumit Arrawatia Assignee: Sumit Arrawatia Priority: Minor Currently, only the interceptors get the client.id in configure(...) method. It is useful to pass the client.id for the MetricReporters and (De)Serializers too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-4151) Update public docs for KIP-78
[ https://issues.apache.org/jira/browse/KAFKA-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Arrawatia updated KAFKA-4151: --- Description: Add documentation to include details on Cluster Id in "Implementation" section. The actual implementation is tracked in KAFKA-4093. (was: System tests for KIP-78. The actual implementation is tracked in KAFKA-4093. ) > Update public docs for KIP-78 > - > > Key: KAFKA-4151 > URL: https://issues.apache.org/jira/browse/KAFKA-4151 > Project: Kafka > Issue Type: New Feature >Reporter: Sumit Arrawatia >Assignee: Sumit Arrawatia > > Add documentation to include details on Cluster Id in "Implementation" > section. The actual implementation is tracked in KAFKA-4093. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-4151) Update public docs for KIP-78
[ https://issues.apache.org/jira/browse/KAFKA-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Arrawatia updated KAFKA-4151: --- Summary: Update public docs for KIP-78 (was: System tests for KIP-78 ) > Update public docs for KIP-78 > - > > Key: KAFKA-4151 > URL: https://issues.apache.org/jira/browse/KAFKA-4151 > Project: Kafka > Issue Type: New Feature >Reporter: Sumit Arrawatia >Assignee: Sumit Arrawatia > > System tests for KIP-78. The actual implementation is tracked in KAFKA-4093. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-4151) System tests for KIP-78
[ https://issues.apache.org/jira/browse/KAFKA-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Arrawatia updated KAFKA-4151: --- Issue Type: New Feature (was: Bug) > System tests for KIP-78 > > > Key: KAFKA-4151 > URL: https://issues.apache.org/jira/browse/KAFKA-4151 > Project: Kafka > Issue Type: New Feature >Reporter: Sumit Arrawatia >Assignee: Sumit Arrawatia > > System tests for KIP-78. The actual implementation is tracked in KAFKA-4093. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KAFKA-4151) System tests for KIP-78
Sumit Arrawatia created KAFKA-4151: -- Summary: System tests for KIP-78 Key: KAFKA-4151 URL: https://issues.apache.org/jira/browse/KAFKA-4151 Project: Kafka Issue Type: Bug Reporter: Sumit Arrawatia Assignee: Sumit Arrawatia System tests for KIP-78. The actual implementation is tracked in KAFKA-4093. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-4006) Kafka connect fails sometime with InvalidTopicException in distributed mode
[ https://issues.apache.org/jira/browse/KAFKA-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Arrawatia updated KAFKA-4006: --- Description: I get trying to spin up a 3 node distributed connect cluster. Sometimes one of the worker fails to boot with the following error when auto topic creation is enabled : org.apache.kafka.common.errors.InvalidTopicException: Topic 'default.config' is invalid default.config is the topic name for Connect config. Also, starting the worker again fixes the issue. was: I get trying to spin up a 3 node distributed connect cluster. Sometimes one of the worker fails to boot with the following error when auto topic creation is enabled : `org.apache.kafka.common.errors.InvalidTopicException: Topic 'default.config' is invalid` error . `default.config` is the topic name for Connect config. Also, starting the worker again fixes the issue. > Kafka connect fails sometime with InvalidTopicException in distributed mode > --- > > Key: KAFKA-4006 > URL: https://issues.apache.org/jira/browse/KAFKA-4006 > Project: Kafka > Issue Type: Bug > Components: KafkaConnect >Affects Versions: 0.10.0.0 >Reporter: Sumit Arrawatia >Assignee: Ewen Cheslack-Postava > > I get trying to spin up a 3 node distributed connect cluster. > Sometimes one of the worker fails to boot with the following error when auto > topic creation is enabled : > org.apache.kafka.common.errors.InvalidTopicException: Topic 'default.config' > is invalid > default.config is the topic name for Connect config. > Also, starting the worker again fixes the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KAFKA-4006) Kafka connect fails sometime with InvalidTopicException in distributed mode
Sumit Arrawatia created KAFKA-4006: -- Summary: Kafka connect fails sometime with InvalidTopicException in distributed mode Key: KAFKA-4006 URL: https://issues.apache.org/jira/browse/KAFKA-4006 Project: Kafka Issue Type: Bug Components: KafkaConnect Affects Versions: 0.10.0.0 Reporter: Sumit Arrawatia Assignee: Ewen Cheslack-Postava I get trying to spin up a 3 node distributed connect cluster. Sometimes one of the worker fails to boot with the following error when auto topic creation is enabled : `org.apache.kafka.common.errors.InvalidTopicException: Topic 'default.config' is invalid` error . `default.config` is the topic name for Connect config. Also, starting the worker again fixes the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
