FR: Plan to implement support for sql_log_bin in Percona Cluster
Bug #1695288 reported by
joffrey92
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
Hi,
I wonder if it is scheduled to backport the following patch inside PXC:
https:/
wsrep_on and sql_log_bin have almost same effect now, and I believe giving back sql_log_bin it's original effect is a good addition to the software.
My current use case would be to have an async slave, and purge data on the cluster, but not on the slave for archiving purposes.
Thanks in advance,
Joffrey
| Changed in percona-xtradb-cluster: | |
| importance: | Undecided → Wishlist |
Revision history for this message
| Przemek (pmalkowski) wrote | #1 |
| Changed in percona-xtradb-cluster: | |
| status: | New → Confirmed |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #2 |
To post a comment you must log in.
Hi Joffrey,
Thank you, I think it is valid request. As Galera replication does not need binary logs, it makes sense to split wsrep_on=off and sql_log_bin = off behavior, so that first one affects only Galera replication and second only binary logging.
However, it would be best if the same is done by upstream Galera library provider in order to keep compatibility - have you reported maybe the same request to the Coderhip team?