[jira] [Comment Edited] (IGNITE-6980) Automatic cancelling of hanging Ignite operations

["Anton Vinogradov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328748#comment-16328748 ] 

Anton Vinogradov edited comment on IGNITE-6980 at 1/17/18 1:18 PM:
-------------------------------------------------------------------

Lets create subtasks for each case.


was (Author: avinogradov):
Lets create subrasks for each case.

> 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.5
>
>
> 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 (covered by IGNITE-6940).
>  - Ignite services calls.
>  - Atomic/transactional cache updates.
>  - SQL queries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)