You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2022/06/02 14:14:00 UTC
[jira] [Updated] (IGNITE-15067) Add custom destination path to the snapshost API
[ https://issues.apache.org/jira/browse/IGNITE-15067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Pereslegin updated IGNITE-15067:
--------------------------------------
Description:
The default configuration path obtains from the IgniteConfiguration. However, in some circumstances, it is good to set this destination path at runtime. This path must be configured relatively in the node working directory and must be accessible from the security point of view.
Proposed API:
{code:java}
public IgniteFuture<Void> createSnapshot(String name, String locPath);
{code}
control.sh *create* snapshot command syntax
{noformat}
control.(sh|bat) --snapshot create snapshot_name [--dest path] [--sync]
Parameters:
snapshot_name - Snapshot name.
--dest path - Path to the directory where the snapshot will be saved. If not specified, the configured default snapshot directory will be used.
--sync - Run the operation synchronously, the command will wait for the entire operation to complete. Otherwise, it will be performed in the background, and the command will immediately return control.
{noformat}
control.sh *check* snapshot command syntax
{noformat}
control.(sh|bat) --snapshot check snapshot_name [--src path]
Parameters:
snapshot_name - Snapshot name.
--src path - Path to the directory where the snapshot files are located. If not specified, the default configured snapshot directory will be used.
{noformat}
control.sh *restore* snapshot command syntax
{noformat}
control.(sh|bat) --snapshot restore snapshot_name --start [--groups group1,...groupN] [--src path] [--sync]
Parameters:
snapshot_name - Snapshot name.
--groups group1,...groupN - Cache group names.
--src path - Path to the directory where the snapshot files are located. If not specified, the default configured snapshot directory will be used.
--sync - Run the operation synchronously, the command will wait for the entire operation to complete. Otherwise, it will be performed in the background, and the command will immediately return control.
{noformat}
was:
The default configuration path obtains from the IgniteConfiguration. However, in some circumstances, it is good to set this destination path at runtime. This path must be configured relatively in the node working directory and must be accessible from the security point of view.
Proposed API:
{code}
public IgniteFuture<Void> createSnapshot(String name, String locPath);
{code}
control.sh *create* snapshot command syntax
{noformat}
control.(sh|bat) --snapshot create snapshot_name [--dest path] [--sync]
Parameters:
snapshot_name - Snapshot name.
path - Path to the directory where the snapshot will be saved. If not specified, the default snapshot directory will be used.
sync - Run the operation synchronously, the command will wait for the entire operation to complete. Otherwise, it will be performed in the background, and the command will immediately return control.
{noformat}
control.sh *check* snapshot command syntax
{noformat}
control.(sh|bat) --snapshot check snapshot_name [--src path]
Parameters:
snapshot_name - Snapshot name.
path - Path to the directory where the snapshot files are located. If not specified, the default snapshot directory will be used.
{noformat}
control.sh *restore* snapshot command syntax
{noformat}
control.(sh|bat) --snapshot restore snapshot_name --start [--groups group1,...groupN] [--src path] [--sync]
Parameters:
snapshot_name - Snapshot name.
group1,...groupN - Cache group names.
path - Path to the directory where the snapshot files are located. If not specified, the default snapshot directory will be used.
sync - Run the operation synchronously, the command will wait for the entire operation to complete. Otherwise, it will be performed in the background, and the command will immediately return control.
{noformat}
> Add custom destination path to the snapshost API
> ------------------------------------------------
>
> Key: IGNITE-15067
> URL: https://issues.apache.org/jira/browse/IGNITE-15067
> Project: Ignite
> Issue Type: Improvement
> Reporter: Maxim Muzafarov
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: iep-43, ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The default configuration path obtains from the IgniteConfiguration. However, in some circumstances, it is good to set this destination path at runtime. This path must be configured relatively in the node working directory and must be accessible from the security point of view.
> Proposed API:
> {code:java}
> public IgniteFuture<Void> createSnapshot(String name, String locPath);
> {code}
> control.sh *create* snapshot command syntax
> {noformat}
> control.(sh|bat) --snapshot create snapshot_name [--dest path] [--sync]
> Parameters:
> snapshot_name - Snapshot name.
> --dest path - Path to the directory where the snapshot will be saved. If not specified, the configured default snapshot directory will be used.
> --sync - Run the operation synchronously, the command will wait for the entire operation to complete. Otherwise, it will be performed in the background, and the command will immediately return control.
> {noformat}
> control.sh *check* snapshot command syntax
> {noformat}
> control.(sh|bat) --snapshot check snapshot_name [--src path]
> Parameters:
> snapshot_name - Snapshot name.
> --src path - Path to the directory where the snapshot files are located. If not specified, the default configured snapshot directory will be used.
> {noformat}
> control.sh *restore* snapshot command syntax
> {noformat}
> control.(sh|bat) --snapshot restore snapshot_name --start [--groups group1,...groupN] [--src path] [--sync]
> Parameters:
> snapshot_name - Snapshot name.
> --groups group1,...groupN - Cache group names.
> --src path - Path to the directory where the snapshot files are located. If not specified, the default configured snapshot directory will be used.
> --sync - Run the operation synchronously, the command will wait for the entire operation to complete. Otherwise, it will be performed in the background, and the command will immediately return control.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)