You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2021/12/20 18:30:00 UTC
[jira] [Assigned] (IGNITE-16177) Snapshot restore operation may hang if cache contains "empty" partitions
[ https://issues.apache.org/jira/browse/IGNITE-16177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Pereslegin reassigned IGNITE-16177:
-----------------------------------------
Assignee: Pavel Pereslegin
> Snapshot restore operation may hang if cache contains "empty" partitions
> ------------------------------------------------------------------------
>
> Key: IGNITE-16177
> URL: https://issues.apache.org/jira/browse/IGNITE-16177
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.12
> Reporter: Pavel Pereslegin
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: iep-43
>
> The snapshot restore may hang when some of the cache group partitions have not been physically created (for example, there is not enough data in the cache).
> Reproducer
> {code:java}
> public class IgniteClusterSnapshotRestoreEmptyPartsTest extends IgniteClusterSnapshotRestoreBaseTest {
> @Test
> public void testRestoreWithEmptyPartition() throws Exception {
> // Cache with 1024 partitions.
> CacheConfiguration<Integer, Object> cacheCfg1 = new CacheConfiguration<>(CACHE1);
> // Add only 10 keys (only 10 partitions will be created on the disk).
> IgniteEx ignite = startGridsWithCache(1, 1024, Integer::new, cacheCfg1);
> // Snapshot contains only 10 (out of 1024 "affinity" partitions).
> ignite.snapshot().createSnapshot(SNAPSHOT_NAME).get(TIMEOUT);
> ignite.cache(CACHE1).destroy();
> // The restore operation hangs during the "preload" phase.
> ignite.snapshot().restoreSnapshot(SNAPSHOT_NAME, null).get(TIMEOUT);
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)