[IGNITE-9121] Revisit future.get() usages when process message from Communication SPI

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.5, 2.6
• Component/s: cache
• Ignite Flags: Docs Required
• Assignee: Unassigned
• Reporter: Pavel Kovalenko
• Created: 30/Jul/18 11:49
• Updated: 30/Jul/18 11:52

Description

Currently, we use explicit synchronous future.get() at some places when process messages from Communication SPI. This potentially may lead to deadlocks or 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.