For my demo project I need to update the same nodes often, possibly multiple times per second and I am getting a lot of “Transaction has been aborted. Please retry” errors (I use dgo) even when few/single transactions are running concurrently and all transactions only contain a single mutation, with commitNow enabled.
Am I correct in assuming this is because multiple transactions for the same nodes are detected and dgraph automatically aborts some of these transactions?
My transaction only consist of a single mutation and the response I give to users is based on the data returned by the query in the mutation. Is there a way to ensure these mutations get executed, I do not care about the exact order they are executed in; just that they get executed without having to retry many times.
Furthermore, it appears that a small amount of transactions succeed without actually updating the data. I’m still trying to confirm this behavior though, since it could well be a case of pebkac.