[jira] [Updated] (KAFKA-4321) Make client.id available to MetricReporter and (De)Serializers in clients

2016-10-19 Thread Sumit Arrawatia (JIRA)
[ 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

[jira] [Created] (KAFKA-4321) Make client.id available to MetricReporter and (De)Serializers in clients

2016-10-19 Thread Sumit Arrawatia (JIRA)
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

[jira] [Updated] (KAFKA-4151) Update public docs for KIP-78

2016-09-15 Thread Sumit Arrawatia (JIRA)
[ 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&quo

[jira] [Updated] (KAFKA-4151) Update public docs for KIP-78

2016-09-15 Thread Sumit Arrawatia (JIRA)
[ 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 d

[jira] [Updated] (KAFKA-4151) System tests for KIP-78

2016-09-12 Thread Sumit Arrawatia (JIRA)
[ 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

[jira] [Created] (KAFKA-4151) System tests for KIP-78

2016-09-12 Thread Sumit Arrawatia (JIRA)
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

Re: [DISCUSS] KIP-78: Cluster Id

2016-09-04 Thread sumit arrawatia
; tags is actually orthogonal to the usage of cluster.id. I am not sure > > the > > > benefits of using tags that you provided can help us decide whether > > > randomly generated cluster.id is better than readable cluster.id from > > > config. > > > >

Re: [DISCUSS] KIP-78: Cluster Id

2016-09-03 Thread sumit arrawatia
Hi Dong, Please find my comments inline. Hopefully they address your concerns. Have a great weekend ! Sumit On Sat, Sep 3, 2016 at 3:17 PM, Dong Lin wrote: > Hi Sumit, > > Please see my comments inline. > > On Sat, Sep 3, 2016 at 10:33 AM, sumit arrawatia < > sumi

Re: [DISCUSS] KIP-78: Cluster Id

2016-09-03 Thread sumit arrawatia
ation for this approach. We plan to implement the first part (UUID) in a manner that makes it easy to add the second part (human readable names using tags) in a future KIP. Hopefully this helps to clarify your doubts and concerns. > Cheers, > Dong > > > > On Sat, Sep 3, 2016 at 12:46

Re: [DISCUSS] KIP-78: Cluster Id

2016-09-03 Thread sumit arrawatia
izers which implement the ClusterResourceListener interface. Cheers, > -Flavio > > > On 03 Sep 2016, at 08:46, sumit arrawatia > wrote: > > > > Hi Dong, > > > > If you set the cluster.id in the config, the problem is how you > > change/update the clus

Re: [DISCUSS] KIP-78: Cluster Id

2016-09-03 Thread sumit arrawatia
Hi Dong, If you set the cluster.id in the config, the problem is how you change/update the cluster.id . You will need to change the all the config files and make sure every one of them is correct as well as update the ZK metadata. This will require a reboot/downtime of the entire cluster, wherea

[jira] [Updated] (KAFKA-4006) Kafka connect fails sometime with InvalidTopicException in distributed mode

2016-07-29 Thread Sumit Arrawatia (JIRA)
[ 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

[jira] [Created] (KAFKA-4006) Kafka connect fails sometime with InvalidTopicException in distributed mode

2016-07-29 Thread Sumit Arrawatia (JIRA)
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