Recalling a Volume to filesystem
Explains how to recall offloaded data to the filesystem.
- Read data offloaded to a remote target (or cold tier), data is automatically recalled to the filesystem to allow the read to succeed.
- Modify data offloaded to an erasure coded volume (or warm tier) or a remote target (or cold tier), data is automatically recalled to the filesystem to allow the write to succeed.
- Purged based on the expiration time period set at the volume level for recalled data if there are no changes (for example, read operation).
- Offloaded based on the rule and the expiration time period set at the volume level for recalled data if there are changes (for example, overwrite operation).
See Data Reads, Writes, and Recalls for more information. If the recall fails, CLDB retries the operation after some time. See Retrying Failed Operation for more information.
You can manually recall all data in a volume using the Control System, CLI, or the REST API.
You can also recall individual files from the tier. See Recalling a File to filesystem Using the CLI and REST API for more information.
Recalling Offloaded Volume Using the Control System
-
Log in to the Control System and click
.Note: The Volumes page is under the Volumes menu in the Kubernetes version of the Control System.
-
Select the tiered volumes to recall from the list of volumes in
the Volumes pane.
Selecting a volume makes the Actions drop-down menu available.
- Click Recall Data from the Actions drop-down menu to display the Recall Tiered Data confirmation window.
-
Review the list of volumes to recall and click Recall
Volumes.
For more information, see Recall of Tiered Data.
Recalling Offloaded Volume Using the CLI and REST API
Run the following command to recall volume data:
/opt/mapr/bin/maprcli volume recall -name <volName>
curl -k -X POST 'https://abc.sj.us:8443/rest/volume/recall?name=volName' --user mapr:mapr
For more information, see volume recall
.