Critical Description
What is the problem?
When the offset for merges is 0 (and possibly in other cases) the start and end time calculated are the day before. Here is a go playground showing the problem.
Context
Hyun-Ju Vega found that when using the hourly backups plan the first merge was failing. The problem was info was exiting with status code 1:
2024-01-03T14:30:55.318Z INFO (Runner) Running command /opt/couchbase/bin/cbbackupmgr info --archive /home/ec2-user/cb_backup_20240101 --offset 0 --limit 0 --json --repo 023110cf-78f9-494d-a023-982356cc6260 --start 2024-01-02T00:00:00Z --end 2024-01-02T23:59:59.999999999Z
|
Note that the start and end times are the day before. The hourly backups plan is meant to merge everything done on the current day. It looks like the change in MB-58028 has broken this use case.
Note: Not just the first merge, but every merge failed.
Attachments
Issue Links
- is caused by
-
MB-58028 [CBBS] Merges do not respect timezone
-
- Reopened
-
| For Gerrit Dashboard: MB-60273 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 203259,9 | MB-60273 Merge times wrong if offset is zero | master | cbbs | Status: MERGED | +2 | +1 |