- ๐ฆ๐บAustralia almunnings Melbourne, ๐ฆ๐บ
Side note: I still feel like it a bandaid on the symptom, and it's still going to be getting that deprecated in getCacheId, all we're doing is separating the caches by adding in the getCacheId again.
- @almunnings opened merge request.
- ๐ฆ๐บAustralia almunnings Melbourne, ๐ฆ๐บ
I'm unsure, quick check and maybe this was missed, and it fixes the issue?
$cid = $this->getCacheId('schema');
forweb/modules/contrib/graphql/src/Plugin/GraphQL/Schema/AlterableComposableSchema.php
- ๐ฆ๐บAustralia almunnings Melbourne, ๐ฆ๐บ
Looks like the changes in ๐ Cache collision when multiple servers are using the same schema plugin Active are breaking.
web/modules/contrib/graphql/src/Plugin/GraphQL/Schema/SdlSchemaPluginBase.php
Method:
getCacheId
$this->getConfiguration()['server_id']
is not always set. It's weirdly only sometimes set?It looks like its set in the server and not the schema?
Full ID returned:
full:graphql_compose:my_server
- /admin/config/graphql/servers/manage/core_graphql/explorer
- /admin/config/graphql/servers/manage/core_graphql/voyagerPartial ID returned:
full:graphql_compose
- /admin/config/graphql/servers/manage/core_graphql/validateSomethings not right or I'm missing something here.
Is it an order or operation or missing data? - ๐จ๐ทCosta Rica esteban.arias
Heya everyone,
If you are using graphql while also using memcache as your default cache backend, please introduce these lines to your settings:
$settings['cache']['bins']['graphql_ast'] = 'cache.backend.database';
$settings['cache']['bins']['graphql_results'] = 'cache.backend.database';This should let graphql use the database tables for caching purposes which seems to make the random issues go away.
I didn't find this fix by myself but got permission to share it to the community.
Hope this helps!