Netapp RPO for replicas should be longer than replica schedule
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
In Progress
|
Medium
|
kiran pawar |
Bug Description
Hi,
I have an observation related to https:/
I noted that the 'hourly' schedule was matched with the one hour check of snapmirror last-transfer-
But on top I think this was flawed, since it does not respect the time that the transfer itself is consuming.
E.g.
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-
The RPO of a hourly schedule is higher than 1 hour.
Looking at what is done at other places I found: https:/
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.
Best,
Maurice
tags: | added: netapp |
tags: | added: replication |
Changed in manila: | |
assignee: | nobody → kiran pawar (kpdev) |
importance: | Undecided → Medium |
milestone: | none → antelope-rc1 |
Changed in manila: | |
milestone: | antelope-rc1 → bobcat-1 |
Fix proposed to branch: master /review. opendev. org/c/openstack /manila/ +/866883
Review: https:/