Manual:External storage

External storage is an abstraction for storing the wiki's content (ie. what would normally go into the text table) outside the normal database, possibly with some kind of compression applied. Some extensions (such as StructuredDiscussions) can use external storage directly for storing other kinds of data.

The contents of external storage are addressed with an URL, with the protocol determining what type of storage should be used. Pre-1.32 these URLs were stored in the  field of the text table, with   set to external ; since 1.32 they are stored in the   field of the content table.

Code
The main class for interacting with external storage is.

Configuration
An example  setup:


 * The Manual:$wgExternalStores line states that a  external store can be used. (The   part is not an arbitrary name that can be adjusted. It has to be  .) This corresponds to the   subclass used, and the protocol of the blob address.
 * The Manual:$wgExternalServers line states all the usable clusters with all usable nodes of a cluster. The top-level array's keys denote a cluster's name (The above example defines only one cluster. It has the name ). The value to those keys are again arrays. They hold the specifications of the individual nodes. The first node is consider the master. All writes to the database are performed through this master node. Zero or more slave nodes may follow. (In the above example, you find two slave nodes). Each node may have its own ,  ,  ,  , and  , as shown in the example. The   parameter allows to specify how much of the load should pass through this note.
 * The Manual:$wgDefaultExternalStore line holds those external stores that may be used for storage of new text. If you omit this line, the external store will be read-only and new texts will go into the default database (i.e.: the same database holding page, revision, image data; not the cluster).

For a multi-master wiki farm setup (like Wikimedia), consider using LBFactory_Multi instead.

Database setup
For the above configuration example, you would have to:
 * 1) Create the database   on the host
 * 2) Run the   SQL-script on the on the database   on the host  . Do not use   for this task, as it will add the required tables to your default database (i.e.: the database holding page, revision, image data) and not to  . If you are not sure how to run the SQL-script on the database   on the host , please consult your database documentation.
 * 3) Set up replication (consult your database's documentation on how to set up replication) towards   on the host , and
 * 4) Set up replication towards   on the host.

Maintenance scripts
There are several maintenance scripts for moving content to the external store:
 * moveToExternal.php - move old revisions to external storage
 * compressOld.php - compress old revisions and potentially move them to external storage
 * recompressTracked.php - move revisions (or other data) from one external storage to another and recompress them in the process