[
https://issues.apache.org/jira/browse/IGNITE-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-6980:
--------------------------------
Labels: iep-7 important (was: iep-7)
> Automatic cancelling of hanging Ignite operations
> -------------------------------------------------
>
> Key: IGNITE-6980
> URL: https://issues.apache.org/jira/browse/IGNITE-6980
> Project: Ignite
> Issue Type: Bug
> Reporter: Denis Magda
> Priority: Critical
> Labels: iep-7, important
> Fix For: 2.4
>
>
> 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.
> Take atomic operations case brought by Val to our attention recently:
> http://apache-ignite-developers.2346864.n4.nabble.com/Timeouts-in-atomic-cache-td19839.html
> 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.
> - Ignite services calls.
> - Atomic/transactional cache updates.
> - SQL queries.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
