Backup should recover from primary Space when using non-persistent blob-store data policy

Description

Backup recover both from external data source & from primary in case of memXtend presist=false

Deploying a space with non-persistent blob store and external data source with non-centeral ssd and mirror (central data source true)
result in primary retrieving data from an external source as expected but backup - loads from an external source and in addition recover data from primary leading for duplicate errors per all objects & Problem is OOM in the backup while recovering.
attached pu and logs. The issue is in 14.5 version, also available backup and primary heap dumps that show the diff in memory consumption while recovering.

Activity

Show:
Ester Atzmon
October 18, 2020, 6:49 AM
Edited

Related test in 14.5 attached MemXtendRecovery.zip – see that backup recover from db and print duplicated while recovery also from primary. customer will need a patch on top of 14.5 version.

( in tgrid: TestMemXtendBackupRecovery was added to master while investigating the above issue, tried to tun Tgrid test with following parameters:

-Dcom.gigaspaces.quality.tf.rocksdb-blobstore.enabled=true
-Dblobstore.persistent=false
-Dblobstore.entriespercentage=0
-Dblobstore.paths=[~/data/db1,~/data/db2]
-Dblobstore.mappingDir=~/data

Saw that paths and mapping had no impact and default was used and persisten=false caused a failure to create the space -> change to true works fine - but it's not the desired test.

)

Meron Avigdor
November 8, 2020, 6:48 PM

branch name: 14.5.0-patch-g-build

Meron Avigdor
November 12, 2020, 7:39 AM

Added Test src/main/java/com/gigaspaces/test/support/SO4IT/case5316/MemXtendBackupRecoveryTest.java

to master branch. commit:

Assignee

Meron Avigdor

Reporter

Ester Atzmon

Labels

None

Priority

Critical

SalesForce Case ID

None

Fix versions

Commitment Version/s

None

Due date

None

Product

None

Edition

Open Source

Platform

All
Configure