per-entity - Re: [Per-Entity] remaining BIG questions
Subject: Per-Entity Metadata Working Group
List archive
- From: Tom Scavo <>
- To: "Cantor, Scott" <>
- Cc: Tom Scavo <>, Per-Entity Metadata Working Group <>
- Subject: Re: [Per-Entity] remaining BIG questions
- Date: Wed, 14 Sep 2016 14:27:32 -0400
- Ironport-phdr: 9a23:UnxuVRIPu08Y473w19mcpTZWNBhigK39O0sv0rFitYgXI/rxwZ3uMQTl6Ol3ixeRBMOAtKIC1rGd6v2ocFdDyKjCmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TWapAQfERTnNAdzOv+9WsuL15z2hKiO/MiZSAxOmD2nJftJJxKqsU+Z4sIfh5dlMOBr4hzSvz1Fd/kAlk1yIlfGoxH5rvy79YBku3BMoekq/tBHeaT8Y6kiS7FEVnIrP31jt56jjgXKUQbavihUaW4RiBcdRlGdtBw=
On Wed, Sep 14, 2016 at 1:45 PM, Cantor, Scott
<>
wrote:
> On 9/14/16, 12:20 PM,
> "
> on behalf of Tom Scavo"
> <
> on behalf of
> >
> wrote:
>
>> 5) What is our failover strategy?
>
> Can you explain what you mean specifically?
Yes, I'll try. First, factor out the CDN. It doesn't have anything to
do with what I'm about to say.
The best way to motivate the question is to review our failover
strategy for aggregate distribution (md.incommon.org). There are two
servers behind md.incommon.org: a primary (here in Ann Arbor) and a
hot spare (in Indiana). We manually fail over to the hot spare when
necessary. Clients never notice when we fail over since that is the
nature of aggregate distribution.
For per-entity metadata, it's a totally different story. Fail over
needs to be automatic, and the various servers need to be
strategically located in geographic regions such that latency is
minimized (or at least acceptable).
Does that help?
Tom
- [Per-Entity] remaining BIG questions, Tom Scavo, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Steve Thorpe, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Nick Roy, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Tom Scavo, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Cantor, Scott, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Tom Scavo, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Cantor, Scott, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Tom Scavo, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Cantor, Scott, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Tom Scavo, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Cantor, Scott, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Tom Scavo, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Cantor, Scott, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Tom Scavo, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Cantor, Scott, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Nick Roy, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Nick Roy, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Cantor, Scott, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Nick Roy, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Nick Roy, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Cantor, Scott, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Nick Roy, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Cantor, Scott, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Nick Roy, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Nick Roy, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Cantor, Scott, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Cantor, Scott, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Cantor, Scott, 09/14/2016
- Re: [Per-Entity] remaining BIG questions, Tom Scavo, 09/14/2016
Archive powered by MHonArc 2.6.19.