You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/02 15:47:02 UTC
[jira] [Updated] (IGNITE-10651)
GridCachePartitionExchangeManager.affinityReadyFuture() should return
GridDhtTopologyFuture instead of IgniteInternalFuture
[ https://issues.apache.org/jira/browse/IGNITE-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Muzafarov updated IGNITE-10651:
-------------------------------------
Fix Version/s: (was: 2.8)
> GridCachePartitionExchangeManager.affinityReadyFuture() should return GridDhtTopologyFuture instead of IgniteInternalFuture
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-10651
> URL: https://issues.apache.org/jira/browse/IGNITE-10651
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.7
> Reporter: Vyacheslav Koptilin
> Priority: Minor
>
> Under some circumstances, {{GridCachePartitionExchangeManager.affinityReadyFuture}} returns {{GridFinishedFuture}} or {{GridCachePartitionExchangeManager.AffinityReadyFuture}}
> Obviously, the returned future cannot be used in order to validate a cache. It seems that this behavior can be improved if {{affinityReadyFuture()}} returns an instance of {{GridDhtTopologyFuture,}} and therefore, it will simplify the logic related to cache validation.
> Perhaps, {{ExchangeFutureSet}} can be changed to {{ExchangeFutureMap}} that should contain a mapping of topology version to the corresponding {{GridDhtTopologyFuture}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)