You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2016/03/24 12:11:25 UTC
[jira] [Created] (IGNITE-2885) Avoid usage of
GridDhtLocalPartition.rmvQueue for Transactional caches
Denis Magda created IGNITE-2885:
-----------------------------------
Summary: Avoid usage of GridDhtLocalPartition.rmvQueue for Transactional caches
Key: IGNITE-2885
URL: https://issues.apache.org/jira/browse/IGNITE-2885
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 1.5.0.final
Reporter: Denis Magda
There is a property that controls maximum remove queue
history for atomic caches (IgniteSystemProperties.IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE).
The strange thing is that this property is also used for transactional
caches as well allocating {{GridDhtLocalPartition.rmvQueue}}
regardless of a cache atomicity type which looks confusing.
In case of transaction caches the queue is used to resolve rebalancing and concurrent puts races. We can try remove it once a partition gets loaded.
Seems that we can't get rid off the queue completely because to support this we need to switch to fair thread-per-partition design.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)