Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
Slider 0.30
-
None
-
None
-
slider may 1, slider may 2, slider June 1, slider June 2, Slider July #1, Slider August #1
Description
The slider, curator &c registries all support registration of some form of (protocol, host, port) tuples.
For some services, it is the ZK binding data that is more relevant to clients.
We should standardise a way for services to register these values as (protocol, quorum, path) in a bindings section. The binding itself will be app-specific, but you could bootstrap things like an hbase or accumulo client from this data. Management and monitoring tooling could validate the validity of the ZK quorum (all hostnames resolve, 1+ host live, ...)