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/03 10:02:03 UTC
[jira] [Updated] (IGNITE-8652) Cache dynamically started from
client while there are no affinity server nodes will be forever considered
in-memory
[ https://issues.apache.org/jira/browse/IGNITE-8652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Muzafarov updated IGNITE-8652:
------------------------------------
Fix Version/s: (was: 2.8)
2.9
> Cache dynamically started from client while there are no affinity server nodes will be forever considered in-memory
> -------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-8652
> URL: https://issues.apache.org/jira/browse/IGNITE-8652
> Project: Ignite
> Issue Type: Bug
> Reporter: Ivan Rakov
> Priority: Major
> Labels: IEP-4, Phase-2
> Fix For: 2.9
>
>
> We implemented stealing data storage configuration from affinity server node during initialization of dynamic cache on client (IGNITE-8476). Though, if there are no affinity nodes at the moment of cache start, client will consider cache as in-memory even when affinity node will proper data storage configuration (telling that it's actually persistent cache) will appear.
> That means cache operations on client may fail with the same error:
> {noformat}
> java.lang.AssertionError: Wrong ready topology version for invalid partitions response
> {noformat}
> ClientAffinityAssignmentWithBaselineTest#testDynamicCacheStartNoAffinityNodes should pass after the fix.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)