Skip to Content.
Sympa Menu

per-entity - Re: [Per-Entity] distribution of aggregate metadata

Subject: Per-Entity Metadata Working Group

List archive

Re: [Per-Entity] distribution of aggregate metadata


Chronological Thread 
  • From: Tom Scavo <>
  • To: IJ Kim <>
  • Cc: "Cantor, Scott" <>, Nick Roy <>, Chris Phillips <>, Per-Entity Metadata Working Group <>
  • Subject: Re: [Per-Entity] distribution of aggregate metadata
  • Date: Fri, 12 Aug 2016 17:59:03 -0400
  • Ironport-phdr: 9a23:VQB/ThSdrF59hZv9BfTkem0Rcdpsv+yvbD5Q0YIujvd0So/mwa67bBON2/xhgRfzUJnB7Loc0qyN7PCmBDdLuMvJmUtBWaIPfidNsd8RkQ0kDZzNImzAB9muURYHGt9fXkRu5XCxPBsdMs//Y1rPvi/6tmZKSV3XfDB4LeXtG4PUk9//l6Xro8WSME10g2+cQ/tRLRD++QTTnsgQnYZ4LKstkF3ErmYeKMpMwmY9GVWW1y3379m3tMp/6T9bsuwm389GTajgeakkF/pVAClwYDN939HiqRSWFVjH3XAbSGhD10MQWwU=

On Fri, Aug 12, 2016 at 12:02 PM, IJ Kim
<>
wrote:
>
> It occurs to me that running multiple mdq metadata providers wouldn't be
> too hard while I'm not sure if clients can chain them or can consume a
> second mdq provider with something like "backingMDQUrl". Achieving five
> 9s among these providers would be much feasible.

This is a great idea. Ops might run a single, primary HA MDQ server on
the CDN of choice and then look to the community to add one or more
backup servers to the pool. Deployers could rely on the primary alone
or configure a chain of primary and secondary servers, where the
secondary is chosen from one of the servers in the pool.

Tom



Archive powered by MHonArc 2.6.19.

Top of Page