It looks like activity log is locking my db table activity_log_messages. It happens when I try to update the admin password. Is there a way to stop it... i can not disable the modules as its part of drupal commons and required by commons home
| 2081 | root | localhost | bs3 | Query | 471 | Updating | UPDATE activity_log_messages SET cached = '' WHERE (stream_owner_id = 1 AND stream_owner_type = 'use |
| 2139 | root | localhost | bs3 | Query | 446 | Locked | UPDATE activity_log_messages SET cached = '' WHERE (stream_owner_id = 39387 AND stream_owner_type = |
| 2209 | root | localhost | bs3 | Query | 397 | Locked | UPDATE activity_log_messages SET cached = '' WHERE (stream_owner_id = 39387 AND stream_owner_type = |
| 2215 | root | localhost | bs3 | Query | 389 | Locked | UPDATE activity_log_messages SET cached = '' WHERE (stream_owner_id = 1473 AND stream_owner_type = ' |
| 2309 | root | localhost | bs3 | Query | 323 | Locked | UPDATE activity_log_messages SET cached = '' WHERE (stream_owner_id = 15862 AND stream_owner_type = |
| 2456 | root | localhost | bs3 | Query | 201 | Locked | UPDATE activity_log_messages SET cached = '' WHERE (stream_owner_id = 16732 AND stream_owner_type = |
| 2639 | root | localhost | bs3 | Query | 67 | Locked | UPDATE activity_log_messages SET cached = '' |
| 2735 | root | localhost | bs3 | Query | 17 | Locked | UPDATE activity_log_messages SET cached = '' WHERE (stream_owner_id = 13119 AND stream_owner_type = |
Comments
Comment #1
icecreamyou commentedI have no idea what could be going on here, but:
Comment #2
knigh7 commentedHi,
Thanks for you reply, I am using Drupal Commons on Ubuntu 10.04, MySQL
Attached is the actual sql that locks
Thanks,
Comment #3
knigh7 commentedI think i fixed it, it looked like the script was locking, so I have set the activity log to clear every 1 day and it seems to have resolved the issue!
Comment #4
icecreamyou commentedIt looks like what's happening is that when a user updates their information, Activity Log tries to clear the cache for all messages related to that user, and that can be slow. If it's really slow and you have low connection termination times set on your server, the connection could be terminated before all the rows that need to be updated are unlocked. You didn't provide the information I asked for, and I haven't reproduced this, so I don't know how much of a problem this actually is. Regardless, it might be possible to lighten the load here (or at least only clear the cache for the most recent N messages or something) so marking this postponed.
Comment #5
knigh7 commentedThanks for your help. I have resolved this issue.