@user121216 opened this Pull Request on February 7th 2019 Contributor

We got some performance issues with that task. Our MySQL replication needs 1-2 hours to catch up the master.

@sgiehl commented on February 7th 2019 Member

@user121216 thanks for the PR. would you mind resolving the conflicts?

@tsteur commented on February 7th 2019 Member

@user121216 cheers for the suggestion, really appreciated. In the last release / config we've already added a feature to do this: delete_logs_unused_actions_schedule_lowest_interval

Just set it to a really high value and it won't be executed.

Let me know if this doesn't work for you.

@user121216 commented on February 8th 2019 Contributor

Sorry, my fault. I thought, I forked the latest version, but I've already had forked years ago.
I will try delete_logs_unused_actions_schedule_lowest_interval. Thanks for the hint!

This Pull Request was closed on February 7th 2019
Powered by GitHub Issue Mirror