[
https://issues.apache.org/jira/browse/IGNITE-10251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-10251:
---------------------------------------
Fix Version/s: (was: 2.9)
2.10
> Get rid of the code left from times when lateAffinity=false was supported
> -------------------------------------------------------------------------
>
> Key: IGNITE-10251
> URL: https://issues.apache.org/jira/browse/IGNITE-10251
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Scherbakov
> Assignee: Dmitriy Govorukhin
> Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This code can hide errors and lead to inefficient processing in some
> scenarios.
> Some examples:
> * *Forced key preloading*
> {code:java}
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture
> and related stuff{code}
> which is called if key is mapped to moving partition
> * *Unnecessary dht lock processing*
> {code:java}
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture#map(java.lang.Iterable<org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry>)
> {code}
> needVal is always false if lateAff=true
> Also
> \{{org.apache.ignite.configuration.IgniteConfiguration#setLateAffinityAssignment}}
> must be removed in 3.0
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
