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
F15537900: D20743.id49458.diff
Thu, Apr 24, 4:28 PM
F15525147: D20743.id49459.diff
Mon, Apr 21, 12:28 PM
F15524247: D20743.diff
Mon, Apr 21, 6:51 AM
F15458739: D20743.id49459.diff
Mon, Mar 31, 6:37 AM
F15440114: D20743.id.diff
Wed, Mar 26, 11:02 AM
F15431712: D20743.diff
Mar 24 2025, 2:03 PM
F15367333: D20743.diff
Mar 11 2025, 5:26 PM
F15332791: D20743.id49458.diff
Mar 7 2025, 8:22 PM
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.