pecl:mysqlnd_ms
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
pecl:mysqlnd_ms [2012/04/17 10:46] – [Development steps (release planning)] uw | pecl:mysqlnd_ms [2012/04/17 12:06] – [Development steps (release planning)] uw | ||
---|---|---|---|
Line 164: | Line 164: | ||
* NOTE: this may require refactoring of four filters. | * NOTE: this may require refactoring of four filters. | ||
* [open] Automatic on-connect fail over, if activated, shall be done in a loop until a connection can be opened. Currently we stop after the first attempt. If automatic fail over is on, we try " | * [open] Automatic on-connect fail over, if activated, shall be done in a loop until a connection can be opened. Currently we stop after the first attempt. If automatic fail over is on, we try " | ||
+ | * [open] Remember failed hosts for the duration of a web request (the plugins' | ||
* [open] Support directing statements manually to a group of nodes for more efficient server cache usage | * [open] Support directing statements manually to a group of nodes for more efficient server cache usage | ||
* [open] Refine QoS session consistency server selection policy | * [open] Refine QoS session consistency server selection policy | ||
* [open] Support "wait for GTID". Currently we loop over all servers until we find a matching one. MySQL 5.6 allows SQL users either to fetch the latest GTID or SQL users can ask for a GTID and their request will block until the GTID has been replicated on the server. We should support the latter logic as well. | * [open] Support "wait for GTID". Currently we loop over all servers until we find a matching one. MySQL 5.6 allows SQL users either to fetch the latest GTID or SQL users can ask for a GTID and their request will block until the GTID has been replicated on the server. We should support the latter logic as well. | ||
+ | * [open] Remember the most current server and test this one first when searching for a GTID (a synchronous server). Use of cached information is possible for the duration of a read-only request sequence. The cache must be flushed and refreshed for every write. | ||
* [open] Improve load balancing | * [open] Improve load balancing | ||
Line 218: | Line 220: | ||
== Problem to solve / Idea == | == Problem to solve / Idea == | ||
- | MySQL replication is asnychronous. Slaves are //eventual consistent// | + | MySQL replication is asynchronous. Slaves are //eventual consistent// |
MySQL replication used for read scale-out requires applications to be able to cope with stale data. If stale data is acceptable, a replication system may replace a MySQL slave read access with an access to a local, eventually stale, cache. **The cache access will lower network latency resulting in faster reply to the query. Furthermore, | MySQL replication used for read scale-out requires applications to be able to cope with stale data. If stale data is acceptable, a replication system may replace a MySQL slave read access with an access to a local, eventually stale, cache. **The cache access will lower network latency resulting in faster reply to the query. Furthermore, | ||
Line 377: | Line 379: | ||
For every node in the configuration users shall be able to set one or more group names. A SQL hint, for example, MS_GROUP=name can be used to hint the load balancer to direct a request to a certain node group. | For every node in the configuration users shall be able to set one or more group names. A SQL hint, for example, MS_GROUP=name can be used to hint the load balancer to direct a request to a certain node group. | ||
+ | |||
+ | === Refine QoS session consistency server selection policy === | ||
+ | |||
+ | == Problem to solve / Idea == | ||
+ | |||
+ | Users can request session consistency. Session consistency guarantees that a user will only be redirected to nodes that have already replicated his changes. Currently we check the status of all configured nodes before we pick a node for statement execution. Checking the status causes extra load on the nodes. | ||
+ | |||
+ | == Feature description == | ||
+ | |||
+ | Two additional ways for finding candidates help lowering the overhead: | ||
+ | |||
+ | * Wait for GTID | ||
+ | * Cache/ | ||
+ | |||
+ | There are two ways to check in MySQL 5.6 if a server has replicated a GTID. One can ask a node whether a GTID has been replicated and either get an immediate response (yes/no) or delay the reply until the node has replicated the GTID (wait for GTID). Currently only the first logic is used. We shall also support "wait for GTID". In that case we pick a candidate and wait until the candidate has replicated the GTID. This will lower the checking overhead as only one node is checked but not all configured nodes. | ||
+ | |||
+ | Furthermore we can persist GTID/ | ||
pecl/mysqlnd_ms.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1