global.wsrep_causal_reads no longer honored

fixed in
5.5: http://bazaar.launchpad.net/~codership/codership-mysql/wsrep-5.5/revision/4021
5.6: http://bazaar.launchpad.net/~codership/codership-mysql/5.6/revision/4132

The bug is about session's wsrep_sync_wait value not inheriting the global value of wsrep_causal_reads during session initialization. The patch (#1) however, updates the global values on SET which IMO is redundant.

As description of 'wsrep_causal_reads' said: "(DEPRECATED) setting this variable is equivalent to setting wsrep_sync_wait READ flag". So we not only have to update session 'wsrep_sync_wait' if we update session 'wsrep_causal_reads', we have to do it to global variables too. And vice versa.

if we don't update global values, it will bring inconsistency and introduce confusion to users. For example, if we don't update global values, there would be scenario:
- global wsrep_causal_reads = 1
- global wsrep_sync_wait = 6
from wsrep_causal_reads, we DO expect causality check on READ stmt. However from wsrep_sync_wait, we DO NOT expect causality check on READ stmt.

Ok. That justifies the patch.

Now consider this :

* Start a node with --wsrep_causal_reads=ON
* Check wsrep_sync_wait's value :

MariaDB [test]> select @@wsrep_causal_reads;
+----------------------+
| @@wsrep_causal_reads |
+----------------------+
| 1 |
+----------------------+
1 row in set (0.00 sec)

MariaDB [test]> select @@wsrep_sync_wait;
+-------------------+
| @@wsrep_sync_wait |
+-------------------+
| 0 | <------- should have been 1
+-------------------+
1 row in set (0.00 sec)

oh. I have never thought that situation. Then your patch is also needed. I'll fix that. thank you.

fixed in
5.5: http://bazaar.launchpad.net/~codership/codership-mysql/wsrep-5.5/revision/4022
5.6: http://bazaar.launchpad.net/~codership/codership-mysql/5.6/revision/4133

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1721