recover metaspace

Used to restore all of the spaces of a metaspace when shared-nothing persistence is used.

Syntax

Note: The options with data and without data with recovery_policy, are mutually exclusive. You can only use one of them in the command. 
recover metaspace 
         [recovery_policy <string> 
           | with data (deprecated) 
           | without data (deprecated)] 
         [quorum <integer>] 
         [keep_files <boolean>] 
         [thread_count <integer>]
Note: The options with data and without data with recovery_policy, are mutually exclusive. You can only use one of them in the command.

Parameters

The following table lists the parameters for this command with a description of each parameter.

recover metaspace Parameters
Parameter Description
recovery_policy
Optional. A string indicating which of the following recovery policies to use when restoring the data for each space in the metaspace:
  • no_data - Does not recover data with the metaspace.
  • without_data - Deprecated. Use no_data instead. Specifies that the spaces of the metaspace should be restored without their data.
  • no_data_loss - (Default.) Start data recovery when there are enough seeders to ensure data loss does not occur.
  • with data - (Optional/Deprecated). Use no_data_loss instead. Specifies that the spaces of the metaspace should be restored with their data which was previously persisted to disk. 'with data' is the same as specifying recovery_policy no_data_loss.
  • data_loss - Start data recovery immediately even if there is a chance of a data loss.
  • fast_load_only - Start data recovery once all seeders are ready.
  • robust_load_only - Start data recovery when there are enough seeders to ensure data loss will not occur. This option will ensure fast load is not attempted.
  • force_load - Start data recovery immediately even if data loss will occur. Ignores all checks for required hosts/seeders and fast load is not attempted.
data Optional/Deprecated. Specifies whether the data from the space should be restored with the space. Specifying with indicates that the data from the space, which has been persisted to disk, should be restored with the space. Specifying without indicates the space should be restored without its data.
Attention: The options with data and without data are now deprecated. Use no_data_loss and no_data instead respectively.
quorum Optional. An integer that specifies the minimum number of seeders which are needed for recovery to start. The default is 1.
keep_files Optional. A boolean value that indicates whether the persistence files should be saved or deleted after recovery is complete. The default is false.
thread_count Optional.

An integer that specifies the number of threads to use for recovering spaces during the recovery process. Spaces can be recovered in parallel using this option. The default is 1.

Note: When recovering a space which has a capacity defined, by default only the keys and indexes of the space are restored to memory regardless of whether or not the capacity has been reached. When capacity has been defined for a space, you can force the recovery of all data for a space, up to the capacity, by using the robust_load_only recovery policy. For any other recovery policy setting, the default behavior of only loading keys and indexes to memory is enforced. The data part of the tuple gets loaded into memory on subsequent access.

Example

recover space ’myspace’ no_data_loss
Note: String values passed as parameters must be enclosed in either single or double quotes.
Related concepts
Related tasks
Related reference