Per-Entity Metadata Working Group

[Patrick Radtke <>]

On Thu, Oct 13, 2016 at 9:48 AM, Cantor, Scott 
<>
 wrote:
>> We'll face the same challenge for any architecture that use AWS
>> elastic load balancers. ELB dns records have TTL of 60 seconds so that
>> AWS can change them as they see fit, and the whole 'elasticity' part
>> is geared towards clients that use DNS correctly (e.g. not Java).
>
> I'm sure you're probably correct, but if you define "correctly" as 
> auto-retry across all A records, I really don't know much besides browsers 
> that do that. Interested to learn otherwise.

Oh, I just meant honoring the TTL.  Java (in my past experience) has
cached forever (unless you disable it), and always hit the first ip
returned. Googling around, it seems like newer versions of Java only
cache forever if their is a security manager involved.  Firefox had
bug a few years ago
(https://bugzilla.mozilla.org/show_bug.cgi?id=861273) where they were
caching CDN and ELB IPs for too long which resulted in them trying to
load assets from IPs that no longer served the content. Anyhow, I'm
glad you brought this up.

-Patrick