ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Kovalenko (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-9121) Revisit future.get() usages when process message from Communication SPI
Date Mon, 30 Jul 2018 11:50:00 GMT
Pavel Kovalenko created IGNITE-9121:
---------------------------------------

             Summary: Revisit future.get() usages when process message from Communication
SPI
                 Key: IGNITE-9121
                 URL: https://issues.apache.org/jira/browse/IGNITE-9121
             Project: Ignite
          Issue Type: Improvement
          Components: cache
    Affects Versions: 2.6, 2.5
            Reporter: Pavel Kovalenko


Currently, we use explicit synchronous future.get() when process messages from Communication
SPI. This potentially may lead to deadlocks to thread-pool exhausting as was showed in IGNITE-9111
e.g.
To fix the problem we should determine all places in the code where we synchronously wait
for some futures and try to either refactor these places or implement a special exception
(which will contain such future) with subsequent retrying a runnable in low-level Communication
SPI processing when future will be completed. 



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

Mime
View raw message