MySQL Forums :: Utilities :: Fabric LOG table not pruned

Advanced Search

Re: Fabric LOG table not pruned
Posted by: tsubasa tanaka ()
Date: December 05, 2016 07:21PM

There're 2 reasons I have faced same situation.

1. Backing-store's `event_scheduler` is not on. (prune_log will be started by event_scheduler)
- MySQL Bugs: #73206: MySQL Fabric should report a warning when MySQL Event Scheduler is disabled

2. prune_log event uses MAKETIME function but that arguments are terribly wrong...
- MySQL Bugs: #81557: MySQL Fabric uses wrong argument of MAKETIME in prune_log Event

Options: ReplyQuote

Subject Views Written By Posted
Fabric LOG table not pruned 487 Vincent Poore 12/05/2016 12:21PM
Re: Fabric LOG table not pruned 221 tsubasa tanaka 12/05/2016 07:21PM
Re: Fabric LOG table not pruned 277 Vincent Poore 12/05/2016 09:02PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.