Skip to content

Fix startup recovery to restore databases as system metadata#3807

Merged
DavIvek merged 10 commits intomasterfrom
fix-mt-recovery
Feb 20, 2026
Merged

Fix startup recovery to restore databases as system metadata#3807
DavIvek merged 10 commits intomasterfrom
fix-mt-recovery

Conversation

@DavIvek
Copy link
Contributor

@DavIvek DavIvek commented Feb 18, 2026

Currently, when --data-recovery-on-startup is enabled, we recover users but not databases. Since both are system metadata rather than user data, we should recover both. However, actual user data should not be recovered.

@DavIvek DavIvek added this to the mg-v3.9.0 milestone Feb 18, 2026
@DavIvek DavIvek self-assigned this Feb 18, 2026
@DavIvek DavIvek added bug bug Docs - changelog only Docs - changelog only CI -build=debug -test=core Run debug build and core tests on push CI -build=release -test=core Run release build and core tests on push CI -build=release -test=e2e Run release build and e2e tests on push labels Feb 18, 2026
@DavIvek
Copy link
Contributor Author

DavIvek commented Feb 18, 2026 •
edited
Loading

Tracking

  • [Link to Epic/Issue]

Standard development

CI Testing Labels

  • Select the appropriate CI test labels (CI -build=build-name -test=test-suite)

Documentation checklist

  • Add the documentation label
  • Add the bug / feature label
  • Add the milestone for which this feature is intended
    • If not known, set for a later milestone
  • Write a release note, including added/changed clauses
    • When --data-recovery-on-startup is enabled, the system now recovers both users and databases, whereas previously only users were recovered. This ensures that all system metadata is restored consistently on startup, while actual user data is still not recovered. #3807
  • [ Documentation PR link memgraph/documentation#XXXX ]
    • Is back linked to this development PR

@DavIvek DavIvek marked this pull request as ready for review February 18, 2026 11:42
as51340
as51340 requested changes Feb 19, 2026
View reviewed changes
andrejtonev
andrejtonev approved these changes Feb 19, 2026
View reviewed changes
Copy link
Contributor

@andrejtonev andrejtonev left a comment

Choose a reason for hiding this comment

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

nice and simple

@DavIvek DavIvek requested a review from as51340 February 20, 2026 09:35
@DavIvek DavIvek enabled auto-merge February 20, 2026 11:03
@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 20, 2026

Quality Gate Passed Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@DavIvek DavIvek added this pull request to the merge queue Feb 20, 2026
Merged via the queue into master with commit 417fcd1 Feb 20, 2026
40 checks passed
@DavIvek DavIvek deleted the fix-mt-recovery branch February 20, 2026 15:55
@gitbuda gitbuda mentioned this pull request Mar 11, 2026
Open
61 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@andrejtonev andrejtonev andrejtonev approved these changes

@as51340 as51340 as51340 approved these changes

Assignees

@DavIvek DavIvek

Labels

bug bug CI -build=debug -test=core Run debug build and core tests on push CI -build=release -test=core Run release build and core tests on push CI -build=release -test=e2e Run release build and e2e tests on push Docs - changelog only Docs - changelog only

Projects

None yet

Milestone

mg-v3.9.0

Development

Successfully merging this pull request may close these issues.

3 participants

@DavIvek @andrejtonev @as51340