Major Description
Currently the GremlinExecutor tries to timeout a eval after the job has started execution in the thread pool, when the likely user expectation is that it begin the timeout testing from the time the eval was invoked. While the current approach works (though not in line with what users probably are thinking is happening), an overloaded server using GremlinExecutor will have a more difficult time clearing the queue of jobs (if it can clear it at all).
Attachments
Issue Links
- links to
