sar-sql DB information is replicated to slaves

Bug #497873 reported by Tom Krouper on 2009-12-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nominated for Trunk by Sheeri K. Cabral

Bug Description

When sar-sql runs, the information is written to the binary log. This could contaminate a replica, especially if you are monitoring both machines. I think sar-sql should either SET SQL_LOG_BIN=0 before inserting into the DB, or have an option to turn it on/off.

Related branches

seattlegaucho (gnarvaja) wrote :

This is not a bug. All rows include the 'server-id' as part of the primary key. This feature makes it possible to query the slave for differences between its master and its own values.

However, I tagged it as 'wishlist' since it should be possible to have an option to avoid replication if desired. Using "set sql_log_bin=0" is the right way of doing it if the flag is set.

I might choose to leave it pending until I do the major command line options overhaul I have in mind, otherwise the command line might get too complex.

Changed in mysar:
status: New → Confirmed
importance: Undecided → Wishlist
assignee: nobody → seattlegaucho (gnarvaja)
seattlegaucho (gnarvaja) on 2009-12-28
tags: added: replication
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers