-
Notifications
You must be signed in to change notification settings - Fork 537
Description
Hi all!
I've got this issue when running my Phoenix/Absinthe app in a libcluster-based cluster, changing the GraphQL schema on deployment leads to a BadFunctionError on nodes still running the old schema. The cluster continues to serve queries against the new schema, causing undefined-function crashes on outdated nodes.
The log is ** (BadFunctionError) function #Function<7.51577645/1 in AtlasWeb.Schema> is invalid, likely because it points to an old version of the code
I'm not sure if this is actually an Abisnthe issue or a clustering issue since the clustering isn't homogeneous at the moment and we use the default libcluster behaviour.
But all the logs I have observed are tied to Schema changes so posting this here in case some had a similar issue and had a fix for it.
I'm not sure what the expected behaviour would be here if the clusters are not homogeneous, but I would've imagined it's possible to refuse to route queries to outdates nodes 🤔