GraphQl Config (SchemaStiching) does not use LockGuardedCacheLoader (Expensive and large config) #39494
Labels
Issue: ready for confirmation
Reported on 2.4.8-beta1
Indicates original Magento version for the Issue report.
Triage: Dev.Experience
Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Preconditions and environment
Code on 2.4.8-beta1 shows no use of LockGuardedCacheLoader for GraphQl Config Data.
See GraphQl di.xml
For uses see:
This can lead to a 'stampede' type issue for the expensive schema stitching process. By using the LockGuardedCacheLoader, we can prevent this issue when the cache is flushed.
Other notes:
Steps to reproduce
Expected result
GraphQl schema stitching is only loaded once. (Or F times where F is some small fraction of N; this would mitigate against one process failing).
Actual result
GraphQl schema stitching is run once per request.
Additional information
You can see this effect by monitoring Redis
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: