[YARN-3373] TTL & identity aware read cache for the SRV records

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: yarn
• Assignee: Unassigned
• Reporter: Gopal Vijayaraghavan
• Created: 19/Mar/15 02:56
• Updated: 19/Mar/15 02:56

Description

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.