Issues
- During physical restore, PBM Agents fails to write last seen cluster timePBM-1379Resolved issue: PBM-1379Dmytro Zghoba
- PBM unable to start backup due to 'context deadline exceeded' errorPBM-1377Resolved issue: PBM-1377Dmytro Zghoba
- Add support for SSE-S3 for S3 providersPBM-1376Resolved issue: PBM-1376Sandra Romanchenko
- Block logical restore of sharded timeseries collectionsPBM-1367Resolved issue: PBM-1367Dmytro Zghoba
- Release notes 2.6.0PBM-1363Resolved issue: PBM-1363Anastasia Alexandrova
- Leftover backup lock after successful physical restorePBM-1360Resolved issue: PBM-1360Dmytro Zghoba
- pbm profile add should fail if pbm-agents doesn't have permissions to specified storagePBM-1353Resolved issue: PBM-1353Dmytro Zghoba
- Impossible to start PITR in case there are old oplogs on the storagePBM-1344Resolved issue: PBM-1344Dmytro Zghoba
- Occasionally pbm-agent is locked out of starting the slicerPBM-1343Resolved issue: PBM-1343Boris Ilijic
- Physical restore fails with "there was an index build in progress"PBM-1341Resolved issue: PBM-1341Dmytro Zghoba
- Physical backup is not completely removed from the storage after executing pbm delete-backup or pbm cleanupPBM-1332Resolved issue: PBM-1332Dmytro Zghoba
- Filesystem storage writes should write, fsync and renamePBM-1329Resolved issue: PBM-1329Dmytro Zghoba
- PITR generation does not resume following agent restart during backupPBM-1326Resolved issue: PBM-1326Boris Ilijic
- Reporting actual priority with pbm statusPBM-1323Resolved issue: PBM-1323
- "node in not suitable for restore" message is confusingPBM-1320Resolved issue: PBM-1320Ivan Groenewold
- The backup cannot be taken from the primary node if even it has the highest priority in PBMPBM-1319Resolved issue: PBM-1319Boris Ilijic
- uploadPartSize, maxUploadParts not printed in logPBM-1318Resolved issue: PBM-1318Dmytro Zghoba
- Hardcoded timeout for resync and delete operations in PBM cli codePBM-1303Resolved issue: PBM-1303Dmytro Zghoba
- Node Priority Control in the Oplog Slicing
PBM-1300Resolved issue: PBM-1300radoslaw.szulgo - Multiple storage configuration for backupsPBM-1271Resolved issue: PBM-1271Dmytro Zghoba
- logical PBM issue archive parser: corruption found in archive; ParserConsumer.BodyBSON()PBM-1239Resolved issue: PBM-1239Dmytro Zghoba
- Support multiple storagesPBM-1228Resolved issue: PBM-1228Dmytro Zghoba
- PBM SDK: list agent statusesPBM-1224Resolved issue: PBM-1224Dmytro Zghoba
- Backup hangs after pbm-agent is restartedPBM-1208Resolved issue: PBM-1208Boris Ilijic
- When installed PBM, pbm-agent URI is setting different as compared to the docPBM-1190Resolved issue: PBM-1190Sandra Romanchenko
- Take node priority into account for oplog slicingPBM-940Resolved issue: PBM-940
- pbm pitr.oplogOnly backup set the priorityPBM-920Resolved issue: PBM-920
- Show nodes prioritiesPBM-901Resolved issue: PBM-901Boris Ilijic
- PITR slicing eventually could end up on primary nodePBM-557Resolved issue: PBM-557Boris Ilijic
- invalid remote store url in text output when starting backupPBM-341Resolved issue: PBM-341Dmytro Zghoba
30 of 30
During physical restore, PBM Agents fails to write last seen cluster time
Done
General
Escalation
General
Escalation
Description
Environment
None
Details
Assignee
Dmytro ZghobaDmytro ZghobaReporter
Dmytro ZghobaDmytro ZghobaLabels
Needs Review
YesNeeds QA
YesComponents
Sprint
NoneFix versions
Priority
Medium
Details
Details
Assignee
Dmytro Zghoba
Dmytro Zghoba
Reporter
Dmytro Zghoba
Dmytro ZghobaLabels
Needs Review
Yes
Needs QA
Yes
Components
Sprint
None
Fix versions
Priority
MediumSmart Checklist
Smart Checklist
Smart Checklist
Created August 19, 2024 at 11:47 AM
Updated March 24, 2025 at 10:57 AM
Resolved August 27, 2024 at 12:25 PM
Activity
Show:
Error example:
The
cluster.donecontains the last seen cluster time by any agents. In this example, two agents tried to write their timestamps concurrently (only a last/later is ok). It is specific to the FS storage type.introduced two-phase write for filesystem storage: (1) write to a temporary file (has
.tmpending) and then (2) move/rename the tmp file to target one. It happens that two agents write to the same tmp filecluster.done.tmpat the same time but one agent made the second phase while another failed (no such file).This error does not affect a restore process but generates error messages in the log.
The same problem could affect PBM CLI with error like: