You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Valentin Kulichenko (JIRA)" <ji...@apache.org> on 2016/04/29 09:33:13 UTC
[jira] [Created] (IGNITE-3073) Possible thread starvation due to
rebalancing
Valentin Kulichenko created IGNITE-3073:
-------------------------------------------
Summary: 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)