[
https://issues.apache.org/jira/browse/IGNITE-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264220#comment-15264220
]
Taras Ledkov commented on IGNITE-3073:
--------------------------------------
The test _IgniteCacheStarvationOnRebalanceTest_ is added to
[branch|https://github.com/gridgain/apache-ignite/commit/984645db92f5f43e5ea08f85a6ccfa3cb5473630]
> Possible thread starvation due to rebalancing
> ---------------------------------------------
>
> Key: IGNITE-3073
> URL: https://issues.apache.org/jira/browse/IGNITE-3073
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Valentin Kulichenko
> Assignee: Valentin Kulichenko
> Priority: Critical
> Fix For: 1.6
>
>
> We're currently rebalancing the utility cache in the system pool. This can
> cause starvation, for example in this scenario:
> # Start several nodes and a cache with indexing configured.
> # Continuously load the system with puts.
> # Add one more node. It will join and will start processing put requests
> immediately.
> # For each request, indexing processor will try to get binary metadata and
> will block on utility cache rebalance future. This will block all threads in
> the system pool.
> # Utility cache rebalancing will be scheduled but will never start, because
> all threads in system pool are blocked.
> I think we should rebalance utility cache synchronously in exchange worker,
> like we do with the marshaller cache.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
