When I send queries in the graphql screen in cloud.dgraph I get
"message": "failed to lazy-load GraphQL schema: : Unexpected meta: 0 for key: 00000000 00 00 00 00 00 00 03 82 a0 00 15 64 67 72 61 70 |...........dgrap|\n00000010 68 2e 67 72 61 70 68 71 6c 2e 73 63 68 65 6d 61 |h.graphql.schema|\n00000020 00 00 00 00 02 7f 25 f5 c7 |......%..|\n"
or it actually gives a result of a query.
If I get one of the other 2 options it is like the query never happened. So far this only seems to happen when I send a query in dgraph cloud but I have not tested a lot with my client yet.
This is quite annoying. Why did this break all of the sudden?
This is happening on the client I am working on aswell. You are having a product outage!
Would probably be best if you open a support ticket in Dgraph Cloud
This issue has been addressed via support.
Yes it has been resolved. What was going on?
There was a single replica in the backend that had some disk corruption for only this specific entry, which turned out to be your GraphQL schema. It went undetected which then reflected in the error messages you were seeing. Replacing the replica fixed the issue. The other replica servers were OK which is why your error message was intermittent (the error message came only from the bad server).
We’ve added additional monitoring to detect this kind of disk issue.