Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 11 Dec 2013 02:14:07 +0000 (UTC)
From: "Animesh Chaturvedi (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12682762.1386187668201.14655.1386728047961@arcas>
In-Reply-To: <JIRA.12682762.1386187668201@arcas>
References: <JIRA.12682762.1386187668201@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-5371) Maitenance mode for secondary
 store.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5371?page=3Dcom.atl=
assian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Animesh Chaturvedi updated CLOUDSTACK-5371:
-------------------------------------------

    Issue Type: New Feature  (was: Bug)

> Maitenance mode for secondary store.
> ------------------------------------
>
>                 Key: CLOUDSTACK-5371
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-537=
1
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>          Components: Management Server
>    Affects Versions: 4.3.0
>         Environment: Build from 4.3
>            Reporter: Sangeetha Hariharan
>            Assignee: edison su
>            Priority: Critical
>             Fix For: Future
>
>
> Set up:
> Advanced Zone with 2 Xenserver 6.2 hosts:
> 1. Deploy 5 Vms in each of the hosts with 10 GB ROOT volume size , so we =
start with 10 Vms.
> 2. Start concurrent snapshots for ROOT volumes of all the Vms by creating=
 hourly snapshots.
> 3. Shutdown the Secondary storage server when the snapshots are in the pr=
ogress. ( In my case i stopped the nfs server)
> 4. Bring the Secondary storage server up after 12 hours. ( In my case sta=
rted the nfs server).
> When secondary server was down (NFS server down) for about 12 hours , I s=
ee that hourly snapshots get attempted every hour and fail with =E2=80=9CCr=
eatedOnPrimary" state . I see many entries ( 2 per failed snapshot attempt)=
 being created on the primary store.
> In such cases , if the admin is aware of  connectivity issues/ running ou=
t of disk space on secondary store , he should be able to set  =E2=80=9CMai=
ntenance Mode=E2=80=9D for secondary store , so that we have to ability to =
not even attempt snapshots instead of attempting and failing and leaving be=
hind snapshots in failed state.


--
This message was sent by Atlassian JIRA
(v6.1.4#6159)