Page MenuHomePhabricator

Never sever non-cluster database; write more read-only documentation
ClosedPublic

Authored by epriestley on Apr 11 2016, 1:50 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Aug 7, 5:04 AM
Unknown Object (File)
Tue, Jul 26, 12:45 PM
Unknown Object (File)
Mon, Jul 18, 5:28 AM
Unknown Object (File)
Jun 30 2022, 10:03 AM
Unknown Object (File)
Jun 24 2022, 5:42 PM
Unknown Object (File)
Jun 16 2022, 8:08 PM
Unknown Object (File)
Jun 3 2022, 1:53 AM
Unknown Object (File)
May 28 2022, 10:52 PM
Subscribers
None

Details

Summary

Ref T4571. Write more of the missing documentation sections and clarify a few things.

Since the "replicating master" check needs a special permission, imposes a performance penalty, is probably very difficult to misconfigure, and likely not a big deal anyway, just drop the idea of trying to automatically detect + prevent it. We still show if it's an issue on the status page, provided we have permission to check.

When you don't have any cluster databases configured, never stop trying to connect to the default master database. We might want to do this eventually as load reduction, but just don't muddy the waters too much for now while things stabilize.

Test Plan
  • Tested functionality in cluster, non-cluster, and degraded-cluster modes.
  • Used status console to monitor a health check cycle.
  • Read docs.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Never sever non-cluster database; write more read-only documentation.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Apr 11 2016, 3:42 PM
This revision was automatically updated to reflect the committed changes.