Timeout when requesting status page while metadata refresh

[Cantor, Scott]

There's no reason we know of that any lock would be held on anything the status page needs to read during a refresh, and any non-dynamic source is loaded when the metadata service itself starts up so it's at IdP startup or under a fill service refresh only. Not during normal operation.

Maybe there's an edge case involving non-failfast sources that can't properly initialize themselves. Could be there's a broader lock involved if there's no "active" metadata loaded for that that resolver. You can file a bug, but I don't think it would be high priority unless something obvious pans out.

Try metrics instead and pull something more focused to check IdP operational status.

-- Scott