日々の覚書: 2025

2025/04/18

Oracle Linux 8.10でのMySQL 9.3.0ビルド

MySQL Bugs: #117993: cmake failed MySQL 9.3.0 + Oracle Linux 8.10 で再現しなかったらしく、フレッシュインストールで試す。

$ wget https://dev.mysql.com/get/Downloads/MySQL-9.3/mysql-9.3.0.tar.gz
$ tar xf mysql-9.3.0.tar.gz
$ cd mysql-9.3.0/
$ sudo dnf install -y cmake

$ cmake -DCMAKE_INSTALL_PREFIX=/usr/mysql/9.3.0 -DMINIMAL_RELWITHDEBINFO=OFF -DFORCE_INSOURCE_BUILD=1
CMake Warning:
  No source or binary directory provided.  Both will be assumed to be the
  same as the current working directory, but note that this warning will
  become a fatal error in future CMake releases.

-- Running cmake version 3.26.5
-- Could NOT find Git (missing: GIT_EXECUTABLE)
-- This is .el8. as found from 'rpm -qf /'
-- Looking for a devtoolset compiler
CMake Warning at CMakeLists.txt:393 (MESSAGE):
  Could not find devtoolset compiler/linker in /opt/rh/gcc-toolset-13

CMake Warning at CMakeLists.txt:395 (MESSAGE):
  You need to install the required packages:

   yum install gcc-toolset-13-gcc gcc-toolset-13-gcc-c++ gcc-toolset-13-binutils gcc-toolset-13-annobin-annocheck gcc-toolset-13-annobin-plugin-gcc

CMake Error at CMakeLists.txt:397 (MESSAGE):
  Or you can set CMAKE_C_COMPILER and CMAKE_CXX_COMPILER explicitly.

-- Configuring incomplete, errors occurred!

$ sudo yum install gcc-toolset-13-gcc gcc-toolset-13-gcc-c++ gcc-toolset-13-binutils gcc-toolset-13-annobin-annocheck gcc-toolset-13-annobin-plugin-gcc
$ sudo dnf install -y --enablerepo=ol8_codeready_builder openssl-devel ncurses-devel libtirpc-devel rpcgen cpp
$ rm CMakeCache.txt
$ cmake -DCMAKE_INSTALL_PREFIX=/usr/mysql/9.3.0 -DMINIMAL_RELWITHDEBINFO=OFF -DFORCE_INSOURCE_BUILD=1

通ったわ…。

$ scl -l
You use deprecated syntax "-l|--list", use "list-collections" instead.
gcc-toolset-11
gcc-toolset-13

おま環だった。ごめんUmesh..

2025/04/16

HeatWave MySQLがどれくらいVanilla MySQL GPL版と同じくらいか考える旅 / 読み取りレプリカ編その2

日々の覚書: HeatWave MySQLがどれくらいVanilla MySQL GPL版と同じくらいか考える旅 / 読み取りレプリカ編の続き。

読み取りレプリカを1つ足してみた。ついでなので “MySQL.8.HA” にしてみたんだけれどこれは単に無視されるのかしら…(クラスタトータルのECPUも8ECPUしか増えなかったので、たぶんこれは関係なく1台だけ足されるんだと思う)

mysql> SELECT * FROM performance_schema.replication_group_members;
+---------------------------+-----------+-------------+-------------+--------------+-------------+----------------+----------------------------+
| CHANNEL_NAME              | MEMBER_ID | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE | MEMBER_ROLE | MEMBER_VERSION | MEMBER_COMMUNICATION_STACK |
+---------------------------+-----------+-------------+-------------+--------------+-------------+----------------+----------------------------+
| group_replication_applier |           |             |        NULL | OFFLINE      |             |                |                            |
+---------------------------+-----------+-------------+-------------+--------------+-------------+----------------+----------------------------+
1 row in set (0.00 sec)

前回気が付かなかったけど、読み取りレプリカは bind_address の設定が増えてた。ロードバランサ側のネームスペースのIPアドレスはWEB画面から見られるIPのいずれでもない。

+---------------+-------------------------------------------+
| Variable_name | Value                                     |
+---------------+-------------------------------------------+
| bind_address  | 10.0.0.195/mysql,10.5.195.88/loadbalancer |
+---------------+-------------------------------------------+
1 row in set (0.01 sec)

ロードバランサ側のIPはちゃんと分散するようになった。単純なラウンドロビンじゃないかしら。

$ time for n in {1..100} ; do mysql -h 10.0.0.118 -uadmin -sse "SELECT @@hostname" ;  done | sort | uniq -c
     58 eiewhuzpjiihavkp
     42 fuis3dpz4ueksuzu

real    0m2.259s
user    0m1.027s
sys     0m0.496s

1台クラッシュさせてみると、少なくとも10秒程度でロードバランサから外している気配はなくて、再起動してくるのに合わせてロードバランサに戻っている。これSQL_Threadだけ止めたりしたらどうなるんだろう。

$ while true ; do for n in {1..100} ; do mysql -h 10.0.0.118 -uadmin -sse "SELECT @@hostname" 2> >(sort -u);  done | sort | u
niq -c ; date; sleep 1; done
     50 eiewhuzpjiihavkp
     50 fuis3dpz4ueksuzu
Wed Apr 16 04:59:49 GMT 2025
     56 eiewhuzpjiihavkp
     44 fuis3dpz4ueksuzu
Wed Apr 16 04:59:52 GMT 2025
     50 eiewhuzpjiihavkp
     50 fuis3dpz4ueksuzu
Wed Apr 16 04:59:55 GMT 2025
     51 eiewhuzpjiihavkp
     49 fuis3dpz4ueksuzu
Wed Apr 16 04:59:58 GMT 2025
     43 eiewhuzpjiihavkp
     57 fuis3dpz4ueksuzu
Wed Apr 16 05:00:02 GMT 2025
      6 ERROR 2003 (HY000): Can't connect to MySQL server on '10.0.0.118:3306' (111)
      1 ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 104
     42 eiewhuzpjiihavkp
     51 fuis3dpz4ueksuzu
Wed Apr 16 05:00:05 GMT 2025
     45 ERROR 2003 (HY000): Can't connect to MySQL server on '10.0.0.118:3306' (111)
     55 fuis3dpz4ueksuzu
Wed Apr 16 05:00:08 GMT 2025
     47 ERROR 2003 (HY000): Can't connect to MySQL server on '10.0.0.118:3306' (111)
     53 fuis3dpz4ueksuzu
Wed Apr 16 05:00:10 GMT 2025
     52 ERROR 2003 (HY000): Can't connect to MySQL server on '10.0.0.118:3306' (111)
     48 fuis3dpz4ueksuzu
Wed Apr 16 05:00:13 GMT 2025
     50 ERROR 2003 (HY000): Can't connect to MySQL server on '10.0.0.118:3306' (111)
     50 fuis3dpz4ueksuzu
Wed Apr 16 05:00:16 GMT 2025
     54 eiewhuzpjiihavkp
     46 fuis3dpz4ueksuzu
Wed Apr 16 05:00:19 GMT 2025

↓エラーログ的にはこのへん。

mysql> SELECT * FROM performance_schema.error_log WHERE error_code <> 'MY-011071'\G

..
*************************** 386. row ***************************
    LOGGED: 2025-04-16 05:00:05.999056
 THREAD_ID: 0
      PRIO: Note
ERROR_CODE: MY-013930
 SUBSYSTEM: Server
      DATA: systemd notify: STATUS=Server startup in progress
*************************** 387. row ***************************
    LOGGED: 2025-04-16 05:00:05.999924
 THREAD_ID: 0
      PRIO: System
ERROR_CODE: MY-015015
 SUBSYSTEM: Server
      DATA: MySQL Server - start.

..
*************************** 604. row ***************************
    LOGGED: 2025-04-16 05:00:16.789157
 THREAD_ID: 0
      PRIO: System
ERROR_CODE: MY-010931
 SUBSYSTEM: Server
      DATA: /usr/sbin/mysqld: ready for connections. Version: '8.4.4-u5-cloud'  socket: '/var/run/mysqld/mysql.sock'  port: 3306  MySQL Enterprise - Cloud.
*************************** 605. row ***************************
    LOGGED: 2025-04-16 05:00:16.789172
 THREAD_ID: 0
      PRIO: System
ERROR_CODE: MY-013292
 SUBSYSTEM: Server
      DATA: Admin interface ready for connections, address: '127.0.0.1'  port: 7306
*************************** 606. row ***************************
    LOGGED: 2025-04-16 05:00:16.789529
 THREAD_ID: 0
      PRIO: Note
ERROR_CODE: MY-013930
 SUBSYSTEM: Server
      DATA: systemd notify: READY=1
STATUS=Server is operational
MAIN_PID=144141

..

エラーログで思い出したついでに読み取りレプリカを追加した時のエラーログ。

*************************** 1408. row ***************************
    LOGGED: 2025-04-16 05:31:42.525733
 THREAD_ID: 0
      PRIO: Note
ERROR_CODE: MY-013930
 SUBSYSTEM: Server
      DATA: systemd notify: READY=1
STATUS=Server is operational
MAIN_PID=35573

*************************** 1409. row ***************************
    LOGGED: 2025-04-16 05:34:50.412149
 THREAD_ID: 44
      PRIO: System
ERROR_CODE: MY-010597
 SUBSYSTEM: Repl
      DATA: 'CHANGE REPLICATION SOURCE TO FOR CHANNEL 'oci_managed_read_replica' executed'. Previous state source_host='', source_port= 3306, source_log_file='', source_log_pos= 4, source_bind=''. New state source_host='10.0.114.60', source_port= 7306, source_log_file='', source_log_pos= 4, source_bind=''.
*************************** 1410. row ***************************
    LOGGED: 2025-04-16 05:34:50.624034
 THREAD_ID: 47
      PRIO: Note
ERROR_CODE: MY-010581
 SUBSYSTEM: Repl
      DATA: Replica SQL thread for channel 'oci_managed_read_replica' initialized, starting replication in log 'FIRST' at position 0, relay log '/db/replication/relay-log-oci_managed_read_replica.000001' position: 4
*************************** 1411. row ***************************
    LOGGED: 2025-04-16 05:34:50.625468
 THREAD_ID: 46
      PRIO: System
ERROR_CODE: MY-014002
 SUBSYSTEM: Repl
      DATA: Replica receiver thread for channel 'oci_managed_read_replica': connected to source 'ocirpl@10.0.114.60:7306' with server_uuid=07c65c46-18f9-11f0-89e5-020017067068, server_id=-1253503313. Starting GTID-based replication.

HeatWave MySQLがどれくらいVanilla MySQL GPL版と同じくらいか考える旅 / 読み取りレプリカ編

WEB画面から作るレプリケーションの話。

「読み取りレプリカ」を “MySQL.8.Standalone” で1つ追加

ソースから観測

ソースから見ると名前解決が有効になってるのでIPアドレスはわからない。
skip_name_resolve はOFFで変えられない。

mysql> SHOW PROCESSLIST;
..
*************************** 4. row ***************************
     Id: 81
   User: ocirpl
   Host: gh7wpmau16ovyk9e.db0vcn0.mysqlcdbnrt.oraclevcn.com:52048
     db: NULL
Command: Binlog Dump GTID
   Time: 107046
  State: Source has sent all binlog to replica; waiting for more updates
   Info: NULL

..

mysql> SHOW REPLICAS;
+------------+------+------+------------+--------------------------------------+
| Server_Id  | Host | Port | Source_Id  | Replica_UUID                         |
+------------+------+------+------------+--------------------------------------+
| 1488978482 |      | 3306 | 3041463983 | 2ce0e2cf-18fb-11f0-bca9-02001704799d |
+------------+------+------+------------+--------------------------------------+
1 row in set (0.00 sec)

権限的には

CONNECTION_ADMIN
- offline_mode でも切断されない、新規接続できる
- read_only でも書き込める (が、他の書き込み用の権限がないのでこれは使ってなさそう)
SERVICE_CONNECTION_ADMIN
- admin_address:admin_port に接続できる
SYSTEM_USER
- non-SYSTEM_USER (= 我々に払い出される管理者アカウント) からの ALTER USER は効かない

あたり。

mysql> SHOW GRANTS FOR ocirpl;
+-------------------------------------------------------------------------------------------------------------+
| Grants for ocirpl@%                                                                                         |
+-------------------------------------------------------------------------------------------------------------+
| GRANT REPLICATION SLAVE ON *.* TO `ocirpl`@`%`                                                              |
| GRANT CONNECTION_ADMIN,GROUP_REPLICATION_STREAM,SERVICE_CONNECTION_ADMIN,SYSTEM_USER ON *.* TO `ocirpl`@`%` |
+-------------------------------------------------------------------------------------------------------------+
2 rows in set (0.00 sec)

mysql> ALTER USER ocirpl IDENTIFIED BY 'a' RETAIN CURRENT PASSWORD;
ERROR 1227 (42000): Access denied; you need (at least one of) the SYSTEM_USER privilege(s) for this operation

レプリカ側には「ホスト」に属しそうなIPと「ホスト群」に属しそうなIPが払い出されているぽい。

1台しか作ってないのでどっちを使っても同じところにアクセス。

$ for n in {1..100} ; do mysql -h 10.0.0.118 -uadmin -sse "SELECT @@hostname" ;  done | sort | uniq -c
    100 fuis3dpz4ueksuzu

$ for n in {1..100} ; do mysql -h 10.0.0.70 -uadmin -sse "SELECT @@hostname" ;  done | sort | uniq -c
    100 fuis3dpz4ueksuzu

ところで、100回程度でも気が付くくらいには差があった。LB経由の方が若干遅い。

$ time for n in {1..100} ; do mysql -h 10.0.0.118 -uadmin -sse "SELECT @@hostname" ;  done | sort | uniq -c
    100 fuis3dpz4ueksuzu

real    0m2.369s
user    0m1.040s
sys     0m0.489s

$ time for n in {1..100} ; do mysql -h 10.0.0.70 -uadmin -sse "SELECT @@hostname" ;  done | sort | uniq -c
    100 fuis3dpz4ueksuzu

real    0m1.708s
user    0m1.030s
sys     0m0.495s

レプリカから観測

大きめのシェイプじゃないとそもそもレプリカを作れないようになっている関係（？）で replica_parallel_workers はやたら多い。

mysql> SELECT @@replica_parallel_workers;
+----------------------------+
| @@replica_parallel_workers |
+----------------------------+
|                         48 |
+----------------------------+
1 row in set (0.00 sec)

mysql> SELECT name, processlist_user, processlist_host, COUNT(*) FROM performance_schema.threads WHERE type <> 'BACKGROUPND' GROUP BY 1, 2, 3;

..
| thread/sql/replica_io                                    | ociadmin         | localhost                                                 |        1 |
| thread/sql/replica_sql                                   | ociadmin         | localhost                                                 |        1 |
| thread/sql/replica_worker                                | ociadmin         | localhost                                                 |       48 |

..

performance_schema.threads は ociadmin なのに SHOW REPLICA STATUS は ocirpl なのはなんでかと思ったけど、 p_s.threads は単に START REPLICA した時のアカウントが出るっぽい。知らなかった。

mysql> SHOW REPLICA STATUS\G
*************************** 1. row ***************************
             Replica_IO_State: Waiting for source to send event
                  Source_Host: 10.0.114.60
                  Source_User: ocirpl
                  Source_Port: 7306
                Connect_Retry: 60
              Source_Log_File: binary-log.020772
          Read_Source_Log_Pos: 198
               Relay_Log_File: relay-log-oci_managed_read_replica.000306
                Relay_Log_Pos: 377
        Relay_Source_Log_File: binary-log.020772
           Replica_IO_Running: Yes
          Replica_SQL_Running: Yes
              Replicate_Do_DB:
          Replicate_Ignore_DB:
           Replicate_Do_Table:
       Replicate_Ignore_Table:
      Replicate_Wild_Do_Table:
  Replicate_Wild_Ignore_Table:
                   Last_Errno: 0
                   Last_Error:
                 Skip_Counter: 0
          Exec_Source_Log_Pos: 198
              Relay_Log_Space: 655
              Until_Condition: None
               Until_Log_File:
                Until_Log_Pos: 0
           Source_SSL_Allowed: Yes
           Source_SSL_CA_File:
           Source_SSL_CA_Path:
              Source_SSL_Cert:
            Source_SSL_Cipher:
               Source_SSL_Key:
        Seconds_Behind_Source: 0
Source_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error:
               Last_SQL_Errno: 0
               Last_SQL_Error:
  Replicate_Ignore_Server_Ids:
             Source_Server_Id: 3041463983
                  Source_UUID: 07c65c46-18f9-11f0-89e5-020017067068
             Source_Info_File: mysql.slave_master_info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
    Replica_SQL_Running_State: Replica has read all relay log; waiting for more updates
           Source_Retry_Count: 0
                  Source_Bind:
      Last_IO_Error_Timestamp:
     Last_SQL_Error_Timestamp:
               Source_SSL_Crl:
           Source_SSL_Crlpath:
           Retrieved_Gtid_Set:
            Executed_Gtid_Set: 9330ac0f-e14a-11ef-a07c-0200170681c1:1-853240
                Auto_Position: 1
         Replicate_Rewrite_DB:
                 Channel_Name: oci_managed_read_replica
           Source_TLS_Version: TLSv1.2,TLSv1.3
       Source_public_key_path:
        Get_Source_public_key: 1
            Network_Namespace:
1 row in set (0.00 sec)

チャンネル名が指定されてたり、ポートが7306になったりしている。
これは admin_port 使ってるんだろうと思うんだけど

mysql> SELECT @@admin_address, @@admin_port;
+-----------------+--------------+
| @@admin_address | @@admin_port |
+-----------------+--------------+
| 127.0.0.1       |         7306 |
+-----------------+--------------+
1 row in set (0.00 sec)

なので、admin_portにアクセスできるのは本来自分自身にしかアクセスできないはず。
ぱっと思いつくのは 127.0.0.1:7306 は mysqld がLISTENして、 10.0.114.60:7306 は (ソースと同じノードに入った) mysqlrouter なりがLISTENして転送してればそうできるかなあと思ったりした。

なおこの 10.0.114.60 (レプリカから見たレプリケーションソースのアドレス) はクライアントからはアクセスできなかった。

mysql> SELECT * FROM mysql.slave_master_info\G
*************************** 1. row ***************************
                Number_of_lines: 33
                Master_log_name:
                 Master_log_pos: 4
                           Host: 10.0.114.60
                      User_name:
                  User_password:
                           Port: 7306
                  Connect_retry: 60
                    Enabled_ssl: 1
                         Ssl_ca:
                     Ssl_capath:
                       Ssl_cert:
                     Ssl_cipher:
                        Ssl_key:
         Ssl_verify_server_cert: 0
                      Heartbeat: 30
                           Bind:
             Ignored_server_ids: 0
                           Uuid:
                    Retry_count: 0
                        Ssl_crl:
                    Ssl_crlpath:
          Enabled_auto_position: 1
                   Channel_name: oci_managed_read_replica
                    Tls_version: TLSv1.2,TLSv1.3
                Public_key_path:
                 Get_public_key: 1
              Network_namespace:
   Master_compression_algorithm: uncompressed
  Master_zstd_compression_level: 3
               Tls_ciphersuites: NULL
Source_connection_auto_failover: 0
                      Gtid_only: 1
1 row in set (0.00 sec)

パスワードが平文で書かれることで（俺の中では）有名な mysql.slave_master_info にはユーザー情報はない。これは CHANGE REPLICATION SOURCE TO source_user = ?, source_password = ? でアカウントを設定せずに START REPLICA USER=? PASSWORD=? で START REPLICA ごとに指定するとこうなるのでそれを使ってる。

確かに自動化されてて人間が START REPLICA を打つことがない今日日のケースではそれは正しい気がする。

mysql> SELECT * FROM mysql.slave_relay_log_info\G
*************************** 1. row ***************************
                             Number_of_lines: 14
                              Relay_log_name: /db/replication/relay-log-oci_managed_read_replica.000001
                               Relay_log_pos: 4
                             Master_log_name:
                              Master_log_pos: 0
                                   Sql_delay: 0
                           Number_of_workers: 0
                                          Id: 1
                                Channel_name: oci_managed_read_replica
                   Privilege_checks_username: NULL
                   Privilege_checks_hostname: NULL
                          Require_row_format: 1
             Require_table_primary_key_check: OFF
 Assign_gtids_to_anonymous_transactions_type: OFF
Assign_gtids_to_anonymous_transactions_value:
1 row in set (0.00 sec)

mysql.slave_relay_log_info には特に面白い情報はない。 REPLICATION_APPLIER 権限を使った分離はされてないってことくらいか。

mysql> SHOW BINARY LOGS;
ERROR 1381 (HY000): You are not using binary logging

レプリカではバイナリログが有効になっていないので、バイナリログを吸い上げるツールをソースに向けたくなくてレプリカ……というわけにはいかなさそう。

取り敢えずこんなところで。

2025/04/13

HeatWave MySQLがどれくらいVanilla MySQL GPL版と同じくらいか考える旅 / performance_schema編

このへんからHeatWave MySQLが9.2から8.4のものに変わっている。

全体として sar の代わりに使えそうなものがそろっている感じ。

2a3
> component_scheduler_tasks
53a55,57
> health_block_device
> health_process_memory
> health_system_memory
58a63,64
> lakehouse_query_stats
> lakehouse_table_query_stats
86a93,101
> rpd_column_id
> rpd_columns
> rpd_exec_stats
> rpd_mirror
> rpd_nodes
> rpd_preload_stats
> rpd_query_stats
> rpd_table_id
> rpd_tables
105a121,128
> system_cpu_stats
> system_cpu_stats_history
> system_disk_stats
> system_disk_stats_history
> system_memory_stats
> system_memory_stats_history
> system_process_stats
> system_process_stats_history
111a135,138
> tp_connections
> tp_thread_group_state
> tp_thread_group_stats
> tp_thread_state

rpdはHeatWave機能( SECONDARY_ENGINE=RAPID )、tpはThread Pool機能(EE限定)、lakehouseもHeatWave系の何か、component_scheduler_tasks も今のところEE限定Audit Log系のスケジューラ。

health_block_device

df 的なものを確認できる。便利。

mysql> SELECT * FROM performance_schema.health_block_device LIMIT 5;
+--------+---------------------+-------------+-----------------+-------------+-------------+
| DEVICE | TIMESTAMP           | TOTAL_BYTES | AVAILABLE_BYTES | USE_PERCENT | MOUNT_POINT |
+--------+---------------------+-------------+-----------------+-------------+-------------+
| xfs    | 2025-04-12 02:10:08 | 53578039296 |     13374173184 |       75.04 | /db         |
| xfs    | 2025-04-12 02:11:09 | 53578039296 |     13375037440 |       75.04 | /db         |
| xfs    | 2025-04-12 02:12:08 | 53578039296 |     13372993536 |       75.04 | /db         |
| xfs    | 2025-04-12 02:13:08 | 53578039296 |     13372977152 |       75.04 | /db         |
| xfs    | 2025-04-12 02:14:08 | 53578039296 |     13372993536 |       75.04 | /db         |
+--------+---------------------+-------------+-----------------+-------------+-------------+
5 rows in set (0.00 sec)

/db の下に入りそうなものはibdファイル、 #ib_redo* , temp*.ibt 他バイナリログ、リレーログ、エラーログ、スローログにジェネラルログその他。後ろ2つは有効化できないような気もするけど入るには入る。
エラーログのファイル出力の無効化は少なくともGPL版ではできないけど、同じく無効化できないとすると大きくなった時にどうやってローテーションできるんだろうか。

mysql> SHOW GLOBAL VARIABLES WHERE value LIKE '%/db%';
+----------------------------------------+----------------------------------------------------+
| Variable_name                          | Value                                              |
+----------------------------------------+----------------------------------------------------+
| admin_ssl_ca                           | /db/metadata/pki/admin_endpoint/ca.pem             |
| admin_ssl_cert                         | /db/metadata/pki/admin_endpoint/server-cert.pem    |
| admin_ssl_key                          | /db/metadata/pki/admin_endpoint/server-key.pem     |
| audit_log_file                         | /db/audit/audit.log                                |
| caching_sha2_password_private_key_path | /db/metadata/pki/customer_endpoint/private_key.pem |
| caching_sha2_password_public_key_path  | /db/metadata/pki/customer_endpoint/public_key.pem  |
| datadir                                | /db/data/                                          |
| general_log_file                       | /db/data/jh5ascukca6rptpn.log                      |
| health_monitor.disk_monitored          | /db                                                |
| innodb_data_home_dir                   | /db/data/                                          |
| innodb_log_group_home_dir              | /db/redo                                           |
| innodb_tmpdir                          | /db/tmp                                            |
| innodb_undo_directory                  | /db/undo                                           |
| log_bin_basename                       | /db/binlogs/binary-log                             |
| log_bin_index                          | /db/binlogs/binary-log.index                       |
| log_error                              | /db/log/error.log                                  |
| mysqlx_ssl_ca                          | /db/metadata/pki/customer_endpoint/ca.pem          |
| mysqlx_ssl_cert                        | /db/metadata/pki/customer_endpoint/server-cert.pem |
| mysqlx_ssl_key                         | /db/metadata/pki/customer_endpoint/server-key.pem  |
| rapid_file_prefix                      | /db/log/rpdlogs/                                   |
| relay_log                              | /db/replication/relay-log                          |
| relay_log_basename                     | /db/replication/relay-log                          |
| relay_log_index                        | /db/replication/relay-log.index                    |
| replica_load_tmpdir                    | /db/tmp                                            |
| sha256_password_private_key_path       | /db/metadata/pki/customer_endpoint/private_key.pem |
| sha256_password_public_key_path        | /db/metadata/pki/customer_endpoint/public_key.pem  |
| slave_load_tmpdir                      | /db/tmp                                            |
| slow_query_log_file                    | /db/data/jh5ascukca6rptpn-slow.log                 |
| ssl_ca                                 | /db/metadata/pki/customer_endpoint/ca.pem          |
| ssl_cert                               | /db/metadata/pki/customer_endpoint/server-cert.pem |
| ssl_key                                | /db/metadata/pki/customer_endpoint/server-key.pem  |
| tmpdir                                 | /db/tmp                                            |
+----------------------------------------+----------------------------------------------------+
32 rows in set (0.01 sec)

health_process_memory

ps で見られるよりちょっと充実してるくらい。ページフォールトの回数は監視の指標になったりするかしら（スラッシングの時は馬鹿みたいに増えるよね？）

mysql> SELECT * FROM performance_schema.health_process_memory LIMIT 5;
+---------------------+--------------+-------+-------------+-------------+------------+-------------+
| TIMESTAMP           | PROCESS_NAME | PID   | VM_RSS      | VM_DATA     | VM_SWAP    | PAGE_FAULTS |
+---------------------+--------------+-------+-------------+-------------+------------+-------------+
| 2025-04-12 02:17:08 | mysqld       | 32527 | 24412291072 | 34097352704 | 8679198720 |       39853 |
| 2025-04-12 02:18:08 | mysqld       | 32527 | 24412237824 | 34097352704 | 8679194624 |       39853 |
| 2025-04-12 02:19:08 | mysqld       | 32527 | 24411959296 | 34097352704 | 8679194624 |       39853 |
| 2025-04-12 02:20:08 | mysqld       | 32527 | 24411840512 | 34098405376 | 8679194624 |       39853 |
| 2025-04-12 02:21:08 | mysqld       | 32527 | 24411840512 | 34097352704 | 8679194624 |       39853 |
+---------------------+--------------+-------+-------------+-------------+------------+-------------+
5 rows in set (0.00 sec)

health_system_memory

こっちは free 相当かしら。書き込みを発生させても(GPL版だとバイナリログとInnoDBログはページキャッシュに乗る) MEMORY_FS_CACHEが上がらないので何か細工をしているかしら(いやだいたい他のプロセスだってページキャッシュを使いそうなものだから0になるのがそもそも計算式が違うのかも知れない)

mysql> SELECT * FROM performance_schema.health_system_memory LIMIT 5;
+---------------------+--------------+------------+-------------+-------------+-----------------+-------------+------------+
| TIMESTAMP           | TOTAL_MEMORY | AVAILABLE  | USE_PERCENT | MEMORY_FREE | MEMORY_FS_CACHE | SWAP_TOTAL  | SWAP_FREE  |
+---------------------+--------------+------------+-------------+-------------+-----------------+-------------+------------+
| 2025-04-12 02:20:08 |  33350533120 | 6123864064 |       81.64 |  1771307008 |               0 | 12403597312 | 3219906560 |
| 2025-04-12 02:21:08 |  33350533120 | 5943508992 |       82.18 |  1590870016 |               0 | 12403597312 | 3219906560 |
| 2025-04-12 02:22:08 |  33350533120 | 5952991232 |       82.15 |  1599184896 |               0 | 12403597312 | 3219906560 |
| 2025-04-12 02:23:08 |  33350533120 | 5956276224 |       82.14 |  1616691200 |               0 | 12403597312 | 3219906560 |
| 2025-04-12 02:24:08 |  33350533120 | 5965537280 |       82.11 |  1625153536 |               0 | 12403597312 | 3220168704 |
+---------------------+--------------+------------+-------------+-------------+-----------------+-------------+------------+
5 rows in set (0.00 sec)

system_cpu_stats

起動時から今までのCPU使用時間の統計だろうか。

mysql> SELECT * FROM performance_schema.system_cpu_stats;
+---------------------+------+----------+---------+-----------+-----------+-----------+--------+------------+----------+----------+---------------+
| TIMESTAMP           | CPU  | USER_MS  | NICE_MS | SYSTEM_MS | IDLE_MS   | IOWAIT_MS | IRQ_MS | SOFTIRQ_MS | STEAL_MS | GUEST_MS | GUEST_NICE_MS |
+---------------------+------+----------+---------+-----------+-----------+-----------+--------+------------+----------+----------+---------------+
| 2025-04-13 02:25:15 | cpu  | 92202470 | 3654590 |  40194370 | 337109440 |   4165050 |      0 |     295800 |   533380 |        0 |             0 |
| 2025-04-13 02:25:15 | cpu0 | 46503290 | 1839240 |  20357500 | 167966720 |   2067360 |      0 |     104300 |   265500 |        0 |             0 |
| 2025-04-13 02:25:15 | cpu1 | 45699170 | 1815340 |  19836870 | 169142720 |   2097690 |      0 |     191500 |   267870 |        0 |             0 |
+---------------------+------+----------+---------+-----------+-----------+-----------+--------+------------+----------+----------+---------------+
3 rows in set (0.00 sec)

system_cpu_stats_history

system_cpu_stats の履歴を収めてるぽい。

mysql> SELECT * FROM performance_schema.system_cpu_stats_history LIMIT 5;
+---------------------+------+----------+---------+-----------+-----------+-----------+--------+------------+----------+----------+---------------+
| TIMESTAMP           | CPU  | USER_MS  | NICE_MS | SYSTEM_MS | IDLE_MS   | IOWAIT_MS | IRQ_MS | SOFTIRQ_MS | STEAL_MS | GUEST_MS | GUEST_NICE_MS |
+---------------------+------+----------+---------+-----------+-----------+-----------+--------+------------+----------+----------+---------------+
| 2025-04-12 02:27:08 | cpu  | 58580280 | 1966080 |  23749580 | 218716700 |   2931420 |      0 |     244180 |   376080 |        0 |             0 |
| 2025-04-12 02:27:08 | cpu0 | 29572120 |  984210 |  12045760 | 108981620 |   1451510 |      0 |      79990 |   187720 |        0 |             0 |
| 2025-04-12 02:27:08 | cpu1 | 29008150 |  981870 |  11703820 | 109735070 |   1479910 |      0 |     164180 |   188360 |        0 |             0 |
| 2025-04-12 02:28:08 | cpu  | 58602220 | 1966300 |  23760060 | 218802810 |   2931810 |      0 |     244210 |   376170 |        0 |             0 |
| 2025-04-12 02:28:08 | cpu0 | 29581300 |  984330 |  12051680 | 109025620 |   1451850 |      0 |      80000 |   187750 |        0 |             0 |
+---------------------+------+----------+---------+-----------+-----------+-----------+--------+------------+----------+----------+---------------+
5 rows in set (0.00 sec)

ふと気になったのでストレージエンジンを確認してみたけどちゃんとPERFORMANCE_SCHEMAストレージエンジン。

mysql> SHOW CREATE TABLE performance_schema.system_cpu_stats_history\G
*************************** 1. row ***************************
       Table: system_cpu_stats_history
Create Table: CREATE TABLE `system_cpu_stats_history` (
  `TIMESTAMP` timestamp NOT NULL,
  `CPU` varchar(255) DEFAULT NULL,
  `USER_MS` bigint unsigned DEFAULT NULL,
  `NICE_MS` bigint unsigned DEFAULT NULL,
  `SYSTEM_MS` bigint unsigned DEFAULT NULL,
  `IDLE_MS` bigint unsigned DEFAULT NULL,
  `IOWAIT_MS` bigint unsigned DEFAULT NULL,
  `IRQ_MS` bigint unsigned DEFAULT NULL,
  `SOFTIRQ_MS` bigint unsigned DEFAULT NULL,
  `STEAL_MS` bigint unsigned DEFAULT NULL,
  `GUEST_MS` bigint unsigned DEFAULT NULL,
  `GUEST_NICE_MS` bigint unsigned DEFAULT NULL
) ENGINE=PERFORMANCE_SCHEMA DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
1 row in set (0.00 sec)

mysql> SHOW CREATE TABLE performance_schema.system_cpu_stats\G
*************************** 1. row ***************************
       Table: system_cpu_stats
Create Table: CREATE TABLE `system_cpu_stats` (
  `TIMESTAMP` timestamp NOT NULL,
  `CPU` varchar(255) DEFAULT NULL,
  `USER_MS` bigint unsigned DEFAULT NULL,
  `NICE_MS` bigint unsigned DEFAULT NULL,
  `SYSTEM_MS` bigint unsigned DEFAULT NULL,
  `IDLE_MS` bigint unsigned DEFAULT NULL,
  `IOWAIT_MS` bigint unsigned DEFAULT NULL,
  `IRQ_MS` bigint unsigned DEFAULT NULL,
  `SOFTIRQ_MS` bigint unsigned DEFAULT NULL,
  `STEAL_MS` bigint unsigned DEFAULT NULL,
  `GUEST_MS` bigint unsigned DEFAULT NULL,
  `GUEST_NICE_MS` bigint unsigned DEFAULT NULL
) ENGINE=PERFORMANCE_SCHEMA DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
1 row in set (0.00 sec)

まあ、PERFORMANCE_SCHEMAストレージエンジンでもファイル(procfs)を読んで返すとかできるし特に変とは思わないか。

system_disk_stats

累計のdiskの読み書きに関して。 sysstat っぽいなと思ったけどあれは累計じゃないか。

mysql> SELECT * FROM performance_schema.system_disk_stats;
+---------------------+--------+------------+-------------+--------------+-------------+--------------+---------------+---------+---------------+
| TIMESTAMP           | DEVICE | READ_COUNT | READ_BYTES  | READ_TIME_MS | WRITE_COUNT | WRITE_BYTES  | WRITE_TIME_MS | FLUSHES | FLUSH_TIME_MS |
+---------------------+--------+------------+-------------+--------------+-------------+--------------+---------------+---------+---------------+
| 2025-04-13 02:28:46 | sda    |    3590521 | 94861327360 |      4041039 |     3996418 | 169612680192 |      66848003 |       0 |             0 |
| 2025-04-13 02:28:46 | sda1   |       2183 |    94466048 |         1227 |         270 |       232448 |           278 |       0 |             0 |
| 2025-04-13 02:28:46 | sda2   |       5707 |   655307776 |         8770 |          49 |       360448 |            54 |       0 |             0 |
| 2025-04-13 02:28:46 | sda3   |    3580836 | 94078171136 |      4029841 |     3996099 | 169612087296 |      66847671 |       0 |             0 |
| 2025-04-13 02:28:46 | dm-0   |       1146 |    28423168 |         1238 |      561845 |   2879037440 |       1418670 |       0 |             0 |
| 2025-04-13 02:28:46 | dm-1   |      12929 |   432137216 |        52422 |     2366458 |  20237922304 |      10891143 |       0 |             0 |
| 2025-04-13 02:28:46 | dm-2   |      13440 |   299335680 |         7041 |           0 |            0 |             0 |       0 |             0 |
| 2025-04-13 02:28:46 | dm-3   |      13440 |   299335680 |         5229 |           0 |            0 |             0 |       0 |             0 |
| 2025-04-13 02:28:46 | dm-4   |     536500 |  9941148672 |       330328 |     2120870 |  15134523392 |       8619408 |       0 |             0 |
| 2025-04-13 02:28:46 | dm-5   |     398113 |  9255805952 |       666898 |      695716 | 112435957760 |      20133941 |       0 |             0 |
| 2025-04-13 02:28:46 | dm-6   |       4905 |   141210624 |         9311 |      312462 |   1297354752 |       1386226 |       0 |             0 |
| 2025-04-13 02:28:46 | dm-7   |    2658197 | 71729394688 |      3257884 |      927932 |   5640888320 |      12070232 |       0 |             0 |
| 2025-04-13 02:28:46 | dm-8   |     315846 |  1313099776 |       366455 |     2926368 |  11986403328 |     671492181 |       0 |             0 |
| 2025-04-13 02:28:46 | dm-9   |      13536 |   301473792 |         4877 |           0 |            0 |             0 |       0 |             0 |
| 2025-04-13 02:28:46 | sdb    |      57672 |  1236349440 |        27859 |     4721229 |  61814304768 |       9779030 |       0 |             0 |
| 2025-04-13 02:28:46 | dm-10  |      59790 |  1211236864 |        27771 |     4777276 |  61814304768 |      10489399 |       0 |             0 |
+---------------------+--------+------------+-------------+--------------+-------------+--------------+---------------+---------+---------------+
16 rows in set (0.00 sec)

system_disk_stats_history

同じく system_disk_stats の履歴版。

mysql> SELECT * FROM performance_schema.system_disk_stats_history LIMIT 5;
+---------------------+--------+------------+-------------+--------------+-------------+--------------+---------------+---------+---------------+
| TIMESTAMP           | DEVICE | READ_COUNT | READ_BYTES  | READ_TIME_MS | WRITE_COUNT | WRITE_BYTES  | WRITE_TIME_MS | FLUSHES | FLUSH_TIME_MS |
+---------------------+--------+------------+-------------+--------------+-------------+--------------+---------------+---------+---------------+
| 2025-04-12 02:32:08 | sda    |    2607392 | 62992951808 |      3066695 |     2576279 | 113759454720 |      45227436 |       0 |             0 |
| 2025-04-12 02:32:08 | sda1   |       1790 |    72803328 |         1035 |         192 |       165376 |           214 |       0 |             0 |
| 2025-04-12 02:32:08 | sda2   |       3527 |   370439168 |         4941 |          33 |       229376 |            33 |       0 |             0 |
| 2025-04-12 02:32:08 | sda3   |    2600702 | 62523068928 |      3059719 |     2576054 | 113759059968 |      45227187 |       0 |             0 |
| 2025-04-12 02:32:08 | dm-0   |       1092 |    27317248 |         1210 |      361034 |   1851645952 |        935976 |       0 |             0 |
+---------------------+--------+------------+-------------+--------------+-------------+--------------+---------------+---------+---------------+
5 rows in set (0.00 sec)

system_memory_stats

メモリの使用量… health_system_memory と違ってこっちは CACHED_BYTES がちゃんとある。こっちの方があてになるんじゃないか感。

ところでこのノード、 SWAP_USED 多くありません…？

mysql> SELECT * FROM performance_schema.system_memory_stats\G
*************************** 1. row ***************************
       TIMESTAMP: 2025-04-13 02:32:02
     TOTAL_BYTES: 33350533120
      FREE_BYTES: 1845776384
      USED_BYTES: 24992989184
 AVAILABLE_BYTES: 7582982144
   BUFFERS_BYTES: 609406976
    CACHED_BYTES: 4481605632
      SLAB_BYTES: 1420754944
SWAP_TOTAL_BYTES: 12403597312
 SWAP_FREE_BYTES: 1806651392
 SWAP_USED_BYTES: 10596945920
         SWAP_IN: 93847047
        SWAP_OUT: 226300583
1 row in set (0.00 sec)

32GBあるうちp_sで計測できているのはたかだか10GBちょっとで、p_sとRSSに差があるのはいつものことだけど health_process_memory ともだいぶ乖離していて(俺のこのノードは)大丈夫だろうか(多少の心当たりはある)

mysql> SELECT event_name, format_bytes(CURRENT_NUMBER_OF_BYTES_USED) FROM memory_summary_global_by_event_name ORDER BY CURRENT_NUMBER_OF_BYTES_USED DESC LIMIT 10;
+-----------------------------------------------------------------------------+--------------------------------------------+
| event_name                                                                  | format_bytes(CURRENT_NUMBER_OF_BYTES_USED) |
+-----------------------------------------------------------------------------+--------------------------------------------+
| memory/innodb/buf_buf_pool                                                  | 10.22 GiB                                  |
| memory/performance_schema/table_shares                                      | 196.00 MiB                                 |
| memory/performance_schema/file_instances                                    | 134.75 MiB                                 |
| memory/innodb/fil0fil                                                       | 83.96 MiB                                  |
| memory/innodb/os0event                                                      | 79.50 MiB                                  |
| memory/performance_schema/events_errors_summary_by_thread_by_error          | 69.36 MiB                                  |
| memory/performance_schema/table_io_waits_summary_by_index_usage             | 68.75 MiB                                  |
| memory/innodb/log_buffer_memory                                             | 64.00 MiB                                  |
| memory/performance_schema/events_statements_summary_by_thread_by_event_name | 58.01 MiB                                  |
| memory/performance_schema/memory_summary_by_thread_by_event_name            | 41.31 MiB                                  |
+-----------------------------------------------------------------------------+--------------------------------------------+
10 rows in set (0.00 sec)

mysql> SELECT * FROM performance_schema.health_process_memory ORDER BY timestamp DESC LIMIT 1;
+---------------------+--------------+-------+-------------+-------------+-------------+-------------+
| TIMESTAMP           | PROCESS_NAME | PID   | VM_RSS      | VM_DATA     | VM_SWAP     | PAGE_FAULTS |
+---------------------+--------------+-------+-------------+-------------+-------------+-------------+
| 2025-04-13 02:38:08 | mysqld       | 32527 | 22930632704 | 34099458048 | 10119245824 |       44544 |
+---------------------+--------------+-------+-------------+-------------+-------------+-------------+
1 row in set (0.00 sec)

system_memory_stats_history

system_memory_stats のヒストリ版。

mysql> SELECT * FROM performance_schema.system_memory_stats_history LIMIT 5;
+---------------------+-------------+------------+-------------+-----------------+---------------+--------------+------------+------------------+-----------------+-----------------+----------+-----------+
| TIMESTAMP           | TOTAL_BYTES | FREE_BYTES | USED_BYTES  | AVAILABLE_BYTES | BUFFERS_BYTES | CACHED_BYTES | SLAB_BYTES | SWAP_TOTAL_BYTES | SWAP_FREE_BYTES | SWAP_USED_BYTES | SWAP_IN  | SWAP_OUT  |
+---------------------+-------------+------------+-------------+-----------------+---------------+--------------+------------+------------------+-----------------+-----------------+----------+-----------+
| 2025-04-12 02:40:08 | 33350533120 | 1592639488 | 26609328128 |      5956194304 |     591269888 |   3181879296 | 1375416320 |      12403597312 |      3220692992 |      9182904320 | 62717427 | 170109173 |
| 2025-04-12 02:41:08 | 33350533120 | 1560834048 | 26639466496 |      5925982208 |     591417344 |   3182825472 | 1375989760 |      12403597312 |      3220692992 |      9182904320 | 62717443 | 170384133 |
| 2025-04-12 02:42:08 | 33350533120 | 1479790592 | 26719854592 |      5845614592 |     591486976 |   3183243264 | 1376157696 |      12403597312 |      3220692992 |      9182904320 | 62717543 | 170395089 |
| 2025-04-12 02:43:08 | 33350533120 | 1442398208 | 26755567616 |      5809876992 |     591552512 |   3184652288 | 1376362496 |      12403597312 |      3220692992 |      9182904320 | 62717555 | 170406233 |
| 2025-04-12 02:44:08 | 33350533120 | 1540587520 | 26656505856 |      5908996096 |     591650816 |   3185319936 | 1376468992 |      12403597312 |      3220692992 |      9182904320 | 62717563 | 170417249 |
+---------------------+-------------+------------+-------------+-----------------+---------------+--------------+------------+------------------+-----------------+-----------------+----------+-----------+
5 rows in set (0.00 sec)

system_process_stats

スレッド単位でCPU時間の統計が取れる。どのスレッドがビジーなのかわかる……にしたって、ユーザーコネクション( HeatWaveだとThreadPoolが有効なので (tp_connection) )がぶん回ってるように見えるだけのような気もする。

mysql> SELECT * FROM performance_schema.system_process_stats;
+---------------------+-------+--------------+---------+-------------------+-------+----------+----------+-----------+-----------+-------------+-------------+-------------+----------------------+-----------+--------------------+---------------+----------------+------------+-------------+
| TIMESTAMP           | PID   | PROCESS_NAME | TID     | THREAD_NAME       | STATE | UTIME_MS | STIME_MS | CUTIME_MS | CSTIME_MS | NUM_THREADS | VSIZE_BYTES | RSS_BYTES   | RSSLIM_BYTES         | PROCESSOR | DELAYACCT_BLKIO_MS | GUEST_TIME_MS | CGUEST_TIME_MS | READ_BYTES | WRITE_BYTES |
+---------------------+-------+--------------+---------+-------------------+-------+----------+----------+-----------+-----------+-------------+-------------+-------------+----------------------+-----------+--------------------+---------------+----------------+------------+-------------+
| 2025-04-13 02:40:42 | 32527 | mysqld       |   32527 | (mysqld)          | S     |     3130 |    10820 |         0 |         0 |          93 | 34276634624 | 22931099648 | 18446744073709551615 |         1 |                120 |             0 |              0 |    3420160 |      462848 |
| 2025-04-13 02:40:42 | 32527 | mysqld       |   32537 | (ib_io_ibuf)      | S     |     3030 |     5220 |         0 |         0 |           0 |           0 |           0 |                    0 |         0 |                  0 |             0 |              0 |          0 |           0 |
| 2025-04-13 02:40:42 | 32527 | mysqld       |   32538 | (ib_io_rd-1)      | S     |     3060 |     5200 |         0 |         0 |           0 |           0 |           0 |                    0 |         0 |                  0 |             0 |              0 |       4096 |           0 |
| 2025-04-13 02:40:42 | 32527 | mysqld       |   32539 | (ib_io_wr-1)      | S     |     2670 |     5600 |         0 |         0 |           0 |           0 |           0 |                    0 |         0 |                  0 |             0 |              0 |          0 |           0 |
| 2025-04-13 02:40:42 | 32527 | mysqld       |   32540 | (ib_io_wr-2)      | S     |     2770 |     5550 |         0 |         0 |           0 |           0 |           0 |                    0 |         0 |                  0 |             0 |              0 |       4096 |           0 |

..

どのスレッドがどの名前に属するかは performance_schema.threads から何となく紐づけられる。

mysql> SELECT name FROM performance_schema.threads WHERE thread_id = PS_CURRENT_THREAD_ID();
+--------------------------------------+
| name                                 |
+--------------------------------------+
| thread/thread_pool/tp_one_connection |
+--------------------------------------+
1 row in set (0.00 sec)

system_process_stats_history

system_process_stats のヒストリ版、ただし thread_name = '(mysqld)' だけ。

mysql> SELECT * FROM performance_schema.system_process_stats_history LIMIT 5;
+---------------------+-------+--------------+-------+-------------+-------+----------+----------+-----------+-----------+-------------+-------------+-------------+----------------------+-----------+--------------------+---------------+----------------+------------+-------------+
| TIMESTAMP           | PID   | PROCESS_NAME | TID   | THREAD_NAME | STATE | UTIME_MS | STIME_MS | CUTIME_MS | CSTIME_MS | NUM_THREADS | VSIZE_BYTES | RSS_BYTES   | RSSLIM_BYTES         | PROCESSOR | DELAYACCT_BLKIO_MS | GUEST_TIME_MS | CGUEST_TIME_MS | READ_BYTES | WRITE_BYTES |
+---------------------+-------+--------------+-------+-------------+-------+----------+----------+-----------+-----------+-------------+-------------+-------------+----------------------+-----------+--------------------+---------------+----------------+------------+-------------+
| 2025-04-12 02:45:09 | 32527 | mysqld       | 32527 | (mysqld)    | S     |     3050 |    10470 |         0 |         0 |          91 | 34274525184 | 24410550272 | 18446744073709551615 |         1 |                120 |             0 |              0 |    3108864 |      462848 |
| 2025-04-12 02:46:08 | 32527 | mysqld       | 32527 | (mysqld)    | S     |     3050 |    10470 |         0 |         0 |          91 | 34274525184 | 24410537984 | 18446744073709551615 |         1 |                120 |             0 |              0 |    3108864 |      462848 |
| 2025-04-12 02:47:08 | 32527 | mysqld       | 32527 | (mysqld)    | S     |     3050 |    10470 |         0 |         0 |          91 | 34274525184 | 24410513408 | 18446744073709551615 |         1 |                120 |             0 |              0 |    3108864 |      462848 |
| 2025-04-12 02:48:08 | 32527 | mysqld       | 32527 | (mysqld)    | S     |     3050 |    10470 |         0 |         0 |          91 | 34274525184 | 24410521600 | 18446744073709551615 |         1 |                120 |             0 |              0 |    3108864 |      462848 |
| 2025-04-12 02:49:08 | 32527 | mysqld       | 32527 | (mysqld)    | S     |     3050 |    10470 |         0 |         0 |          91 | 34274525184 | 24409808896 | 18446744073709551615 |         1 |                120 |             0 |              0 |    3108864 |      462848 |
+---------------------+-------+--------------+-------+-------------+-------+----------+----------+-----------+-----------+-------------+-------------+-------------+----------------------+-----------+--------------------+---------------+----------------+------------+-------------+
5 rows in set (0.00 sec)

登録: 投稿 ( Atom )

GA