[
https://issues.apache.org/jira/browse/IGNITE-15450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17481846#comment-17481846
]
Pavel Pereslegin commented on IGNITE-15450:
-------------------------------------------
The final solution is to add a "wait" flag to wait for the entire operation to
complete.
*Create*
{noformat}
Create cluster snapshot:
control.(sh|bat) --snapshot create snapshot_name [--wait]
Parameters:
snapshot_name - Snapshot name.
wait - Wait for the entire operation to complete. Otherwise,
the operation will be performed in the background, and the command will
immediately return control.
{noformat}
*Restore*
{noformat}
Restore snapshot:
control.(sh|bat) --snapshot restore snapshot_name [--wait] [--groups
group1,...groupN]
Parameters:
snapshot_name - Snapshot name.
wait - Wait for the entire operation to complete. Otherwise,
the operation will be performed in the background, and the command will
immediately return control.
group1,...groupN - Cache group names.
{noformat}
> Add special option to run snapshot commands (create/restore) synchronously.
> ---------------------------------------------------------------------------
>
> Key: IGNITE-15450
> URL: https://issues.apache.org/jira/browse/IGNITE-15450
> Project: Ignite
> Issue Type: Improvement
> Components: control.sh
> Reporter: Pavel Pereslegin
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: iep-43, ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The process of restoring a snapshot fails if at least one of the restored
> caches already exists.
> However, when starting this operation via control.sh, the command returns a
> successful startup status, which can be confusing for users.
> We can improve this behavior by adding a separate check for existing caches
> when starting the restore operation and displaying a user-friendly error
> message.
> An *alternative* option is to start a snapshot restore operation
> synchronously.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
