If the Dgraph standard out log contains connection broken messages, although it may look like the problem occurred with the Dgraph, the actual cause of the problem is usually a broken connection between the server that hosts the front-end application and the server that hosts the Dgraph.
WARN [DATE TIME] UTC (1239830549803) DGRAPH {dgraph}: Aborting request: connection broken: client 10.10.21.21
1239830549803 10.6.35.35 - 349 0 19.35 0.00 0 - 0 0 - -
Typically, the connection broken message means that the Dgraph encountered an unexpected failure in the connection between the client and the Dgraph. This type of error may occur outside the Dgraph, such as in the network, or be caused by the timeout of the client application session.
Investigate the connection between the client and the Dgraph. For example, to prevent timeouts of the client application sessions, you may decide to implement front-end application retries.