Help me please! cache_form table not cleared after running cron!

Comments

eric_a’s picture

eric_a commented

Every single form build takes 6 hours to expire. If your site has many forms and many, many hits, you will have many form builds and this cache bin will grow. Do you have any evidence that cache_form entries are never cleared at cron time, while entries from other tables do?

grendzy’s picture

grendzy commented
Category: bug » support
Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)
tr’s picture

tr commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

I cannot reproduce this in Drupal 6 or Drupal 7. Each row in the cache_form table has an expiration time. When cron runs, any row past its expiration time will be deleted. Like Eric_A said, it takes about 6 hours for a row to expire. If there are no expired rows, cron will not appear to do anything. The cache_form table is never cleared completely by cron - only the expired rows are cleared.

tr’s picture

tr commented

Double post.

giorgosk’s picture

giorgosk
Location Chios, Greece 🇬🇷
commented

big database tables might need optimizing to get rid of overhead
I would give http://drupal.org/project/db_maintenance a try

giorgio79’s picture

giorgio79 commented

#1506196: cache_form is never cleared on some sites similar request

saitanay’s picture

saitanay commented
Issue summary: View changes

DELETED

Anonymous’s picture

Anonymous (not verified) commented

For what it's worth, I recently ran into this with Drupal 7 and a 42GB cache_form table. What was happening in my case was at some point (I think around 24-25GB) the cache_form table became too large to clear on that particular system. The reason it became too large to clear is because MySQL would run out of disk space because of a combination of the binlog generated and the temporary storage used during that DELETE query in case of a rollback. After MySQL crashed and restarted, the temporary storage had been cleared so it was hard to see that it was an out of disk space issue.

Drupal also doesn't tell you if there was a failure in that manner.