You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2019/09/24 11:47:00 UTC
[jira] [Updated] (IGNITE-6980) Automatic cancelling of hanging
Ignite operations
[ https://issues.apache.org/jira/browse/IGNITE-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Plekhanov updated IGNITE-6980:
--------------------------------------
Fix Version/s: (was: 2.8)
> Automatic cancelling of hanging Ignite operations
> -------------------------------------------------
>
> Key: IGNITE-6980
> URL: https://issues.apache.org/jira/browse/IGNITE-6980
> Project: Ignite
> Issue Type: New Feature
> Reporter: Denis Magda
> Priority: Blocker
> Labels: iep-7, important
>
> 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-6940).
> - 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)