You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Yakov Zhdanov (JIRA)" <ji...@apache.org> on 2015/08/06 16:43:21 UTC

[jira] [Updated] (IGNITE-979) Revisit timeout logic in Ignite.

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

Yakov Zhdanov updated IGNITE-979:
---------------------------------
    Fix Version/s:     (was: sprint-7)
                   ignite-1.4

> Revisit timeout logic in Ignite.
> --------------------------------
>
>                 Key: IGNITE-979
>                 URL: https://issues.apache.org/jira/browse/IGNITE-979
>             Project: Ignite
>          Issue Type: Task
>          Components: general
>    Affects Versions: sprint-4
>            Reporter: Vladimir Ozerov
>            Priority: Critical
>             Fix For: ignite-1.4
>
>
> Migrated from GG private JIRA (GG-9487).
> "Also think of removing registration of events in timeout processor, but have several threads scanning the corresponding futures collection and cancel operations if necessary.
> List to check:
> - tasks
> - cache ops (atomic and tx modes):
> - get
> - put
> - query
> - lock
> - service deployment
> - continuos queries
> - message listeners deployment
> - ?"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)