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

show slave status, show global status deadlock

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 10.0.19
    • N/A
    • OTHER
    • None
    • RHEL 6.5 x86_64

    Description

      On parallel slave:

      | 16210 | system user |                     | NULL               | Connect | 1961018 | Waiting for work from SQL thread       | NULL               |    0.000 |
      | 16211 | system user |                     | NULL               | Connect | 1961148 | Waiting for work from SQL thread       | NULL               |    0.000 |
      | 16212 | system user |                     | NULL               | Connect | 1961148 | Waiting for work from SQL thread       | NULL               |    0.000 |
      | 16213 | system user |                     | NULL               | Connect | 1961148 | Waiting for work from SQL thread       | NULL               |    0.000 |
      | 16214 | system user |                     | NULL               | Connect | 1961148 | Waiting for work from SQL thread       | NULL               |    0.000 |
      | 16215 | system user |                     | NULL               | Connect | 1961018 | Waiting for work from SQL thread       | NULL               |    0.000 |
      | 16216 | system user |                     | NULL               | Connect | 1961148 | Waiting for work from SQL thread       | NULL               |    0.000 |
      | 16217 | system user |                     | NULL               | Connect | 1961019 | Waiting for work from SQL thread       | NULL               |    0.000 |
      | 21710 | munin       | localhost           | information_schema | Query   |  431112 | init                                   | SHOW SLAVE STATUS  |    0.000 |
      | 21711 | munin       | localhost           | information_schema | Query   |  431050 | Filling schema table                   | SHOW GLOBAL STATUS |    0.000 |
      | 21712 | munin       | localhost           | information_schema | Query   |  430988 | Filling schema table                   | SHOW GLOBAL STATUS |    0.000 |
      | 21713 | munin       | localhost           | information_schema | Query   |  430926 | Filling schema table                   | SHOW GLOBAL STATUS |    0.000 |
      | 21714 | munin       | localhost           | information_schema | Query   |  430864 | Filling schema table                   | SHOW GLOBAL STATUS |    0.000 |
      | 21715 | munin       | localhost           | information_schema | Query   |  430802 | Filling schema table                   | SHOW GLOBAL STATUS |    0.000 |
      | 21716 | munin       | localhost           | information_schema | Query   |  430740 | Filling schema table                   | SHOW GLOBAL STATUS |    0.000 |
      | 21717 | munin       | localhost           | information_schema | Query   |  430678 | Filling schema table                   | SHOW GLOBAL STATUS |    0.000 |
      | 21718 | munin       | localhost           | information_schema | Query   |  430616 | Filling schema table                   | SHOW GLOBAL STATUS |    0.000 |
      | 21719 | munin       | localhost           | information_schema | Query   |  430554 | Filling schema table                   | SHOW GLOBAL STATUS |    0.000 |
      | 21720 | munin       | localhost           | information_schema | Query   |  430492 | Filling schema table                   | SHOW GLOBAL STATUS |    0.000 |
      | 21721 | munin       | localhost           | information_schema | Query   |  430429 | Filling schema table                   | SHOW GLOBAL STATUS |    0.000 |
      | 21722 | munin       | localhost           | information_schema | Query   |  430367 | Filling schema table                   | SHOW GLOBAL STATUS |    0.000 |
      | 21723 | munin       | localhost           | information_schema | Query   |  430305 | Filling schema table                   | SHOW GLOBAL STATUS |    0.000 |
      | 21724 | munin       | localhost           | information_schema | Query   |  430243 | Filling schema table                   | SHOW GLOBAL STATUS |    0.000 |
      | 21725 | wpro        | 172.16.194.79:60555 | NULL               | Query   |   99373 | init                                   | SHOW SLAVE STATUS  |    0.000 |
      | 21726 | openquery   | 127.0.0.1:59505     | NULL               | Killed  |    2166 | init                                   | show slave status  |    0.000 |
      | 21731 | openquery   | localhost           | NULL               | Query   |       0 | init                                   | show processlist   |    0.000 |

      attached backtrace taken at this point. As no RPM build of debug symbols this is missing symbols still (MDEV-4646). Using an objdump analysis like MDEV-8108 will probably point to the relevant lock.

      Using MDEV-7126 as basis for test:
      no response from:

      show global variables
      show global variables like 'replicate_i%';
      show global status like 'Bytes_%';
      show global status like 'Busy_%';
      show global status like 'x%';

      response from:

      MariaDB [(none)]> show global variables like 'report%';
       
      +-----------------+-------------+
      | Variable_name   | Value       |
      +-----------------+-------------+
      | report_host     | tulwaurt009 |
      | report_password |             |
      | report_port     | 3310        |
      | report_user     |             |
      +-----------------+-------------+
      4 rows in set (0.00 sec)
       
      MariaDB [(none)]> show global variables like 'replicate_a%';
      +-------------------------------+-------+
      | Variable_name                 | Value |
      +-------------------------------+-------+
      | replicate_annotate_row_events | ON    |
      MariaDB [(none)]> show global variables like 'de%';
      +-----------------------------+----------+
      | Variable_name               | Value    |
      +-----------------------------+----------+
      | deadlock_search_depth_long  | 15       |
      | deadlock_search_depth_short | 4        |
      | deadlock_timeout_long       | 50000000 |
      | deadlock_timeout_short      | 10000    |
      | debug_no_thread_alarm       | OFF      |
      | default_regex_flags         |          |
      | default_storage_engine      | InnoDB   |
      | default_week_format         | 0        |
      | delay_key_write             | ON       |
      | delayed_insert_limit        | 100      |
      | delayed_insert_timeout      | 300      |
      | delayed_queue_size          | 1000     |
      +-----------------------------+----------+
       

      Attachments

        Issue Links

          Activity

            danblack Daniel Black added a comment -

            my bad. missed that datadir was out of space.

            danblack Daniel Black added a comment - my bad. missed that datadir was out of space.

            Did the server properly complain about the disk space issue in the error log?
            Did it unlock after the space was freed?

            elenst Elena Stepanova added a comment - Did the server properly complain about the disk space issue in the error log? Did it unlock after the space was freed?
            danblack Daniel Black added a comment -

            > Did the server properly complain about the disk space issue in the error log?

            yes

            > Did it unlock after the space was freed?

            I killed mysqld off before I realised there was no space. Worked fine space was freed and mysqld restarted.

            danblack Daniel Black added a comment - > Did the server properly complain about the disk space issue in the error log? yes > Did it unlock after the space was freed? I killed mysqld off before I realised there was no space. Worked fine space was freed and mysqld restarted.

            OK, then I think it's reasonable to close it. I was asking because I think in our pile of open issues we have some that complained about the server not reviving properly after running out of disk space and then getting it back.

            elenst Elena Stepanova added a comment - OK, then I think it's reasonable to close it. I was asking because I think in our pile of open issues we have some that complained about the server not reviving properly after running out of disk space and then getting it back.

            People

              Unassigned Unassigned
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.