AW: Timeout when requesting status page while metadata refresh

[Bergmann, Clemens]

Hi Scott,

thanks for the fast reply. I will look into the metrics endpoints. Do you have any suggestion on what metric might be appropriate for LB inclusion? 

Viele Grüße
Clemens (Bergmann)
-- 
Clemens Bergmann
Gruppe Nutzermanagement und Entwicklung
Technische Universität Darmstadt
Hochschulrechenzentrum, Alexanderstraße 2, 64289 Darmstadt
Tel. +49 6151 16 71184
http://www.hrz.tu-darmstadt.de/


> -----Ursprüngliche Nachricht-----
> Von: users <users-bounces at shibboleth.net> Im Auftrag von Cantor, Scott
> Gesendet: Donnerstag, 2. September 2021 14:25
> An: Shib Users <users at shibboleth.net>
> Betreff: Re: Timeout when requesting status page while metadata refresh
> 
> 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
> 
> 
> --
> For Consortium Member technical support, see
> https://shibboleth.atlassian.net/wiki/x/ZYEpPw
> To unsubscribe from this list send an email to users-
> unsubscribe at shibboleth.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6377 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/users/attachments/20210902/0a72d028/attachment.p7s>