From 18e80b781b346c87aa6bba345c6240f9ee9b2997 Mon Sep 17 00:00:00 2001 From: Ulf Wendel Date: Tue, 15 May 2012 14:46:10 +0000 Subject: [PATCH] 1.4 development tree changes. git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@325700 c90b9560-bf6c-de11-be94-00142212c4b1 --- reference/mysqlnd_ms/changes.xml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/reference/mysqlnd_ms/changes.xml b/reference/mysqlnd_ms/changes.xml index 74f86e0bdd..a40fbb82e8 100644 --- a/reference/mysqlnd_ms/changes.xml +++ b/reference/mysqlnd_ms/changes.xml @@ -58,6 +58,33 @@ is opened. This is most useful when using lazy connections, which are a default. + + + Introduced wait_for_gtid_timeout setting to throttle + slave reads that need session consistency. 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 wait_for_gtid_timeout instructs the plugin + to poll a slaves status for wait_for_gtid_timeout seconds + if the first execution of the SQL statement has shown 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 master stategy existed to failover to a master if + a slave connection fails. loop_before_master is + similar but tries all other slaves before attempting to connect to the master + if a slave connection fails. The number of attempts can be limited using + the max_retries option. + +