If an Ignite operation hangs due to some reason due to an internal problem or buggy application code it needs to eventual fail after a timeout fires.
An application must not freeze waiting for a human being intervention if an atomic update fails internally.
Even more, I would let all possible operation to fail after a timeout fires:
- Ignite compute computations (covered by
- Ignite services calls.
- Atomic cache updates (see devlist discussion - http://apache-ignite-developers.2346864.n4.nabble.com/Timeouts-in-atomic-cache-td19839.html).
- Transactional cache updates (covered by IGNITE-6894 and IGNITE-6895).
- SQL queries.