You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-dev@hadoop.apache.org by "Gopal V (JIRA)" <ji...@apache.org> on 2015/03/19 03:56:38 UTC

[jira] [Created] (YARN-3373) TTL & identity aware read cache for the SRV records

Gopal V created YARN-3373:
-----------------------------

             Summary: TTL & identity aware read cache for the SRV records
                 Key: YARN-3373
                 URL: https://issues.apache.org/jira/browse/YARN-3373
             Project: Hadoop YARN
          Issue Type: Sub-task
          Components: yarn
            Reporter: Gopal V


The freshness/staleness checks of the SRV record should be an abstracted implementation detail of the service registry.

This implies that every client is asked to listServiceRecords each time they require a list of the records, which would be incredibly expensive if it involved network round-trips during normal tight-loop operations.

The combination of unique binding records and the TTL provides the equivalent of the DNS (fixed CNAME -> unique A) roll-over mechanisms used to cache-bust effectively on the client-side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)