Sangeetha Hariharan created CLOUDSTACK-5371:
-----------------------------------------------
Summary: Maitenance mode for secondary store.
Key: CLOUDSTACK-5371
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5371
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
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
progress. ( In my case i stopped the nfs server)
4. Bring the Secondary storage server up after 12 hours. ( In my case started
the nfs server).
When secondary server was down (NFS server down) for about 12 hours , I see
that hourly snapshots get attempted every hour and fail with “CreatedOnPrimary"
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 out of
disk space on secondary store , he should be able to set “Maintenance Mode”
for secondary store , so that we have to ability to not even attempt snapshots
instead of attempting and failing and leaving behind snapshots in failed state.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
