You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sangeetha Hariharan (JIRA)" <ji...@apache.org> on 2013/12/06 04:20:37 UTC
[jira] [Updated] (CLOUDSTACK-5392) Multiple Secondary Store - There
is no retry happening on snapshot failures when one of the secondary stores
is not reachable.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sangeetha Hariharan updated CLOUDSTACK-5392:
--------------------------------------------
Attachment: 1205logs.rar
> 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
> 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#6144)