> On 8 May 2015, at 01:52, Gour Saha <[email protected]> wrote: > > Last but not least, I'm wondering if there would already be a plan to > expose somehow (through an internal or an external service) the registry > through DNS (that's what we really use for service location for HTTPFS & > OpenTSDB). A bash polling script would certainly be sufficient for our > needs for now, but longer-term, we'd need to have a more robust solution. > > Registry and REST APIs on registry comes directly from YARN - > https://issues.apache.org/jira/browse/YARN-913 > https://issues.apache.org/jira/browse/YARN-2948 > http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/registry/yarn-registry.html
DNS support is always something that's been considered; it's why the paths in the registry spec are required to be valid DNS names (though the check is actually disabled primarily because usernames aren't and punycoding doesn't address things like spaces in names, just high-unicode characters. We held back on this originally due to (a) need to scope things for hadoop 2.6 and (b) worries about how operations teams will like more DNS servers popping up in the organisation. I think we can try to do the DNS -it just needs someone to sit down and to it. I'm afraid my todo list is already full I'd like to wrap up the registry stuff with an HTTP service that can be deployable at a fixed location; we have this in slider but it's there to show its possible more than anything else (because it moves around).
