Is BLACKHOLE support feasible?

Bug #1296718 reported by Jay Janssen
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Confirmed
Wishlist
Seppo Jaakola

Bug Description

Since BLACKHOLE's internal state doesn't change at all, does it matter if it does not support Galera and prioritized transaction? Is it feasible to support BLACKHOLE RBR intermixed with Innodb transactions in PXC?

Revision history for this message
Alex Yurchenko (ayurchen) wrote :

Uh, forgive my ignorance, what would be BLACKHOLE RBR? Some generic row representation?

Anyway, given that the only purpose of blackhole is to write event into binlog, it should not matter whether it is ROW or STATEMENT.

Revision history for this message
Jay Janssen (jay-janssen) wrote :

Well, I want it mixed in a trx with Innodb stuff -- can I mix binlog formats within a single transaction? No idea.

Changed in percona-xtradb-cluster:
assignee: nobody → Seppo Jaakola (seppo-jaakola)
status: New → In Progress
Revision history for this message
Seppo Jaakola (seppo-jaakola) wrote :

Blackhole engine cannot generate ROW events, as there are no rows in the table to play with.

However, it would be possible to generate STATEMENT format events (query_log_event) for blackhole writes, even though session would be configured for ROW format replication.

But, is this the wanted feature? And do blackhole transactions need to be replicated or just remain in master binlog file?

Changed in percona-xtradb-cluster:
status: In Progress → Confirmed
importance: Undecided → Wishlist
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.