IDPv3 seems to fail to reload configuration when under heavy load.

[Peter Schober]

* alex.samuseu <alexander.samuseu at gmail.com> [2019-03-01 22:05]:
> A few cases I'm aware of are seem to be about reloading metadata of
> a new SP - until they restart the service, they get the standard
> "The application you have accessed is not registered for use with
> this service" error page which is shown when metadata for a certain
> SP isn't yet known to IDP.

Even without any specific configuration in individual
MetadataProviders most types should reload by default:

https://wiki.shibboleth.net/confluence/display/IDP30/MetadataConfiguration#MetadataConfiguration-ReloadingAttributesReloadingAttributes

So maybe the metadata provider is of the wrong type (you didn't
provide any specifics) or maybe the loaded metadata itself has a weird
EntitiesDescriptor/@cacheDuration value or indeed this is a bug due to
the high load you mentoned, or yet again something else...

-peter