we have this error from time to time when querying dgraph cluster on AWS. if we retry query, then next query runs ok.
logs are clean both on zero and server instances.
is it normal practice to use retries when querying dgraph? cause for now we don’t have any clue why we get this error, and retry is the only one solution we know. there is no network issues in aws as well…