Netapp RPO for replicas should be longer than replica schedule

Bug #1996859 reported by Maurice Escher
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Fix Released
kiran pawar

Bug Description


I have an observation related to

I noted that the 'hourly' schedule was matched with the one hour check of snapmirror last-transfer-end-timestamp in

But on top I think this was flawed, since it does not respect the time that the transfer itself is consuming.

Let's assume my hourly scheduled transfer runs at 8:04.
There is not much data to copy, so it runs 1 minute -> finished at 8:05.
Next transfer runs at 9:04.
This time there is a bit more data to transfer, it runs 10 minutes until 9:14.

Manila checking at 9:10 would see the last-transfer-end-timestamp of 8:05 and report out of sync.
The RPO of a hourly schedule is higher than 1 hour.

Looking at what is done at other places I found: with giving an RPO of double the time set of the schedule, which makes sense to me. The more often the transfer runs, the less data it has to copy and the faster it completes.

I assume the configurable schedule (fix of bug 1996750) lands, so the RPO can't stay hardcoded anyway.
I suggest to either make the RPO configurable (and document with some hints) or calculate it based on the schedule.


tags: added: netapp
tags: added: replication
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

Fix proposed to branch: master

Changed in manila:
status: New → In Progress
Changed in manila:
assignee: nobody → kiran pawar (kpdev)
importance: Undecided → Medium
milestone: none → antelope-rc1
Changed in manila:
milestone: antelope-rc1 → bobcat-1
Changed in manila:
milestone: bobcat-1 → bobcat-2
Changed in manila:
status: In Progress → Fix Committed
Changed in manila:
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/manila

This issue was fixed in the openstack/manila release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.