sigmasternchen/php-doc-en
1
0
Fork 0
mirror of https://github.com/sigmasternchen/php-doc-en synced 2025-03-16 00:48:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Give hints on deployment

Browse source 
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@321155 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Ulf Wendel 2011-12-19 09:55:46 +00:00
parent db51b7f117
commit fb7d79a129
1 changed files with 18 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
reference/mysqlnd_ms/setup.xml
View file

@ -8,6 +8,7 @@
&reftitle.required;
<para>
<literal>PHP 5.3.6</literal> or newer.
Some advanced functionality requires <literal>PHP 5.4.0</literal> or newer.
</para>
<para>
The <literal>mysqlnd_ms</literal> replication and load balancing
@ -40,10 +41,20 @@
the MySQL replication slave servers, the server pick (load balancing) policy,
the failover strategy, and the use of lazy connections.
</para>
<para>
The plugin loads its configuration file at the beginning of a web request.
It is then cached in memory and used for the duration of the web request.
This way, there is no need to restart PHP after deploying the configuration
file. Configuration file changes will become active almost instantly.
</para>
<para>
The PHP configuration directive
<link linkend="ini.mysqlnd-ms.ini-file"><literal>mysqlnd_ms.ini_file</literal></link>
is used to set the plugins configuration file.
is used to set the plugins configuration file. Please note, that
the PHP configuration directive may not be evaluated for every web request.
Therefore, changing the plugins configuration file name or location may
require a PHP restart. However, no restart is required to read changes if
an already existing plugin configuration file is updated.
</para>
<para>
Using and parsing <acronym>JSON</acronym> is efficient, and using <acronym>JSON</acronym>
@ -200,8 +211,12 @@ $mysqli = new mysqli("localhost", "username", "password", "database");
and a list of slave servers. The master list is configured with the keyword
<literal>master</literal>, while the slave list is configured with the
<literal>slave</literal> keyword. Failing to provide a slave list will result
in a fatal <constant>E_WRROR</constant> level error, although a slave list
may be empty.
in a fatal <constant>E_ERROR</constant> level error, although a slave list
may be empty. It is possible to allow no slaves. However, this is only recommended
with synchronous clusters, please see also
<link linkend="mysqlnd-ms.supportedclusters">supported clusters</link>.
The main part of the documentation focusses on the use
of aynchronous MySQL replication clusters.
</para>
<para>
The master and slave server lists can be optionally indexed by symbolic