expose desync functionality to the client

Bug #1049599 reported by Alex Yurchenko on 2012-09-12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Vladislav Klyachin
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Fix Released

Bug Description

As seen at https://groups.google.com/d/msg/percona-discussion/-/fInV4T3hoTAJ : we already have desync functionality utilized in RSU. However it is not exposed to client explicitly, which may be useful in some situations. Exposing this functionality to client still preserves the HA properties of the cluster as opposed to using async master-slave replication.

Should be easy to do either via /*! WSREP_DESYNC */ comment on the query or SET GLOBAL wsrep_desync=1 variable.

Changed in codership-mysql:
importance: Undecided → Wishlist
milestone: none → 5.5.27-23.8
status: New → Confirmed
Changed in codership-mysql:
milestone: 5.5-24 → 5.5.32-23.7.6
Changed in codership-mysql:
assignee: nobody → Vladislav Klyachin (klyachin)
Changed in codership-mysql:
status: Confirmed → Fix Committed
Changed in percona-xtradb-cluster:
milestone: none → 5.5.33-23.7.6
Changed in percona-xtradb-cluster:
status: New → Fix Committed
Changed in codership-mysql:
status: Fix Committed → Fix Released
Changed in percona-xtradb-cluster:
status: Fix Committed → Fix Released

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers