ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Setrakyan (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-6980) Automatic cancelling of hanging Ignite operations
Date Sun, 01 Apr 2018 14:57:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmitriy Setrakyan reassigned IGNITE-6980:
-----------------------------------------

    Assignee: Aleksey Plekhanov  (was: Dmitriy Setrakyan)

> 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
>            Assignee: Aleksey Plekhanov
>            Priority: Blocker
>              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.
> 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
(v7.6.3#76005)

Mime
View raw message