With the new distributed configuration management feature of OODT, users now get the chance deploy large number of instances of OODT components without having to worry about manually configuring all those instances. This new feature allows any OODT component to retrieve configuration required from zookeeper on the fly.

toc 

Example Scenario

For example, lets consider the file manager component. Suppose that we want to deploy 20 file manager instances in a cluster. Configuring them one by one would be a tiresome task with the user repeating the same set of tasks 20 times, copying properties files, XML files and such other files related to configuration of that file manager instance. If we had to configure a file manager instance manually, 

...

Now we have published our configuration to zookeeper successfully.

Using Distributed Configuration Management

Once the configuration is published to zookeeper, we can deploy our OODT components to corresponding servers in the cluster. At this point, if we want to use the distributed configuration management in those instances, we have to follow the following steps.

1. First, we should enable distributed configuration management by setting the org.apache.oodt.config.distributed system property to true.

2. Then,  we must either specify the zookeeper connect string as the org.apache.oodt.config.zk.connectString system property or specify the properties file (file location as org.apache.oodt.config.zkProperties) in which we have set the aforementioned property for zookeeper connect string.

3. When the above two steps are completed, we can run any OODT component with the support of distributed configuration management.

Example with file manager. We need to add the following two properties to filemgr executable.

-Dorg.apache.oodt.config.zk.connectString=<zookeeper-connect-string> \
-Dorg.apache.oodt.config.distributed=true \