Federated gateway - 500 error on whole graph if one underlying graph/service is down

Hi there, I have been trying out federated gateway and I am worried about the entire service going down if one graph is not running. If you have a number of micro graphql services underneath that can cause a lot of problems. I tried turning off / on services while starting up federated gateway. It should really pick up the services more gracefully. For example: the below caused the entire graphql to result in 500 internal error (instead of just reporting an error that one service is down and allowing all the other services to operate as normal. It should rather be an online/offline kind of thing. Error checking for changes to service definitions: Couldn't load service definitions for "testgraphLocal" at http://test-graph:8099/query: request to http://test-graph:8099/query failed, reason: getaddrinfo ENOTFOUND test-graph This data graph is missing a valid configuration. Couldn't load service definitions for "testgraphLocal" at http://test-graph:8099/query: request to http://test-graph:8099/query failed, reason: getaddrinfo ENOTFOUND test-graph

Posted by saul-data on Jul 28, 2020, 9:56 PM

Tags

• reliability (Other)

Related issues

• The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
• I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
• I hate that I'm in deep enough to know what you mean.
• The biggest problem with “AI” is that big corps are shoving it down our throats.
• in the middel of a coding session with 5.6 sol.
• [Hero Run] 535B-A23B on 18T tokens