Page MenuHomePhabricator

Straighten out replication/cache behavior in "bin/storage dump"
ClosedPublic

Authored by epriestley on Aug 28 2019, 3:19 PM.
Tags
None
Referenced Files
F18827335: D20743.diff
Fri, Oct 24, 9:25 AM
F18650076: D20743.diff
Sep 20 2025, 11:21 PM
F18638400: D20743.id49458.diff
Sep 17 2025, 10:22 AM
F18570549: D20743.id49459.diff
Sep 10 2025, 3:55 AM
F18570548: D20743.id49458.diff
Sep 10 2025, 3:55 AM
F18567329: D20743.id.diff
Sep 9 2025, 3:41 PM
F18277824: D20743.diff
Aug 22 2025, 8:27 PM
F18095864: D20743.id49459.diff
Aug 8 2025, 2:57 AM
Subscribers
None

Details

Summary

Fixes T13336.

  • Prevent --no-indexes from being combined with --for-replica, since combining these options can only lead to heartbreak.
  • In --for-replica mode, dump caches too. See discussion in T13336. It is probably "safe" to not dump these today, but fragile and not correct.
  • Mark the "MarkupCache" table as having "Cache" persistence, not "Data" persistence (no need to back it up, since it can be fully regenerated from other datasources).
Test Plan

Ran bin/storage dump with various combinations of flags.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.Aug 28 2019, 3:25 PM
This revision was automatically updated to reflect the committed changes.