Idea Details

Logging MW updates

Last activity 2 days ago
RSros's profile image
07-06-2016 04:37 PM

Would like to propose that the MW updates be removed from the query log file and entered into either the update log or their own replication log file. Reason being is that the query logs and possibly update logs can get quite large (no matter that they can be rolled over according to number of lines) and having MW updates in their own log file would be a lot easier for analysis.  Rackspace has a rather large global directory environment with a lot of traffic, so optimally the MW updates would be better in their own log file, but would accept them in the update log file if necessary.

 

Thanks very much

Robert M Rossiter

Rackspace Hosting

Data Analyst III


Comments

07-27-2016 08:14 PM

Thanks Rob,

I will raise this as a backlog item for review.

I think it would be best to move these updates into a separate log. The update-log should be reserved for mastered updates. Some customers use this to replay updates to sync external systems.

As per the suggestion above, we should provide an option to ignore updates relating to replication and recovery from the query-log.

Thanks,

Justin

07-19-2016 08:02 AM

Making this a configurable option, with the default set to the current location of the query log, would be a great improvement.