pecl:mysqlnd_ms
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
pecl:mysqlnd_ms [2012/04/17 11:48] – [Raw Bin ideas (RFCs)] uw | pecl:mysqlnd_ms [2012/04/17 12:01] – [Raw Bin ideas (RFCs)] uw | ||
---|---|---|---|
Line 383: | Line 383: | ||
== Problem to solve / Idea == | == 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. The load shall be optionally reduced with tweaking settings. | + | 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 == | == 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