# Does Percona XtraDB Cluster use binlog\_checksum, and can it be safely set to NONE?

**URL:** <https://forums.percona.com/t/does-percona-xtradb-cluster-use-binlog-checksum-and-can-it-be-safely-set-to-none/38643>\
**Category:** Percona XtraDB Cluster\
**Created:** [July 11, 2025, 10:06am UTC](https://forums.percona.com/t/does-percona-xtradb-cluster-use-binlog-checksum-and-can-it-be-safely-set-to-none/38643 "2025-07-11T10:06:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![JuanMag](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/juanmag/32/20721_2.png) [@JuanMag](https://forums.percona.com/u/JuanMag)\
**Post date:** [July 11, 2025, 10:06am UTC](https://forums.percona.com/t/does-percona-xtradb-cluster-use-binlog-checksum-and-can-it-be-safely-set-to-none/38643/1 "2025-07-11T10:06:03Z")

</div>

Hello,

I have a doubt regarding `binlog_checksum` in Percona XtraDB Cluster (PXC 8.0.40).

By default, Percona (like standard MySQL) uses `binlog_checksum=CRC32`. My questions are:

1. Does Percona XtraDB Cluster explicitly rely on the `binlog_checksum` setting for replication or internal consistency checks?
2. Is it safe or recommended to change `binlog_checksum` to `NONE` on just one node of the cluster, or must this setting be uniform across all nodes?
3. Could setting `binlog_checksum=NONE` cause replication issues or data inconsistency within the cluster?

I’d appreciate any guidance or best practices on managing the `binlog_checksum` setting within a Percona XtraDB Cluster.

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![niljoshi](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/niljoshi/32/16889_2.png) [@niljoshi](https://forums.percona.com/u/niljoshi)\
**Post date:** [July 11, 2025, 2:16pm UTC](https://forums.percona.com/t/does-percona-xtradb-cluster-use-binlog-checksum-and-can-it-be-safely-set-to-none/38643/2 "2025-07-11T14:16:44Z")

</div>

Hi,  
Please find my answers inline.

> 1. Does Percona XtraDB Cluster explicitly rely on the `binlog_checksum` setting for replication or internal consistency checks?

Percona XtraDB Cluster uses Galera synchronous replication, which operates differently from standard MySQL asynchronous replication that relies on the binary log. Galera replicates **writesets** (logical transactions), not binary log events.

binlog\_checksum controls whether checksums are written in the binary log. It is mostly relevant for asynchronous replication (e.g., master-slave replication using binlogs).  
In PXC, unless you are also using asynchronous replication (async slave) in parallel with Galera (so-called hybrid replication), the binlog\_checksum setting is effectively unused for the core Galera replication.

> 1. Is it safe or recommended to change `binlog_checksum` to `NONE` on just one node of the cluster, or must this setting be uniform across all nodes?

As explained above, if you are not using asynchronous replication anywhere with Galera, it doesn’t matter you are setting it NONE for one node or all. But it’s better to keep uniformity across the cluster.

> 1. Could setting binlog\_checksum=NONE cause replication issues or data inconsistency within the cluster?

This is covered in the above reply.

---

<div class="post-metadata">

**Author:** ![JuanMag](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/juanmag/32/20721_2.png) [@JuanMag](https://forums.percona.com/u/JuanMag)\
**Post date:** [July 14, 2025, 8:13am UTC](https://forums.percona.com/t/does-percona-xtradb-cluster-use-binlog-checksum-and-can-it-be-safely-set-to-none/38643/3 "2025-07-14T08:13:31Z")

</div>

Perfect  
Thank you very much!
