You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/08/04 20:46:14 UTC
[jira] [Resolved] (SLIDER-76) registration data to allow for
listing of ZK bindings
[ https://issues.apache.org/jira/browse/SLIDER-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved SLIDER-76.
----------------------------------
Resolution: Duplicate
covered in YARN-913
> registration data to allow for listing of ZK bindings
> -----------------------------------------------------
>
> Key: SLIDER-76
> URL: https://issues.apache.org/jira/browse/SLIDER-76
> Project: Slider
> Issue Type: Sub-task
> Components: registry
> Affects Versions: Slider 0.30
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> 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, ...)
--
This message was sent by Atlassian JIRA
(v6.2#6252)