Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-34645

truncated deadlock output

Details

    Description

      When a large number of deadlocks are generated the deadlock messages are incomplete without query. Although innodb_print_all_deadlocks is set to ON

      2024-06-29 12:37:58 1720967 [Note] InnoDB: *** WAITING FOR THIS LOCK TO BE GRANTED:
      		 
      2024-06-29 12:37:58 1720967 [Note] InnoDB: *** CONFLICTING WITH:
      		 
      2024-06-29 12:37:58 1720967 [Note] InnoDB: 
      2024-06-29 12:37:58 1720967 [Note] InnoDB: *** WAITING FOR THIS LOCK TO BE GRANTED:
      		 
      2024-06-29 12:37:58 1720967 [Note] InnoDB: *** CONFLICTING WITH:
      		 
      2024-06-29 12:37:58 1720967 [Note] InnoDB: *** WE ROLL BACK TRANSACTION (1)
      		 
      2024-06-29 12:37:59 1721033 [Note] InnoDB: Transactions deadlock detected, dumping detailed information.
      		 
      2024-06-29 12:37:59 1721033 [Note] InnoDB: 
      2024-06-29 12:37:59 1721033 [Note] InnoDB: *** WAITING FOR THIS LOCK TO BE GRANTED:
      		 
      2024-06-29 12:37:59 1721033 [Note] InnoDB: *** CONFLICTING WITH:
      		 
      2024-06-29 12:37:59 1721033 [Note] InnoDB: 
      2024-06-29 12:37:59 1721033 [Note] InnoDB: *** WAITING FOR THIS LOCK TO BE GRANTED:
      		 
      2024-06-29 12:37:59 1721033 [Note] InnoDB: *** CONFLICTING WITH:
      		 
      2024-06-29 12:37:59 1721033 [Note] InnoDB: *** WE ROLL BACK TRANSACTION (2)
      		 
      2024-06-29 12:37:59 1719165 [Note] InnoDB: Transactions deadlock detected, dumping detailed information.
      		 
      2024-06-29 12:37:59 1719165 [Note] InnoDB: 
      2024-06-29 12:37:59 1719165 [Note] InnoDB: *** WAITING FOR THIS LOCK TO BE GRANTED:
      		 
      2024-06-29 12:37:59 1719165 [Note] InnoDB: *** CONFLICTING WITH:
      		 
      2024-06-29 12:37:59 1719165 [Note] InnoDB: 
      2024-06-29 12:37:59 1719165 [Note] InnoDB: *** WAITING FOR THIS LOCK TO BE GRANTED:
      		 
      2024-06-29 12:37:59 1719165 [Note] InnoDB: *** CONFLICTING WITH:
      		 
      2024-06-29 12:37:59 1719165 [Note] InnoDB: *** WE ROLL BACK TRANSACTION (1)
      		 
      2024-06-29 12:37:59 1719247 [Note] InnoDB: Transactions deadlock detected, dumping detailed information.
      		 
      2024-06-29 12:37:59 1719247 [Note] InnoDB: 
      2024-06-29 12:37:59 1719247 [Note] InnoDB: *** WAITING FOR THIS LOCK TO BE GRANTED:
      		 
      2024-06-29 12:37:59 1719247 [Note] InnoDB: *** CONFLICTING WITH:
      		 
      2024-06-29 12:37:59 1719247 [Note] InnoDB: 
      2024-06-29 12:37:59 1719247 [Note] InnoDB: *** WAITING FOR THIS LOCK TO BE GRANTED:
      		 
      2024-06-29 12:37:59 1719247 [Note] InnoDB: *** CONFLICTING WITH:
      		 
      2024-06-29 12:37:59 1719247 [Note] InnoDB: *** WE ROLL BACK TRANSACTION (2)
      		 
      2024-06-29 12:37:59 1720870 [Note] InnoDB: Transactions deadlock detected, dumping detailed information.
      		 
      2024-06-29 12:37:59 1720870 [Note] InnoDB: 
      2024-06-29 12:37:59 1720870 [Note] InnoDB: *** WAITING FOR THIS LOCK TO BE GRANTED:
      		 
      2024-06-29 12:37:59 1720870 [Note] InnoDB: *** CONFLICTING WITH:
      		 
      2024-06-29 12:37:59 1720870 [Note] InnoDB:

      Attachments

        Issue Links

          is duplicated by

          Task - A task that needs to be done. MDEV-32576 increase query length in he InnoDB deadlock output

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Transition Time In Source Status Execution Times
            Kristian Nielsen made transition -
            Open Closed
            		1h 9m 1

            People

              Unassigned Unassigned
              muhammad.irfan Muhammad Irfan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.