1
0
Fork 0
mirror of https://we.phorge.it/source/phorge.git synced 2024-11-19 05:12:41 +01:00

Fix a bad link in the database partitioning docs

Summary: Fixes T11959. Also, minor wordsmithing.

Test Plan: Read vv carefully.

Reviewers: chad

Reviewed By: chad

Maniphest Tasks: T11959

Differential Revision: https://secure.phabricator.com/D17007
This commit is contained in:
epriestley 2016-12-07 12:29:37 -08:00
parent 0dfe665539
commit e8d9c676b1

View file

@ -6,8 +6,6 @@ Guide to partitioning Phabricator applications across multiple database hosts.
Overview
========
WARNING: Partitioning is a prototype.
You can partition Phabricator's applications across multiple databases. For
example, you can move an application like Files or Maniphest to a dedicated
database host.
@ -19,17 +17,18 @@ The advantages of doing this are:
- you can match application workloads to hardware or configuration to make
operating the cluster easier.
This configuration is complex, and very few installs need to pursue it.
Phabricator will normally run comfortably with a single database master even
for large organizations.
This configuration is complex, and very few installs will benefit from pursuing
it. Phabricator will normally run comfortably with a single database master
even for large organizations.
Partitioning generally does not do much to increase resiliance or make it
easier to recover from disasters, and is primarily a mechanism for scaling.
easier to recover from disasters, and is primarily a mechanism for scaling and
operational convenience.
If you are considering partitioning, you likely want to configure replication
with a single master first. Even if you choose not to deploy replication, you
should review and understand how replication works before you partition. For
details, see @{Cluster:Databases}.
details, see @{article:Cluster: Databases}.
Databases also support some advanced configuration options. Briefly: