Q1: What is the problem that you are trying to solve?
During our first Upgrade to V3 on one our pro test servers we noticed that our action_logs table had grown to over 16 Million entries which caused the Database Migration to hang at “V300AddActionLogsExtraIndex” for about 45 minutes.
Q2 - Who is impacted?
Anyone with large action_logs table
Q3 - Why is it important and/or urgent?
This was very confusing at first as all the other migration jobs took less then 10 seconds. We have now cut down the table manually but that isn’t a permanent solution.
Q4 - What is your proposed solution?
It would be great if there was some kind of log rotation so that the table doesn’t get this big again.