Details
Major Description
In short, the setup: group, that contains two members, one proxy and one hosted. The requested metadata is contained in a proxy (but is also deployed on same path in hosted repeatedly). This setup group should never return 404, as the requested metadata does exists, even under load.
Current code does not uses the fact that merged metadata content is reusable, and does an unneeded roundtrip to Storage that introduces concurrency issues with group cache.