You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test Description
Check that the blobber can regain ability to gain rewards and act normally after crashing and reviving empty (with all data cleaned) by restoring its data from a historical Backup Snapshot of the data directory.
Test Scenario
Similar to node-recovery-2 test (Blobber/Validator Node Recovery). Changes are:
Need to take historical backup of the data & files directory of the blobber before it's dropped (for example: tar -czvf blobber-data-1.tar.gz ./docker.local/blobber1/data & tar -czvf blobber-files-1.tar.gz ./docker.local/blobber1/files), then wait for some time before dropping the blobber.
Need to clean all the data/files of the blobber after it's dropped (for example: rm -rf ./docker.local/blobber1/data & rm -rf ./docker.local/blobber1/files).
Need to restore the backup before reviving the blobber (for example: tar -xzvf blobber-data-1.tar.gz -C ./docker.local/blobber1/data & tar -xzvf blobber-files-1.tar.gz -C ./docker.local/blobber1/files.
Comment/DM if anything is unclear.
The text was updated successfully, but these errors were encountered:
Test Description
Check that the blobber can regain ability to gain rewards and act normally after crashing and reviving empty (with all data cleaned) by restoring its data from a historical Backup Snapshot of the data directory.
Test Scenario
Similar to node-recovery-2 test (Blobber/Validator Node Recovery). Changes are:
tar -czvf blobber-data-1.tar.gz ./docker.local/blobber1/data
&tar -czvf blobber-files-1.tar.gz ./docker.local/blobber1/files
), then wait for some time before dropping the blobber.rm -rf ./docker.local/blobber1/data
&rm -rf ./docker.local/blobber1/files
).tar -xzvf blobber-data-1.tar.gz -C ./docker.local/blobber1/data
&tar -xzvf blobber-files-1.tar.gz -C ./docker.local/blobber1/files
.Comment/DM if anything is unclear.
The text was updated successfully, but these errors were encountered: