revi-archive/phorge-phorge
1
0
Fork 0
mirror of https://we.phorge.it/source/phorge.git synced 2025-04-10 03:18:41 +02:00
Code Issues Releases Wiki Activity

Fix a bad link in the database partitioning docs

Browse source 
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
1 changed files with 6 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
src/docs/user/cluster/cluster_partitioning.diviner
View file

@ -6,8 +6,6 @@ Guide to partitioning Phabricator applications across multiple database hosts.
Overview Overview
======== ========
WARNING: Partitioning is a prototype.
You can partition Phabricator's applications across multiple databases. For You can partition Phabricator's applications across multiple databases. For
example, you can move an application like Files or Maniphest to a dedicated example, you can move an application like Files or Maniphest to a dedicated
database host. database host.
@ -19,17 +17,18 @@ The advantages of doing this are:
- you can match application workloads to hardware or configuration to make - you can match application workloads to hardware or configuration to make
operating the cluster easier. operating the cluster easier.
This configuration is complex, and very few installs need to pursue it. This configuration is complex, and very few installs will benefit from pursuing
Phabricator will normally run comfortably with a single database master even it. Phabricator will normally run comfortably with a single database master
for large organizations. even for large organizations.
Partitioning generally does not do much to increase resiliance or make it 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 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 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 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: Databases also support some advanced configuration options. Briefly: