[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)
[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 ] Vladimir Ozerov updated IGNITE-6980: Fix Version/s: (was: 2.7) 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 >Assignee: Aleksey Plekhanov >Priority: Blocker > Labels: iep-7, important > Fix For: 2.8 > > > 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)
[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 ] Dmitriy Pavlov updated IGNITE-6980: --- Fix Version/s: (was: 2.6) 2.7 > 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.7 > > > 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)
[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 ] Andrey Gura updated IGNITE-6980: Fix Version/s: (was: 2.5) 2.6 > 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.6 > > > 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)
[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 ] Denis Magda updated IGNITE-6980: Issue Type: New Feature (was: Bug) > 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)
[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 ] Denis Magda updated IGNITE-6980: Priority: Blocker (was: Critical) > 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 >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)
[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 ] Anton Vinogradov updated IGNITE-6980: - Description: 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. was: 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 cache updates (see devlist discussion). - Transactional cache updates (covered by IGNITE-6894 and IGNITE-6895). - SQL queries. > 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 >Assignee: Aleksey Plekhanov >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. > 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)
[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 ] Anton Vinogradov updated IGNITE-6980: - Description: 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 cache updates (see devlist discussion). - Transactional cache updates (covered by IGNITE-6894 and IGNITE-6895). - SQL queries. was: 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. > 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 >Assignee: Aleksey Plekhanov >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 cache updates (see devlist discussion). > - Transactional cache updates (covered by IGNITE-6894 and IGNITE-6895). > - SQL queries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 ] Anton Vinogradov updated IGNITE-6980: - Description: 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. was: 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. > 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)
[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 ] Vladimir Ozerov updated IGNITE-6980: Fix Version/s: (was: 2.4) 2.5 > 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. > - Ignite services calls. > - Atomic/transactional cache updates. > - SQL queries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 ] 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)
