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

MariaDB Galera Cluster response longer than 1 second

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 10.2.22
    • N/A
    • OS: Ubuntu 18.04 server 64bit
      Linux: 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
      Database: mysql Ver 15.1 Distrib 10.2.22-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2

    Description

      MariaDB Galera Cluster response longer than 1 second

      the collected slow log samples as follow:

      SET timestamp=1557759155;
      UPDATE `api_logs` SET `response_code` = 200
      WHERE `id` = 104258;

      1. User@Host: CD.com[CD.com] @ [192.168.1.141]
      2. Thread_id: 1154 Schema: ciosa_productivo QC_hit: No
      3. Query_time: 1.055928 Lock_time: 0.000034 Rows_sent: 0 Rows_examined: 0
      4. Rows_affected: 1
        SET timestamp=1557759155;
        INSERT INTO `ci_sessions` (`session_id`, `ip_address`, `user_agent`, `last_activity`, `user_data`) VALUES ('6adcce0d0cc4dae7dbb3dcb7171979c0', '200.39.24.163', 'Mozilla/5.0 (Windows NT 6.2; WOW64; Trident/7.0; rv:11.0) like Gecko', 1557759147, '');
      5. User@Host: CD.com[CD.com] @ [192.168.1.56]
      6. Thread_id: 1157 Schema: ciosa_productivo QC_hit: No
      7. Query_time: 1.105405 Lock_time: 0.000024 Rows_sent: 0 Rows_examined: 0
      8. Rows_affected: 1

      Attachments

        1. status.txt
          5 kB
        2. slow.log
          6 kB

        Activity

          People

            jplindst Jan Lindström (Inactive)
            xiaolingfeng xiaolingfeng
            Votes:
            0 Vote for this issue
            Watchers:
            7 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.