Yeah. This should be a client side feature. I think discussing scenarios where retry is useful to clients and bubbling up proper errors would be the correct solution to this problem. A good example would be locks, currently clients have no clean way of detecting locks and retrying appropriately.
On Mon, Sep 19, 2016 at 1:25 PM, Stephen Mallette <[email protected]> wrote: > A long while back I created this issue to support a way for Gremlin Server > to retry failed transactions automatically. Aside from the difficulties > discussed with Dylan in the issue itself, I'm realizing now that the > complexity is more that Gremlin Server should probably bear. > > Barring objection I will assume lazy consensus after 72 hours (Thursday, > September 22, 2016, 7am EST) and simply close this one: > > https://issues.apache.org/jira/browse/TINKERPOP-739 >
