Skip to Content.
Sympa Menu

per-entity - RE: [Per-Entity] A little MDQ mvp in AWS

Subject: Per-Entity Metadata Working Group

List archive

RE: [Per-Entity] A little MDQ mvp in AWS


Chronological Thread 
  • From: "Cantor, Scott" <>
  • To: Patrick Radtke <>
  • Cc: Christopher Hubing <>, "Per-Entity Metadata Working Group" <>
  • Subject: RE: [Per-Entity] A little MDQ mvp in AWS
  • Date: Thu, 13 Oct 2016 16:48:14 +0000
  • Accept-language: en-US
  • Authentication-results: spf=pass (sender IP is 164.107.81.218) smtp.mailfrom=osu.edu; cirrusidentity.com; dkim=none (message not signed) header.d=none;cirrusidentity.com; dmarc=bestguesspass action=none header.from=osu.edu;
  • Ironport-phdr: 9a23:+v8hEB8tMHcOG/9uRHKM819IXTAuvvDOBiVQ1KB90+wcTK2v8tzYMVDF4r011RmSAtWdtqkP0reempujcFJDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBX660e/5j8KGxj5KRE9ZqGsQtaT3IyL0LWK8oHJYg5LzAC0ba9xIV3itQzNrMgdgqNpK7wr1wDIrnZOZ+VK1CVjIlfFzDjm4cLltrVq9ThXobZpzMVHTbmwN/AzRLpECy5gaUgy/9CtuBXeG1jcrkAAW3kbx0IbSzPO6wv3C9Ko6nP3
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99
> 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.

-- Scott


Archive powered by MHonArc 2.6.19.

Top of Page