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

Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2015/06/02 15:08:17 UTC

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

Vladimir Ozerov created IGNITE-979:
--------------------------------------

             Summary: 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: sprint-6


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)