14.3.16 import (imports data)
- Organization of this subsection
(1) Description
This subcommand imports data from the store data files to which data has been exported from memory caches.
The subcommand relocates data by importing (put) the data from store data files.
(2) Rules
-
You can execute this subcommand when the cluster's status is 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.
-
You can execute this subcommand when the target EADS servers are in initialized status.
-
To prevent a full garbage collection (FullGC) from occurring while operations are underway, each EADS server performs FullGC when this subcommand terminates.
-
While this subcommand has obtained a lock from the EADS server, the EADS server is not isolated. However, if a process is shut down or the EADS server terminates while the subcommand has the lock, the lock is released, and then the EADS server is isolated.
(3) Format
eztool import [-d path-name-of-store-data-file-storage-location]
[--convertid EADS-server-ID-conversion-rule]
[store-data-file-key]
(4) Options and arguments
(a) -d path-name-of-store-data-file-storage-location or --directory path-name-of-store-data-file-storage-location
This option specifies the path name of the store data file storage location.
Specify this option to import only the store data files located in the specified directory.
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 you specify a relative path for the path name of the store data file storage location, the path is relative to the management directory of each EADS server.
(b) --convertid EADS-server-ID-conversion-rule
Specify this option if you have grouped keys by specifying the EADS server ID of the storage location (EADS server ID specified groups are used) and if you want to convert the specified EADS server ID to another EADS server ID and import data.
Specify the EADS server ID conversion rule in the following format:
source-EADS-server-ID>target-EADS-server-ID
You can specify for the source EADS server ID and the target EADS server ID 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 at the beginning or at the end
Example: --convertid ,1>2,
-
Null character string delimited by commas or a character string consisting of only spaces that is delimited by commas
Example: --convertid 1>2,, ,
(c) store-data-file-key
This option specifies the store data file key of a store data file.
Specify the store data file key of a store data file that was output by the eztool export or eztool stop command.
If the store data file key is omitted, the store data file with the most recent store data file key displayed in latest by the eztool listesd command is imported automatically.
A store data file with the following name will be imported:
|
Command used to output the store data file |
Store data file name |
|---|---|
|
eads_YYYYMMDDhhmmss_EADS-server-ID.esd |
|
|
eads_stop_YYYYMMDDhhmmss_EADS-server-ID.esd |
- Legend:
-
YYYYMMDDhhmmss: Command execution date and time
YYYY: year, MM: month, DD: day, hh: hour (00 through 23), mm: minute, ss: second
If an EADS server or the store data file storage directory contains multiple store data files, this subcommand automatically imports the store data file with the most recent command execution date and time.
If there are multiple store data file with the same command execution date and time (with only the EADS server ID being different), the subcommand imports all the applicable store data files.
If a store data file output by the eztool export command has the same command execution date and time as a store data file output by the eztool stop command, the subcommand imports the store data file output by the eztool export command.
(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
-
The subcommand does not import a corrupted or invalid store data file.
-
If data is imported from a store data file that was created by an EADS server whose version is earlier than 03-00, valid operation is not guaranteed.
-
Processing of the subcommand 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.
-
When data imported (put) from a store data file and data already in the cache have the same key name, the subcommand checks the key update dates and times and overwrites the data already in the cache only when the data's update date and time in the store data file are 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.