14.3.26 importecf (relocates persistent data)
This subsection is applicable when you are using disk caches or two-way caches.
- Organization of this subsection
(1) Description
This subcommand relocates persistent data by importing (put) data from cache data files and cache index files located in a specified directory.
When you add EADS servers to the cluster, delete EADS servers from the cluster, or change the multiplicity and size of data, you can use this subcommand to relocate data from cache data files.
(2) Rules
-
This subcommand can be executed only when the status of the cluster is the following:
-
Cluster available (AVAILABLE)
-
-
The target of this subcommand is the EADS servers whose cluster participation status is online. This subcommand cannot be executed if the cluster contains any EADS server whose cluster participation status is standby. You can determine the cluster participation status with the eztool status command.
-
This subcommand can be executed when the target EADS servers are in the following status:
-
Initialized
-
-
To prevent a full garbage collection (FullGC) from occurring while operations are underway, each EADS server performs FullGC when this subcommand terminates.
-
An EADS server is not isolated while this subcommand has obtained a lock from the EADS server. However, if the process is shut down or the EADS server terminates while the subcommand has the lock, the lock is released, and then the EADS server becomes isolated.
(3) Format
eztool importecf [--convertid EADS-server-ID-conversion-rule]
path-name-of-storage-for-cache-data-files-and-cache-index-files
(4) Options and arguments
(a) --convertid EADS-server-ID-conversion-rule
Specify this option if you have grouped keys by specifying the EADS server IDs of the storage locations (EADS server ID specified groups are used) and you want to convert the specified EADS server IDs to other EADS server IDs and import the data.
Specify each EADS server ID conversion rule in the following format:
source-EADS-server-ID>target-EADS-server-ID
For the source EADS server ID and the target EADS server ID, you can specify an integer in the range from 1 to 96 (a two-digit integer beginning with zero, such as 01 and 02, cannot be specified).
The target EADS server ID must differ from the source EADS server ID.
If you specify multiple EADS server ID conversion rules, delimit them with the comma. When multiple EADS server ID conversion rules are specified, the order in which the rules are specified has no effect on the priority. Note that the same source EADS server ID cannot be specified more than once.
The following characters and character strings are ignored:
-
Comma specified at the beginning or at the end
Example: --convertid ,1>2,
-
Null character string delimited by commas or a character string consisting only of spaces that is delimited by commas
Example: --convertid 1>2,, ,
(b) path-name-of-storage-for-cache-data-files-and-cache-index-files
This option specifies the path name of the storage location for the cache data files and cache index files that you want to import.
The path name cannot be a directory that contains an asterisk (*), double quotation mark ("), question mark (?), vertical bar (|), less-than sign (<), or greater-than sign (>).
If a relative path is specified as the path of the cache data file and cache index file storage location, it is treated as being relative to the management directory.
(5) Return code
The following table lists the return codes that this subcommand returns.
|
No. |
Return code |
Description |
|
|---|---|---|---|
|
eads.command.compat parameter omitted in the command properties |
0300 specified in the eads.command.compat parameter in the command properties |
||
|
1 |
0 |
0 |
Command execution was successful. |
|
2 |
101 |
101 |
Initialization of the command failed. |
|
3 |
110 |
Connection establishment failed. |
|
|
4 |
111 |
The command failed due to a communication timeout. |
|
|
5 |
120 |
The command failed due to a syntax error. |
|
|
6 |
130 |
The command failed because it could not be executed. |
|
|
7 |
131 |
The command failed because another command was executing. |
|
|
8 |
150 |
The command failed during execution. |
|
|
9 |
200 |
The command failed due to a timeout. |
|
(6) Notes
-
Output directories for cache information files, cache index files, and cache data files cannot be specified.
-
When this subcommand is executed, all cache persistent data files and cache index files in the directory subject to import processing are imported.
-
If the cache data files and cache index files that are to be imported are corrupted or were open when a failure occurred, deleted data might be restored.
-
If an error occurs while the subcommand is processing a set of a cache data file and a cache index file subject to import processing, the subcommand processes the next set of a cache data file and a cache index file. In such a case, the subcommand results in an error. If this happens, execute the following commands to determine the problem:
-
Execute the eztool status command to check the cluster status.
-
Execute the eztool listcache command to check the list of caches.
-
-
This subcommand's processing might require a considerable amount of time depending on the number of data items and the amount of data, because data items are added again individually.
-
If data with the key to be imported (put) already exists, the subcommand checks the key update dates and times and overwrites the data only when the update date and time of the key to be imported is the more recent.
-
When data with keys including EADS server ID specified groups is added and there is no range for a specified EADS server ID, the subcommand does not add that data. If this happens, a one-time warning message is issued.
-
The total data restriction function is disabled while this subcommand is executing.