Oracle 5.0 Reference Manual page 2674

• Introduced new default charset setting
connection is opened. This is most useful when using lazy connections, which are a default.
• Introduced
If global transaction identifier are used and the service level is set to session consistency, the plugin
tries to find up-to-date slaves. The slave status check is done by a SQL statement. If nothing else
is set, the slave status is checked only one can the search for more up-to-date slaves continues
immediately thereafter. Setting
status for
that the slave is not up-to-date yet. The poll will be done once per second. This way, the plugin will
wait for slaves to catch up and throttle the client.
• New failover strategy loop_before_master. By default the plugin does no failover. It is possible to
enable automatic failover if a connection attempt fails. Upto version 1.3 only
to failover to a master if a slave connection fails.
slaves before attempting to connect to the master if a slave connection fails.
The number of attempts can be limited using the
remembered and skipped in load balancing for the rest of the web request.
remember_failed
semantics may change in the future without prior notice.
20.7.6.9.3. PECL/mysqlnd_ms 1.3 series
Copyright 1997-2012 the PHP Documentation Group. [2230]
1.3.2-stable
• Release date: 04/2012
• Motto/theme: see 1.3.0-alpha
Bug fixes
• Fixed problem with multi-master where although in a transaction the queries to the master weren't
sticky and were spread all over the masters (RR). Still not sticky for Random. Random_once is not
affected.
1.3.1-beta
• Release date: 04/2012
• Motto/theme: see 1.3.0-alpha
Bug fixes
• Fixed problem with building together with QC.
1.3.0-alpha
• Release date: 04/2012
• Motto/theme: Query caching through quality-of-service concept
The 1.3 series aims to improve the performance of applications and the overall load of an
asynchronous MySQL cluster, for example, a MySQL cluster using MySQL Replication. This is done by
transparently replacing a slave access with a local cache access, if the application allows it by setting
an appropriate quality of service flag. When using MySQL replication a slave can serve stale data. An
application using MySQL replication must continue to work correctly with stale data. Given that the
application is know to work correctly with stale data, the slave access can transparently be replace with
a local cache access.
Mysqlnd replication and load balancing plugin (mysqlnd_ms)
wait_for_gtid_timeout
wait_for_gtid_timeout
wait_for_gtid_timeout
are considered experimental although decent stability is given. Syntax and
to allow proper escaping before a
server_charset
setting to throttle slave reads that need session consistency.
instructs the plugin to poll a slaves
seconds if the first execution of the SQL statement has shown
loop_before_master
max_retries
2654
strategy existed
master
is similar but tries all other
option. Failed hosts can be
max_retries
and