Moodle

Database contention issue because mdl_user table is being continuously written to

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 1.9.5
  • Fix Version/s: None
  • Component/s: Database SQL/XMLDB
  • Labels:
    None
  • Affected Branches:
    MOODLE_19_STABLE

Description

As discussed in http://moodle.org/mod/forum/discuss.php?d=135455#p592874, I have reported that the fact that several fields mdl_user table get written to with updates to login time and ip addresses, database contention happens frequently in Moodle, leading to frequently hangups in the user experience.

This happens whenever a long query takes place that involves the user table (a great many such queries do). Then if someone logins or has other logable activity, it will hang all access to Moodle until both the read and the update queries have completed. The problem is made worse if there are any corrupt indexes.

Some developers believe that these things have been moved to other tables, but that is not the case. Some have said it affects only certain DB engines, but I am not sure which ones, and one of the most common ones used with installation instructions is such an engine.

The solution would seem to be to move updates involving routine changes in the user table to another table as such fields would not be a routine part of many of the queries that take extensive time to execute.

Activity

Hide
Michael de Raadt added a comment -

Thanks for reporting this issue.

We have detected that this issue has been inactive for over a year has been recorded as affecting versions that are no longer supported.

If you believe that this issue is still relevant to current versions (2.1 and beyond), please comment on the issue. Issues left inactive for a further month will be closed.

Michael d;

lqjjLKA0p6

Show
Michael de Raadt added a comment - Thanks for reporting this issue. We have detected that this issue has been inactive for over a year has been recorded as affecting versions that are no longer supported. If you believe that this issue is still relevant to current versions (2.1 and beyond), please comment on the issue. Issues left inactive for a further month will be closed. Michael d; lqjjLKA0p6
Hide
Michael de Raadt added a comment -

I'm closing this issue as it appears to have become inactive and is probably not relevant to a current supported version. If you are encountering this problem or one similar, please launch a new issue.

Show
Michael de Raadt added a comment - I'm closing this issue as it appears to have become inactive and is probably not relevant to a current supported version. If you are encountering this problem or one similar, please launch a new issue.

People

Vote (3)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved: