# \[Note\] WSREP: Skipping empty log\_xid: COMMIT

**URL:** <https://forums.percona.com/t/note-wsrep-skipping-empty-log-xid-commit/2428>\
**Category:** Percona XtraDB Cluster 5.x\
**Created:** [May 27, 2012, 8:14am UTC](https://forums.percona.com/t/note-wsrep-skipping-empty-log-xid-commit/2428 "2012-05-27T08:14:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ywliu](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ywliu/32/8897_2.png) [@ywliu](https://forums.percona.com/u/ywliu)\
**Post date:** [May 27, 2012, 8:14am UTC](https://forums.percona.com/t/note-wsrep-skipping-empty-log-xid-commit/2428/1 "2012-05-27T08:14:40Z")

</div>

Hi,

As I was running sysbench 0.5 against Percona XtraDB cluster, I saw many entries like this in the server log:

[Note] WSREP: Skipping empty log\_xid: COMMIT

I am very new to Galera replication. I wonder what this message means here, though it looks harmless.

Yen-Wei Liu

---

<div class="post-metadata">

**Author:** ![seppo](https://avatars.discourse-cdn.com/v4/letter/s/35a633/32.png) [@seppo](https://forums.percona.com/u/seppo)\
**Post date:** [May 28, 2012, 12:42pm UTC](https://forums.percona.com/t/note-wsrep-skipping-empty-log-xid-commit/2428/2 "2012-05-28T12:42:10Z")

</div>

This should be debug level message. Check what you have set for wsrep\_debug variable. To avoid debug level messages, set in my.cnf:

wsrep\_debug=0

-seppo