Skip to content

PBM 1763 pitr fails with document validation failure - #401

Open
rasika-chivate wants to merge 9 commits into
mainfrom
PBM-1763-PITR-fails-with-DocumentValidationFailure-
Open

rasika-chivate wants to merge 9 commits into
mainfrom
PBM-1763-PITR-fails-with-DocumentValidationFailure-

Conversation

@rasika-chivate

@rasika-chivate rasika-chivate commented Sep 29, 2026 •

Copy link
Copy Markdown
Collaborator

Documents the TTL limitation for logical restores, including PITR, of time series collections configured with expireAfterSeconds. Manually disable the TTL monitor before starting the restore and keep it disabled for the duration of the restore. Record each data-bearing mongod instance's original setting and restore it when the operation ends, even if it fails.

Updated docs/features/known-limitations.md, under Logical restores of time series collections with expiration. The existing page TOC includes this heading; no navigation changes are needed.

Sources:

Validation: MkDocs build and git diff --check passed. Verified the rendered page TOC, warning, command blocks and upstream link attributes. Existing unrelated link warnings remain.

@rasika-chivate
rasika-chivate marked this pull request as draft September 29, 2026 08:05
@rasika-chivate
rasika-chivate requested a balanced review from Copilot September 29, 2026 08:05
@rasika-chivate rasika-chivate changed the title Pbm 1763 pitr fails with document validation failure PBM 1763 pitr fails with document validation failure Sep 29, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟡 Changes recommended

The workaround must clarify that the runtime parameter needs configuring on applicable mongod instances.

Review effort: Balanced
Findings: 1 Low severity

Open (1)
What changed in this PR

Documents a workaround for PITR failures involving expiring time-series collections.

Changes:

  • Explains the TTL monitor failure.
  • Advises disabling TTL monitoring during restoration.
File Description
docs/​features/​known-limitations.md Adds the limitation, error, and workaround.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread docs/features/known-limitations.md Outdated
Co-authored-by: rasika-chivate <95711051+rasika-chivate@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟢 Approval recommended

The guidance is complete; the remaining malformed link attribute is a minor documentation issue.

Review effort: Balanced
Findings: 1 Low severity

Open (1)
Resolved since last review (1)

Comment thread docs/features/known-limitations.md Outdated
…ttribute for ttlMonitorEnabled'

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Comment thread docs/features/known-limitations.md

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟢 Approval recommended

The documentation accurately and clearly covers the limitation and required workaround.

Review effort: Balanced
Findings: None

Resolved since last review (1)

Comment thread docs/features/known-limitations.md Outdated
(Location6781400) Time series bucket document is missing 'control' field
```

Before starting the restore, manually disable the TTL monitor on every data-bearing `mongod` instance in the target deployment. Keep it disabled for the duration of the restore. The [`ttlMonitorEnabled` :octicons-link-external-16:](https://www.mongodb.com/docs/v8.0/reference/parameters/#mongodb-parameter-param.ttlMonitorEnabled){:target="_blank"} parameter applies to individual instances, so configure each one separately:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should just disable it on the Primary instance on RS, or all Primary instances on every RS (config server + all shards) in sharded cluster.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🔵 Needs a closer look

The instructions omit secondary data-bearing nodes that may become primary during restoration.

Review effort: Balanced
Findings: None

This branch was successfully deployed

1 active deployment
PBM-1763-PITR-fails-with-DocumentValidationFailure- - pbm-docs-preview PR #401 — c3a7411f Deployed Oct 6, 2026 by nastena1606
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants