You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Manikumar Reddy (JIRA)" <ji...@apache.org> on 2016/05/21 03:58:12 UTC

[jira] [Updated] (KAFKA-2547) Make DynamicConfigManager to use the ZkNodeChangeNotificationListener introduced as part of KAFKA-2211

     [ https://issues.apache.org/jira/browse/KAFKA-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manikumar Reddy updated KAFKA-2547:
-----------------------------------
    Status: Reopened  (was: Closed)

> Make DynamicConfigManager to use the ZkNodeChangeNotificationListener introduced as part of KAFKA-2211
> ------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-2547
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2547
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Parth Brahmbhatt
>            Assignee: Parth Brahmbhatt
>             Fix For: 0.10.1.0, 0.10.0.0
>
>
> As part of KAFKA-2211 (https://github.com/apache/kafka/pull/195/files) we introduced a reusable ZkNodeChangeNotificationListener to ensure node changes can be processed in a loss less way. This was pretty much the same code in DynamicConfigManager with little bit of refactoring so it can be reused. We now need to make DynamicConfigManager itself to use this new class once KAFKA-2211 is committed to avoid code duplication.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)