[jira] [Updated] (KAFKA-12768) Mirrormaker2 consumer config not using newly assigned client id
[ https://issues.apache.org/jira/browse/KAFKA-12768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent updated KAFKA-12768: Attachment: (was: mirroramker2.properties) > Mirrormaker2 consumer config not using newly assigned client id > --- > > Key: KAFKA-12768 > URL: https://issues.apache.org/jira/browse/KAFKA-12768 > Project: Kafka > Issue Type: Bug > Components: mirrormaker >Affects Versions: 2.6.0 >Reporter: Vincent >Priority: Major > > Component: MirrorMaker2 from the 2.6.0 distribution. > We tried to set quotas based client.id in mirrormaker2. We tried the setting > source.consumer.client.id and source.client.id properties with no luck. > I was able to update the consumer client id using the > US->EUROPE.consumer.client.id config (from the customer) with a single > instance of MM2. With a single instance, everything works fine without any > issue. However, we are running 2 instances of MirrorMaker 2 with tasks.max > set to 2 and it doesn't work with multiple MM2 processes. We also tried > stopping all mirromaker2 instances and starting them again but it didn't help. > Currently, the only workaround is to recreate (or rename) the Connect > internal topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-12768) Mirrormaker2 consumer config not using newly assigned client id
[ https://issues.apache.org/jira/browse/KAFKA-12768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent updated KAFKA-12768: Attachment: (was: mirrormaker.log) > Mirrormaker2 consumer config not using newly assigned client id > --- > > Key: KAFKA-12768 > URL: https://issues.apache.org/jira/browse/KAFKA-12768 > Project: Kafka > Issue Type: Bug > Components: mirrormaker >Affects Versions: 2.6.0 >Reporter: Vincent >Priority: Major > > Component: MirrorMaker2 from the 2.6.0 distribution. > We tried to set quotas based client.id in mirrormaker2. We tried the setting > source.consumer.client.id and source.client.id properties with no luck. > I was able to update the consumer client id using the > US->EUROPE.consumer.client.id config (from the customer) with a single > instance of MM2. With a single instance, everything works fine without any > issue. However, we are running 2 instances of MirrorMaker 2 with tasks.max > set to 2 and it doesn't work with multiple MM2 processes. We also tried > stopping all mirromaker2 instances and starting them again but it didn't help. > Currently, the only workaround is to recreate (or rename) the Connect > internal topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-12768) Mirrormaker2 consumer config not using newly assigned client id
[ https://issues.apache.org/jira/browse/KAFKA-12768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent updated KAFKA-12768: Attachment: (was: instance2_log) > Mirrormaker2 consumer config not using newly assigned client id > --- > > Key: KAFKA-12768 > URL: https://issues.apache.org/jira/browse/KAFKA-12768 > Project: Kafka > Issue Type: Bug > Components: mirrormaker >Affects Versions: 2.6.0 >Reporter: Vincent >Priority: Major > > Component: MirrorMaker2 from the 2.6.0 distribution. > We tried to set quotas based client.id in mirrormaker2. We tried the setting > source.consumer.client.id and source.client.id properties with no luck. > I was able to update the consumer client id using the > US->EUROPE.consumer.client.id config (from the customer) with a single > instance of MM2. With a single instance, everything works fine without any > issue. However, we are running 2 instances of MirrorMaker 2 with tasks.max > set to 2 and it doesn't work with multiple MM2 processes. We also tried > stopping all mirromaker2 instances and starting them again but it didn't help. > Currently, the only workaround is to recreate (or rename) the Connect > internal topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-12768) Mirrormaker2 consumer config not using newly assigned client id
[ https://issues.apache.org/jira/browse/KAFKA-12768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent updated KAFKA-12768: Attachment: (was: instance1_log) > Mirrormaker2 consumer config not using newly assigned client id > --- > > Key: KAFKA-12768 > URL: https://issues.apache.org/jira/browse/KAFKA-12768 > Project: Kafka > Issue Type: Bug > Components: mirrormaker >Affects Versions: 2.6.0 >Reporter: Vincent >Priority: Major > > Component: MirrorMaker2 from the 2.6.0 distribution. > We tried to set quotas based client.id in mirrormaker2. We tried the setting > source.consumer.client.id and source.client.id properties with no luck. > I was able to update the consumer client id using the > US->EUROPE.consumer.client.id config (from the customer) with a single > instance of MM2. With a single instance, everything works fine without any > issue. However, we are running 2 instances of MirrorMaker 2 with tasks.max > set to 2 and it doesn't work with multiple MM2 processes. We also tried > stopping all mirromaker2 instances and starting them again but it didn't help. > Currently, the only workaround is to recreate (or rename) the Connect > internal topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-12768) Mirrormaker2 consumer config not using newly assigned client id
[ https://issues.apache.org/jira/browse/KAFKA-12768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent updated KAFKA-12768: Description: Component: MirrorMaker2 from the 2.6.0 distribution. We tried to set quotas based client.id in mirrormaker2. We tried the setting source.consumer.client.id and source.client.id properties with no luck. I was able to update the consumer client id using the US->EUROPE.consumer.client.id config (from the customer) with a single instance of MM2. With a single instance, everything works fine without any issue. However, we are running 2 instances of MirrorMaker 2 with tasks.max set to 2 and it doesn't work with multiple MM2 processes. We also tried stopping all mirromaker2 instances and starting them again but it didn't help. Currently, the only workaround is to recreate (or rename) the Connect internal topics. was: Component: MirrorMaker2 from the 2.6.0 distribution. The customer tried to set quotas based client.id in mirrormaker2. He tried the setting source.consumer.client.id and source.client.id properties with no luck. I was able to update the consumer client id using the US->EUROPE.consumer.client.id config (from the customer) with a single instance of MM2. The customer also indicated that, with a single instance, everything works fine without any issue. However, we are running 2 instances of MirrorMaker 2 with tasks.max set to 2. He also tried stopping all mirromaker2 instances and starting them again but it didn't help. Currently, the only workaround is to recreate (or rename) the Connect internal topics. > Mirrormaker2 consumer config not using newly assigned client id > --- > > Key: KAFKA-12768 > URL: https://issues.apache.org/jira/browse/KAFKA-12768 > Project: Kafka > Issue Type: Bug > Components: mirrormaker >Affects Versions: 2.6.0 >Reporter: Vincent >Priority: Major > Attachments: instance1_log, instance2_log, mirroramker2.properties, > mirrormaker.log > > > Component: MirrorMaker2 from the 2.6.0 distribution. > We tried to set quotas based client.id in mirrormaker2. We tried the setting > source.consumer.client.id and source.client.id properties with no luck. > I was able to update the consumer client id using the > US->EUROPE.consumer.client.id config (from the customer) with a single > instance of MM2. With a single instance, everything works fine without any > issue. However, we are running 2 instances of MirrorMaker 2 with tasks.max > set to 2 and it doesn't work with multiple MM2 processes. We also tried > stopping all mirromaker2 instances and starting them again but it didn't help. > Currently, the only workaround is to recreate (or rename) the Connect > internal topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
