Correct the display of PITR chunks for pbm status output

Description

 

Backups: ======== S3 MinIO s3://http://127.0.0.1:9000/bkt/pbm   Snapshots:     2022-06-21T11:29:03Z 221.14MB <logical> [complete: 2022-06-21T11:29:11Z]     2022-06-06T12:16:35Z 221.07MB <logical> [complete: 2022-06-06T12:16:45Z]     2022-04-14T09:52:17Z 222.15MB <logical> [complete: 2022-04-14T09:52:25Z]     2022-04-01T09:53:07Z 222.15MB <logical> [complete: 2022-04-01T09:53:16Z]     2022-04-01T09:51:53Z 221.42MB <logical> [complete: 2022-04-01T09:52:02Z]     2022-03-30T14:05:28Z 222.08MB <logical> [complete: 2022-03-30T14:05:36Z]     2022-03-25T16:17:06Z 222.00MB <logical> [complete: 2022-03-25T16:17:17Z]     2022-03-25T16:12:16Z 221.83MB <logical> [complete: 2022-03-25T16:12:24Z]     2022-03-25T16:11:19Z 221.82MB <logical> [complete: 2022-03-25T16:11:27Z]     2022-03-25T16:08:57Z 9.27MB <logical> [complete: 2022-03-25T16:09:05Z]     2022-03-25T15:48:50Z 1.49GB <logical> [complete: 2022-03-25T15:49:08Z]     2022-03-25T15:46:24Z 191.66MB <logical> [complete: 2022-03-25T15:46:33Z]     2022-03-25T15:32:23Z 184.33MB <logical> [complete: 2022-03-25T15:32:32Z]   PITR chunks [2.08MB]:     2022-06-21T11:29:11Z - 2022-06-21T11:35:19Z (no base snapshot)     2022-04-14T09:52:25Z - 2022-04-14T10:08:44Z (no base snapshot)     2022-03-30T14:05:36Z - 2022-03-30T14:47:39Z (no base snapshot)

 

  1. All ranges have respective base snapshots contrary to what is displayed.

  2. All ranges should start from +1 second. See https://jira.percona.com/browse/PBM-686

`pbm list` works fine:

Backup snapshots:   2022-03-25T15:32:23Z <logical> [complete: 2022-03-25T15:32:32Z]   2022-03-25T15:46:24Z <logical> [complete: 2022-03-25T15:46:33Z]   2022-03-25T15:48:50Z <logical> [complete: 2022-03-25T15:49:08Z]   2022-03-25T16:08:57Z <logical> [complete: 2022-03-25T16:09:05Z]   2022-03-25T16:11:19Z <logical> [complete: 2022-03-25T16:11:27Z]   2022-03-25T16:12:16Z <logical> [complete: 2022-03-25T16:12:24Z]   2022-03-25T16:17:06Z <logical> [complete: 2022-03-25T16:17:17Z]   2022-03-30T14:05:28Z <logical> [complete: 2022-03-30T14:05:36Z]   2022-04-01T09:51:53Z <logical> [complete: 2022-04-01T09:52:02Z]   2022-04-01T09:53:07Z <logical> [complete: 2022-04-01T09:53:16Z]   2022-04-14T09:52:17Z <logical> [complete: 2022-04-14T09:52:25Z]   2022-06-06T12:16:35Z <logical> [complete: 2022-06-06T12:16:45Z]   2022-06-21T11:29:03Z <logical> [complete: 2022-06-21T11:29:11Z] PITR <off>:   2022-03-30T14:05:37Z - 2022-03-30T14:47:39Z   2022-04-14T09:52:26Z - 2022-04-14T10:08:44Z   2022-06-21T11:29:12Z - 2022-06-21T11:35:19Z

 

Here is the content of backups and chunks metadata:

 

Environment

None

Attachments

4
  • 21 Jun 2022, 03:17 PM
  • 21 Jun 2022, 03:17 PM
  • 21 Jun 2022, 03:15 PM
  • 21 Jun 2022, 03:15 PM

Smart Checklist

Activity

andrew.pogrebnoi June 21, 2022 at 3:16 PM

Another strange case:

Snapshots:     2022-06-21T14:35:53Z 230.96KB <logical> [complete: 2022-06-21T14:36:03Z]   PITR chunks [259.06KB]:     2022-06-21T14:36:04Z - 2022-06-21T14:59:28Z     2022-06-21T14:36:03Z - 2022-06-21T14:36:03Z (no base snapshot)

The second for the first range is skipped. But it became a separate range!

Done

Details

Assignee

Reporter

Needs Review

Yes

Needs QA

Yes

Fix versions

Affects versions

Priority

Smart Checklist

Created June 21, 2022 at 2:09 PM
Updated March 5, 2024 at 6:52 PM
Resolved July 12, 2022 at 9:29 AM

Flag notifications