[jira] [Commented] (CLOUDSTACK-2919) Snapshot cannot be saved to full Secondary Storage, but doesn't utilize other Secondary Storage locations

["Nitin Mehta (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679398#comment-13679398 ] 

Nitin Mehta commented on CLOUDSTACK-2919:
-----------------------------------------

For a snapshot operation, following enhancements are required.

1. Before trying to backup snapshot, introduce an allocator to take considerations like size, load, previous snapshots etc. in consideration so
that a more refined decision can be taken for choosing sec. storage

2. If for some case backingup snapshot on one sec. storage fails, have a retry
mechanism to back it up on other sec. storage especially when the previous sec. storage has been down or has some size issues etc.
                
> Snapshot cannot be saved to full Secondary Storage, but doesn't utilize other Secondary Storage locations
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2919
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2919
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: Nitin Mehta
>             Fix For: 4.2.0
>
>
> This issue was noticed when the customer attempted to take a snapshot but failed.
> Logs revealed that the Secondary Storage to which CS was trying to save the
> Snapshot had no more free space. 
> CS did retry multiple times to save to the same Secondary Storage location
> after the initial failure but with no success.
> However, CS failed to notice two other Secondary Storage locations in the same
> zone with enough free space for a successful snapshot.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira