Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-dev@hadoop.apache.org
Date: Thu, 19 Mar 2015 02:56:38 +0000 (UTC)
From: "Gopal V (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12783105.1426733789000.139300.1426733798774@Atlassian.JIRA>
In-Reply-To: <JIRA.12783105.1426733789000@Atlassian.JIRA>
References: <JIRA.12783105.1426733789000@Atlassian.JIRA>
 <JIRA.12783105.1426733789008@arcas>
Subject: [jira] [Created] (YARN-3373) TTL & identity aware read cache for
 the SRV records
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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)