[jira] [Commented] (IGNITE-10251) Get rid of the code left from times when lateAffinity=false was supported

["Maxim Muzafarov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-10251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16948507#comment-16948507 ] 

Maxim Muzafarov commented on IGNITE-10251:
------------------------------------------

Moved to the next release due to inactivity. Please, feel free to move it back if you will be able to complete the ticket by 2.8 code freeze date, December 2, 2019.


> 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: Alexei Scherbakov
>            Assignee: Dmitriy Govorukhin
>            Priority: Major
>             Fix For: 2.9
>
>
> 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)