[
https://issues.apache.org/jira/browse/CLOUDSTACK-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851000#comment-13851000
]
Min Chen commented on CLOUDSTACK-5392:
--------------------------------------
The correct fix for this bug is to fix related bug CLOUDSTACK-5371, that is, to
provide maintenance mode for a secondary store which has connection issue. Then
the first attempt of createSnapshot may fail, then admin can put the
problematic store in maintenance mode, then next time if createSnapshot is
invoked, CloudStack orchestration will choose another store to take and backup
snapshot, then everything will be fine. We don't need to overly optimize things
to handle uncommon scenarios.
> Multiple Secondary Store - There is no retry happening on snapshot failures
> when one of the secondary stores is not reachable.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5392
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5392
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.3.0
> Environment: Build from 4.3
> Reporter: Sangeetha Hariharan
> Assignee: Min Chen
> Priority: Critical
> Fix For: 4.3.0
>
> Attachments: 1205logs.rar
>
>
> Multiple Secondary Store - There is no retry happening on snapshot failures
> when one of the secondary stores is not reachable.
> Steps to reproduce the problem:
> Set up:
> Advanced zone set up with 2 Xenserver hosts.
> 2 secondary NFS stores - ss1 and ss2.
> Bring down ss1.
> Deployed 3 VMs.
> Create snapshots for ROOT volume of these 3 VMs.
> out of the 3 snapshot request , 2 were sent to ss1 and 1 to ss2.
> The 2 createSnapshot commands that were sent to ss1 , failed during
> "org.apache.cloudstack.storage.command.CopyCommand".
> But there was no retry done on ss2.
> Expected Behavior:
> On failure to back up on 1 secondary store , we should attempt on other
> secondary stores.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
