Bloated Database Due To Log – Recommend NOT using until fixed!

  • Derek Rippe

    (@dwrippe)


    8 years, 7 months ago

    Discovered today that this plugin is maintaining life-long logs, in the database, of redirected pages and elements.

    These tables and entries in the database are making up, in many cases, over 75% of the database file size. I’ve already had one site go down due to “too many connections” to the database, which I believe was a direct cause of this plugin.

    By default I believe the plugin is supposed to be keeping logs for a week. But changing that setting seems to have no affect on what is dumping into the database.

    I had one 55MB database, of which 47MB were a result of this plugin.

    I had another database that was 26MB in size, 19MB were due to this plugin.

    If you are currently using this plugin, I highly recommend disabling and deleting it until this issue has been resolved.

    https://wordpress.org/plugins/redirection/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Derek Rippe

    (@dwrippe)

    8 years, 7 months ago

    For what it’s worth, it’s the “_redirection_404” table that bloats. I don’t fully understand how this plugin works, but it looks to be storing hits, possibly from everyone including crawlers, in this table. So I guess every time anything throws a 404, it logs the entry in a new row, resulting in a massive table.

    Deleting the 404 logs in the Dashboard obviously clears this out, but if you have hundreds of log pages, deleting these is tedious.

    It appears as if the “One Week” 404 log setting isn’t being held to by default (as I’ve never adjusted these, but they have all been set to One Week).

    With any luck this will make sense to the developer and a fix can be sorted.

    Thread Starter Derek Rippe

    (@dwrippe)

    8 years, 7 months ago

    My last post on this, as I’ve found a “workaround” for the sites we have that rely heavily on this plugin.

    The issue is indeed related to the logs being stored for longer than expected. Disabling logs on the Options page does not delete existing logs, but it does seem to prevent new logs from being created.

    If you’ve got any massive tables as a result of this plugin, you’re going to have to delete all the logs in the Dashboard, THEN disable the logs on the Options page. If you disable the logs first, you won’t be able to access the existing logs to delete the entries.

    Recommend a way to delete all logs with a single click!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Bloated Database Due To Log – Recommend NOT using until fixed!’ is closed to new replies.