HBase indexer ZK configurations are not being cleaned up or updated after the initial setting

It appears that old configurations are still persisting in ZK when it comes to adding new indexers. I discovered this after creating this bad setting in hbase-indexer-site.xml:

<property>
   <name>hbase.zookeeper.quorum</name>
   <value>search-testing-3rdparty-1.ent.cloudera.com:2181</value>
</property> 

(the port number should not be specified)

and then running hbase add-indexer -n hbaseIndexer ... which still resulted in a successfully created and active indexer called "hbaseIndexer" that wouldn't properly index data.

Deleting the indexer using hbase-indexer delete-indexer -n hbaseIndexer and restarting the indexer service with the proper hbase-indexer-site settings doesn't fix it; if you try to create the "hbaseIndexer" indexer again, it'll still use those old bad zookeeper quorum settings and generate a broken indexer.

The workaround I used was to delete the entire /ngdata tree from ZooKeeper and begin fresh with all the proper configurations.