Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-19127

DB Deadlocks on ezcontentobject_tree when updating subnode

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Medium Medium
    • Resolution: Unresolved
    • Affects Version/s: 4.4.0
    • Fix Version/s: 4.4.0
    • Component/s: Database related
    • Labels:
      None
    • Environment:

      eZ Publish 4.4

      Description

      Customer is currently encountering a high number of DB deadlocks resulting in fatal errors, usually when publishing content. This appears to be due to the update of the subnode modified time in the ezcontentobject_tree table.

      Here is an example of the DB deadlock error messages:

      [ Feb 06 2012 16:58:12 ] [10.170.35.242] eZMySQLDB:
      Query error: Deadlock found when trying to get lock; try restarting transaction. Query: UPDATE ezcontentobject_tree SET modified_subnode=1328543892 WHERE node_id IN ( 1, 5, 105, 49299 )
       
      [ Feb 06 2012 16:58:12 ] [10.170.35.242] eZDBInterface::commit TRANSID-ed2d72f29cfa81a46a9fcae6a3d67393:
      Transaction in progress failed due to DB error, transaction was rollbacked. Transaction ID is TRANSID-ed2d72f29cfa81a46a9fcae6a3d67393.
      {noformat}
      

      Steps to reproduce

      There are no steps to reproduce, although the reported behavior can be verified in situations when there is heavy traffic.

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              unknown
              Reporter:
              Nuno Oliveira
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: