SP metadata cache keeps growing

Cantor, Scott cantor.2 at osu.edu
Thu Feb 27 14:48:57 EST 2020

On 2/27/20, 2:45 PM, "users on behalf of Peter Schober" <users-bounces at shibboleth.net on behalf of peter.schober at univie.ac.at> wrote:

> Obviously that would need some testing and it's unclear to me what a
> good value would be. (30m just turned out not to be sufficient on a
> test system with 2GB RAM and 2 cores, for loading out edugain-enabled
> local feed.)

I have not seen anything resembling that bad a result, so that means something's probably really wrong. Maybe the signature step is that bad now, but I didn't think so. I know the parsing isn't.

> I'd be tempted to go with TimeoutStartSec=infinity, deactivating this
> protection completely, but then loading huge metadata files in the
> foreground -- outside of a background thread -- only hurts the very
> first time, AFAIR, and people probably shouldn't be doing that in the
> first place given that MDQ now exists...

If it's the signature, then it's first time mostly. If not, it's every time.

As always, MDQ is fine, until you need discovery. I don't know what to say about that, I guess SeamlessAccess or bust.

-- Scott

More information about the users mailing list