You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Igor Kamyshnikov (JIRA)" <ji...@apache.org> on 2019/02/12 11:17:00 UTC
[jira] [Created] (IGNITE-11296) 3rd-party persistence: Backup and
primary partitions data differ after a single IgniteCache.get that loaded
data from the persistent store which breaks skipStore behavior
Igor Kamyshnikov created IGNITE-11296:
-----------------------------------------
Summary: 3rd-party persistence: Backup and primary partitions data differ after a single IgniteCache.get that loaded data from the persistent store which breaks skipStore behavior
Key: IGNITE-11296
URL: https://issues.apache.org/jira/browse/IGNITE-11296
Project: Ignite
Issue Type: Bug
Components: cache, cassandra
Affects Versions: 2.7, 2.5
Reporter: Igor Kamyshnikov
1) run 2 ignite servers on different machines
(this is important because of org.apache.ignite.internal.processors.cache.GridCacheContext#selectAffinityNodeBalanced - it takes into account MACs)
2) run cassandra and insert some records into cassandra
3) connect to the ignite cluster as Ignite client node and invoke
IgniteCache.get(pk);
4) execute IgniteCache.withSkipStore().get(pk) several times
The values returned will be randomly NULLs or non-NULLs.
5) depending on a chance, the data loaded in 3) can appear in primary partition or backup partition. If they are in backup partition, then they are not visible to Ignite JDBC.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)