MySQL Forums - Chinese

【报1错】data目录初始化时jemalloc.dll错1误提示 (no replies)

sir luo — Wed, 19 Nov 2025 02:36:59 +0000

操1作系1统：windows server 2008
安1装包：mysql-8.0.43-winx64.zip
解1压后执1行： [E1R1R1O1R] [1M1Y-013849] [Server] Load1LibraryEx("j1emalloc.dll", NULL, LOAD_LIBRARY_SEARCH_APPLICATION_DIR) failed with error code 87: "参1数1错1误。", using default malloc.

尝1试安1装MICROSOFT VISUAL C++ 2015 - 2022 RUNTIME
MICROSOFT VISUAL C++ 2019 RUNTIME

安1装后依1然存1在该报1错，但是启1动mysql后可以正1常创1建表和插1入数1据，这个错1误是1否会有什1么影1响，需1要怎1么处1理能解1决这个问1题呢

MySQL failue (no replies)

Tik Ho Hui — Mon, 18 Aug 2025 06:27:33 +0000

我的 notebook上的 MySQL 又 failure, 我想知道為何會 fail 得這般密 (數星期一次), 是不是我每天都 start 同 stop 所致 ?? 以下是 logging !!!

2025-08-18 14:17:58 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 18264
2025-08-18 14:17:58 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2025-08-18 14:17:58 0 [Note] InnoDB: Uses event mutexes
2025-08-18 14:17:58 0 [Note] InnoDB: Compressed tables use zlib 1.3
2025-08-18 14:17:58 0 [Note] InnoDB: Number of pools: 1
2025-08-18 14:17:58 0 [Note] InnoDB: Using SSE2 crc32 instructions
2025-08-18 14:17:58 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2025-08-18 14:17:58 0 [Note] InnoDB: Completed initialization of buffer pool
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=239] log sequence number 512606 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=380] log sequence number 512606 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=240] log sequence number 512650 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=369] log sequence number 512650 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=241] log sequence number 512694 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=381] log sequence number 512694 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=242] log sequence number 512738 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=382] log sequence number 512738 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=244] log sequence number 512782 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=383] log sequence number 512782 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=245] log sequence number 512826 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=384] log sequence number 512826 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=246] log sequence number 512870 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=385] log sequence number 512870 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=247] log sequence number 512914 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=386] log sequence number 512914 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=248] log sequence number 512958 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=387] log sequence number 512958 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=249] log sequence number 513002 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=370] log sequence number 513002 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=250] log sequence number 513062 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=371] log sequence number 513062 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=251] log sequence number 513106 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=388] log sequence number 513106 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=252] log sequence number 513150 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=389] log sequence number 513150 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=253] log sequence number 513194 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=372] log sequence number 513194 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=254] log sequence number 513238 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=390] log sequence number 513238 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=255] log sequence number 513282 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=391] log sequence number 513282 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=256] log sequence number 426708 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=392] log sequence number 426708 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=257] log sequence number 465143 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Page [page id: space=0, page number=393] log sequence number 465143 is in the future! Current system log sequence number 401246.
2025-08-18 14:17:58 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2025-08-18 14:17:58 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2025-08-18 14:17:58 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2025-08-18 14:17:58 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2025-08-18 14:17:58 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2025-08-18 14:17:58 0 [Note] InnoDB: Waiting for purge to start
2025-08-18 14:17:59 0 [Note] InnoDB: 10.4.32 started; log sequence number 401237; transaction id 2136
2025-08-18 14:17:59 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2025-08-18 14:17:59 0 [Note] Plugin 'FEEDBACK' is disabled.
2025-08-18 14:17:59 0 [Note] InnoDB: Buffer pool(s) load completed at 250818 14:17:59
2025-08-18 14:17:59 0 [Note] Server socket created on IP: '::'.

MYSQL failure (no replies)

Tik Ho Hui — Tue, 05 Aug 2025 03:58:24 +0000

我的 Mysql 經常無故 Failure, 我已經把 Windows 的 Fast Startup Turnoff 了, 但仍然發生, 以下是 Error Log : 請問為何會發生這些問題 ??

2025-08-05 11:36:59 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 21576
2025-08-05 11:36:59 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2025-08-05 11:36:59 0 [Note] InnoDB: Uses event mutexes
2025-08-05 11:36:59 0 [Note] InnoDB: Compressed tables use zlib 1.3
2025-08-05 11:36:59 0 [Note] InnoDB: Number of pools: 1
2025-08-05 11:36:59 0 [Note] InnoDB: Using SSE2 crc32 instructions
2025-08-05 11:36:59 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2025-08-05 11:36:59 0 [Note] InnoDB: Completed initialization of buffer pool
2025-08-05 11:36:59 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2025-08-05 11:36:59 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2025-08-05 11:36:59 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2025-08-05 11:36:59 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2025-08-05 11:36:59 0 [Note] InnoDB: Waiting for purge to start
2025-08-05 11:36:59 0 [Note] InnoDB: 10.4.32 started; log sequence number 534053; transaction id 1539
2025-08-05 11:36:59 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2025-08-05 11:36:59 0 [Note] Plugin 'FEEDBACK' is disabled.
2025-08-05 11:36:59 0 [Note] InnoDB: Buffer pool(s) load completed at 250805 11:36:59
2025-08-05 11:36:59 0 [Note] Server socket created on IP: '::'.
2025-08-05 11:36:59 0x20c8 InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\os\os0file.cc line 6132
InnoDB: Failing assertion: slot
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
2025-08-05 11:36:59 0x620c2025-08-05 11:36:59 0x6350 InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\os\os0file.cc line 6132
InnoDB: Failing assertion: slot
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
2025-08-05 11:37:03 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 2708
2025-08-05 11:37:03 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2025-08-05 11:37:03 0 [Note] InnoDB: Uses event mutexes
2025-08-05 11:37:03 0 [Note] InnoDB: Compressed tables use zlib 1.3
2025-08-05 11:37:03 0 [Note] InnoDB: Number of pools: 1
2025-08-05 11:37:03 0 [Note] InnoDB: Using SSE2 crc32 instructions
2025-08-05 11:37:03 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2025-08-05 11:37:03 0 [Note] InnoDB: Completed initialization of buffer pool
2025-08-05 11:37:03 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2025-08-05 11:37:03 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2025-08-05 11:37:03 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2025-08-05 11:37:03 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2025-08-05 11:37:03 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2025-08-05 11:37:03 0 [Note] InnoDB: Waiting for purge to start
2025-08-05 11:37:03 0 [Note] InnoDB: 10.4.32 started; log sequence number 534053; transaction id 1539
2025-08-05 11:37:03 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2025-08-05 11:37:03 0 [Note] Plugin 'FEEDBACK' is disabled.
2025-08-05 11:37:03 0 [Note] Server socket created on IP: '::'.

CVE-2025-21521漏洞如何解决 (no replies)

先生黄 — Thu, 20 Mar 2025 01:27:32 +0000

CVE-2025-21521漏洞如何解决?旧的mysql是5.7版本，是否只能升级mysql版本才能解决此问题

CVE-2025-21521漏洞如何解决 (no replies)

先生黄 — Tue, 18 Mar 2025 07:21:59 +0000

请问一下CVE-2025-21521漏洞如何解决？我现在mysql版本为5.7版本

节点切换后，数据节点不能立刻访问，需要等待近40秒，如何解决 (no replies)

XIELEI YANG — Wed, 08 Jan 2025 10:40:13 +0000

mysql-5.7.29 ndb-7.5.17

主机A，一个管理节点，数据节点和SQL节点。主用数据节点。
主机B，一个管理节点，数据节点和SQL节点。

将主机A重启，
主机B访问mysql报错 ERROR 1296 (HY000): Got error 4009 'Cluster Failure' from NDBCLUSTER
需要等待 40s左右，才可以正常访问

/usr/local/app/mysql-cluster/config.ini
[tcp default]
SendBufferMemory=2M
ReceiveBufferMemory=2M

[ndbd default]
NoOfReplicas=2 ## data num
DataMemory=2048M
IndexMemory=640M

LockPagesInMainMemory=1
NoOfFragmentLogFiles=300
SchedulerSpinTimer=400
SchedulerExecutionTimer=100
RealTimeScheduler=1
TimeBetweenGlobalCheckpoints=1000
TimeBetweenEpochs=200
RedoBuffer=32M
TimeBetweenLocalCheckpoints=6

MaxNoOfOrderedIndexes=512
MaxNoOfConcurrentOperations=100000

## mng
[ndb_mgmd]
NodeId=1
hostname=10.188.68.45
datadir=/usr/local/app/mysql-cluster/

[ndb_mgmd]
NodeId=2
hostname=10.188.68.46
datadir=/usr/local/app/mysql-cluster/

## data
[ndbd]
NodeId=11
hostname=10.188.68.45
datadir=/usr/local/app/mysql/data
StopOnError=0
StartPartialTimeout=1000
StartPartitionedTimeout=1000
TransactionDeadLockDetectionTimeOut=60000
[ndbd]
NodeId=12
hostname=10.188.68.46
datadir=/usr/local/app/mysql/data
StopOnError=0
StartPartialTimeout=1000
StartPartitionedTimeout=1000
TransactionDeadLockDetectionTimeOut=60000

## sql
[mysqld]
NodeId=21
hostname=10.188.68.45
[mysqld]
NodeId=22
hostname=10.188.68.46
[mysqld]

[mysqld]

请问这个查询的1055错误的导致原因 (no replies)

Kuandian Gan — Fri, 11 Oct 2024 07:22:59 +0000

select a,* from XXX 报错 (no replies)

kevin.tan tann — Sun, 06 Oct 2024 03:02:13 +0000

mysql> SELECT LENGTH(CAST(emp_no AS CHAR)) as emp_no_length,* FROM salaries limit 10;
运行时报错
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '* FROM salaries limit 10' at line 1
但
mysql> SELECT LENGTH(CAST(emp_no AS CHAR)) as emp_no_length,salaried.* FROM salaries limit 10;
运行正常

MySQL突然crash报错Error in `/usr/sbin/mysqld': double free or corruption (!prev): 0x00007fce8c0258e0 (no replies)

YINGYIFNEG YING — Thu, 12 Sep 2024 08:42:43 +0000

MySQL突然自动重启了，MySQL版本是8.0.27，且监控显示主机cpu内存都正常，数据库也没有做过变更。

以下是MySQL的error日志记录的相关信息，麻烦各位分析一下

*** Error in `/usr/sbin/mysqld': double free or corruption (!prev): 0x00007fce8c0258e0 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x81329)[0x7fda3bbb8329]
/usr/sbin/mysqld(_ZN8MEM_ROOT10FreeBlocksEPNS_5BlockE+0x23)[0x1fb9f43]
/usr/sbin/mysqld(_Z14free_tmp_tableP5TABLE+0x10b)[0xe5daab]
/usr/sbin/mysqld(_ZN4JOIN7destroyEv+0x2a9)[0xdfcad9]
/usr/sbin/mysqld(_ZN11Query_block7cleanupEP3THDb+0x75)[0xe6d755]
/usr/sbin/mysqld(_ZN16Query_expression7cleanupEP3THDb+0x8e)[0xe6d92e]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0xa8a)[0xd9c6da]
/usr/sbin/mysqld(_Z20dispatch_sql_commandP3THDP12Parser_state+0x412)[0xd9fdc2]
/usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0xe0e)[0xda10ee]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x194)[0xda3194]
/usr/sbin/mysqld[0xed9c70]
/usr/sbin/mysqld[0x248d630]
/lib64/libpthread.so.0(+0x7ea5)[0x7fda3d87aea5]
/lib64/libc.so.6(clone+0x6d)[0x7fda3bc35b0d]
======= Memory map: ========
00400000-037d0000 r-xp 00000000 08:02 1490 /usr/sbin/mysqld
037d0000-03945000 r--p 033cf000 08:02 1490 /usr/sbin/mysqld
03945000-03ccf000 rw-p 03544000 08:02 1490 /usr/sbin/mysqld
03ccf000-041f9000 rw-p 00000000 00:00 0
0565c000-0d2e0000 rw-p 00000000 00:00 0 [heap]
7fcac8000000-7fcae8000000 rw-p 00000000 00:00 0
7fcae8000000-7fcb08000000 rw-s 00000000 08:02 33562377 /tmp/#33562377 (deleted)
7fcb18000000-7fcb28000000 rw-s 00000000 08:02 33554525 /tmp/#33554525 (deleted)
7fcb38000000-7fcb60000000 rw-p 00000000 00:00 0
这一段有点长，类似的我直接跳到最后一段
7ffcc81c0000-7ffcc81c2000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
05:29:52 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x7fce8c003730
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7fcefb8fec70 thread_stack 0x100000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x3d) [0x1fc33bd]
/usr/sbin/mysqld(handle_fatal_signal+0x30b) [0xee902b]
/lib64/libpthread.so.0(+0xf630) [0x7fda3d882630]
/lib64/libc.so.6(gsignal+0x37) [0x7fda3bb6d387]
/lib64/libc.so.6(abort+0x148) [0x7fda3bb6ea78]
/lib64/libc.so.6(+0x78f67) [0x7fda3bbaff67]
/lib64/libc.so.6(+0x81329) [0x7fda3bbb8329]
/usr/sbin/mysqld(MEM_ROOT::FreeBlocks(MEM_ROOT::Block*)+0x23) [0x1fb9f43]
/usr/sbin/mysqld(free_tmp_table(TABLE*)+0x10b) [0xe5daab]
/usr/sbin/mysqld(JOIN::destroy()+0x2a9) [0xdfcad9]
/usr/sbin/mysqld(Query_block::cleanup(THD*, bool)+0x75) [0xe6d755]
/usr/sbin/mysqld(Query_expression::cleanup(THD*, bool)+0x8e) [0xe6d92e]
/usr/sbin/mysqld(mysql_execute_command(THD*, bool)+0xa8a) [0xd9c6da]
/usr/sbin/mysqld(dispatch_sql_command(THD*, Parser_state*)+0x412) [0xd9fdc2]
/usr/sbin/mysqld(dispatch_command(THD*, COM_DATA const*, enum_server_command)+0xe0e) [0xda10ee]
/usr/sbin/mysqld(do_command(THD*)+0x194) [0xda3194]
/usr/sbin/mysqld() [0xed9c70]
/usr/sbin/mysqld() [0x248d630]
/lib64/libpthread.so.0(+0x7ea5) [0x7fda3d87aea5]
/lib64/libc.so.6(clone+0x6d) [0x7fda3bc35b0d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fce8c0008e8): SELECT b.* FROM VIEW_SPLITER_WITH_NONULL_COORDINATE b WHERE (b.lat_radius >= 0.529081873335674e0 AND b.lat_radius <= 0.5291445879372011e0) AND (b.lon_radius >= 2.1001055711686654e0 and b.lon_radius <= 2.1001782201540538e0) AND acos(sin(0.5291132306364376e0) * sin(lat_radius) + cos(0.5291132306364376e0) * cos(b.lat_radius) * cos(b.lon_radius - 2.1001418956613596e0)) <= 3.135730076355027e-05 and exists(select 1 from org_area a left join region_space rm on a.area_id = rm.id left join department d on a.organize_id = d.id where d.id in (select d1.id from my_user_data_auth a left join my_user mu on a.user_id = mu.id left join department d1 on a.org_id = d1.id where a
Connection ID (thread ID): 154255880
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2024-09-12T13:30:01.270376+08:00 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.27-commercial) starting as process 25317
2024-09-12T13:30:01.290550+08:00 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-09-12T13:30:08.297337+08:00 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-09-12T13:30:12.090760+08:00 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2024-09-12T13:30:12.097686+08:00 0 [System] [MY-010232] [Server] XA crash recovery finished.
2024-09-12T13:30:14.108847+08:00 0 [Warning] [MY-013746] [Server] A deprecated TLS version TLSv1 is enabled for channel mysql_main
2024-09-12T13:30:14.108891+08:00 0 [Warning] [MY-013746] [Server] A deprecated TLS version TLSv1.1 is enabled for channel mysql_main
2024-09-12T13:30:14.111384+08:00 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-09-12T13:30:14.111451+08:00 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-09-12T13:30:14.165426+08:00 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.27-commercial' socket: '/tmp/mysql.sock' port: 3306 MySQL Enterprise Server - Commercial

mysql主从在数据透明加密过程中，从库发生了crash事件 (no replies)

YINGYIFNEG YING — Thu, 21 Mar 2024 11:00:22 +0000

MySQL版本：8.0.31

问题：主从复制架构上都install加载了加密插件后，主库执行了ALTER TABLE t1 ENCRYPTION='Y';加密命令，从库开始同步数据，同步到一张19G的临时表时，从库产生了crash。后手动拉起从库数据库，从库正常加密，数据同步正常。疑问为什么从库会发生crash？

具体的日志信息如下：
2024-03-20T02:30:02.446372+08:00 47611 [Warning] [MY-013712] [Server] No suitable 'keyring_component_metadata_query' service implementation found to fulfill the request.
2024-03-20T13:58:12Z UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=30a13d091dc0c69784b16dd4169f1382a73d2f9d
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x100000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x2128b81]
/usr/sbin/mysqld(print_fatal_signal(int)+0x387) [0xfd62d7]
/usr/sbin/mysqld(handle_fatal_signal+0xa5) [0xfd6395]
/lib64/libpthread.so.0(+0x12ce0) [0x7fa150c1ece0]
/usr/sbin/mysqld(rec_get_offsets(unsigned char const*, dict_index_t const*, unsigned long*, unsigned long, ut::Location, mem_block_info_t**)+0x22) [0x24309d2]
/usr/sbin/mysqld(btr_search_drop_page_hash_index(buf_block_t*)+0x4cc) [0x24710dc]
/usr/sbin/mysqld(buf_LRU_free_page(buf_page_t*, bool)+0x7c5) [0x24b5895]
/usr/sbin/mysqld(buf_flush_do_batch(buf_pool_t*, buf_flush_t, unsigned long, unsigned long, unsigned long*)+0xca6) [0x24a9936]
/usr/sbin/mysqld() [0x24aa09e]
/usr/sbin/mysqld() [0x24ac4fd]
/usr/sbin/mysqld(void Detached_thread::operator()(void (*&&)())+0xca) [0x22e78aa]
/lib64/libstdc++.so.6(+0xc2ba3) [0x7fa14f9a1ba3]
/lib64/libpthread.so.0(+0x81cf) [0x7fa150c141cf]
/lib64/libc.so.6(clone+0x43) [0x7fa14efb9d83]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2024-03-20T21:58:15.824852+08:00 0 [Warning] [MY-011070] [Server] 'Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it' is deprecated and will be removed in a future release.
2024-03-20T21:58:15.824897+08:00 0 [Warning] [MY-011069] [Server] The syntax '--master-info-repository' is deprecated and will be removed in a future release.
2024-03-20T21:58:15.824903+08:00 0 [Warning] [MY-011069] [Server] The syntax '--relay-log-info-repository' is deprecated and will be removed in a future release.
2024-03-20T21:58:15.824919+08:00 0 [Warning] [MY-011068] [Server] The syntax 'log_slave_updates' is deprecated and will be removed in a future release. Please use log_replica_updates instead.
2024-03-20T21:58:15.824934+08:00 0 [Warning] [MY-011068] [Server] The syntax 'slave_skip_errors' is deprecated and will be removed in a future release. Please use replica_skip_errors instead.
2024-03-20T21:58:15.824940+08:00 0 [Warning] [MY-011069] [Server] The syntax '--slave-rows-search-algorithms' is deprecated and will be removed in a future release.
2024-03-20T21:58:15.824951+08:00 0 [Warning] [MY-011069] [Server] The syntax '--replica-parallel-type' is deprecated and will be removed in a future release.
2024-03-20T21:58:15.824969+08:00 0 [Warning] [MY-011070] [Server] 'Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it' is deprecated and will be removed in a future release.
2024-03-20T21:58:15.825983+08:00 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.31) starting as process 787138
2024-03-20T21:58:15.850478+08:00 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-03-20T21:58:16.364389+08:00 1 [ERROR] [MY-012657] [InnoDB] Encryption can't find master key, please check the keyring is loaded.
2024-03-20T21:58:16.364430+08:00 1 [ERROR] [MY-012226] [InnoDB] Encryption information in datafile: ./icm/#sql-a278f_9.ibd can't be decrypted, please confirm that keyring is loaded.
2024-03-20T21:58:16.898658+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 0 for {space: 1615, page_no:390535} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898686+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 1 for {space: 1615, page_no:303826} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898692+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 2 for {space: 1615, page_no:382794} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898697+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 3 for {space: 1615, page_no:260842} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898702+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 4 for {space: 1615, page_no:332990} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898707+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 5 for {space: 1615, page_no:316131} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898712+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 6 for {space: 1615, page_no:11504} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898717+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 7 for {space: 1615, page_no:263396} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898722+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 8 for {space: 1615, page_no:384707} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898735+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 9 for {space: 1615, page_no:445810} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898740+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 10 for {space: 1615, page_no:215338} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898747+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 11 for {space: 1615, page_no:234022} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898752+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 12 for {space: 1615, page_no:49176} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898757+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 13 for {space: 1615, page_no:280063} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898762+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 14 for {space: 1615, page_no:106606} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898766+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 15 for {space: 1615, page_no:39945} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898772+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 16 for {space: 1615, page_no:445811} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898776+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 17 for {space: 1615, page_no:71416} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898781+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 18 for {space: 1615, page_no:71344} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898786+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 19 for {space: 1615, page_no:437571} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898791+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 20 for {space: 1615, page_no:402287} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898796+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 21 for {space: 1615, page_no:297545} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898801+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 22 for {space: 1615, page_no:310188} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898806+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 23 for {space: 1615, page_no:49348} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898811+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 24 for {space: 1615, page_no:191608} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898816+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 25 for {space: 1615, page_no:282704} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898820+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 26 for {space: 1615, page_no:160972} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898825+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 27 for {space: 1615, page_no:55215} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898830+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 28 for {space: 1615, page_no:381013} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898835+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 29 for {space: 1615, page_no:453898} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898840+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 30 for {space: 1615, page_no:476051} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898846+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 31 for {space: 1615, page_no:447088} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898851+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 32 for {space: 1615, page_no:360299} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898855+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 33 for {space: 1615, page_no:402264} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898863+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 34 for {space: 1615, page_no:281424} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898868+08:00 1 [Warning] [MY-013541] [InnoDB] Doublewrite page 35 for {space: 1615, page_no:280052} could not be restored. File name unknown for tablespace ID 1615
2024-03-20T21:58:16.898931+08:00 1 [ERROR] [MY-012179] [InnoDB] Could not find any file associated with the tablespace ID: 1615
2024-03-20T21:58:16.898941+08:00 1 [ERROR] [MY-012964] [InnoDB] Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)
2024-03-20T21:58:16.999256+08:00 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
2024-03-20T21:58:17.288414+08:00 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2024-03-20T21:58:17.288809+08:00 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2024-03-20T21:58:17.288891+08:00 0 [ERROR] [MY-010119] [Server] Aborting
2024-03-20T21:58:17.290497+08:00 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.31) MySQL Community Server - GPL.

自学者多长时间可以开始从事测试或开发相关岗位的工作 (no replies)

Ivy Inka — Thu, 30 Nov 2023 03:10:47 +0000

我是女生想知道花上几个月不工作学习开发（不报班），能有资格去做一名开发或者测试吗，专升本...
或者有没有人能提供一些可能性呢
迷茫

请问论坛管理员的联系方式 (no replies)

xie xie — Tue, 15 Aug 2023 03:22:41 +0000

我发了一个帖子，但是系统显示：“A word you have used in your post has been banned from use. Please use a different word or contact the forum administrators.”，想联系下管理员，看问题出在哪？请问管理员如何联系？谢谢。

mysql mgr新成员加入组问题之新成员无法通过二进制日志从其它可用成员同步数据 (no replies)

liu my — Sun, 06 Aug 2023 20:21:12 +0000

1、我原来只有一个数据库服务A，通过执行数据备份同时刷新二进制日志。
mysqldump --single-transaction --flush-logs --master-data=2 --all-databases > backup_date.sql
这时刷新后的binlog日志名称为mysql000010，位置323，备份后的数据变动都在该新biglog文件后。
然后配置相关mysql mgr变量，A服务作为引导启动，并且启动成功。
2、搭建数据库服务B，并且配置mysql mgr组复制相关配置，导入刚从数据库服务A的备份。清除日志。启动组复制，报错“Plugin group_replication reported: 'This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.'” 数据库服务B的组复制中的分布式恢复从数据库服务A的bin.000001 文件开始恢复数据，但数据库服务A这个对应的二进制文件已经转移到其它库了，并且数据库服务B也不需要从bin.000001开始恢复数据，而是需要从这个备份数据后的新二进制文件开始从组中其他成员恢复数据，请问如何解决这个问题？

ICP中explain key-lenth和OPTIMIZER_TRACE中refine_plan展示信息不对称问题 (no replies)

yijie fu — Wed, 07 Sep 2022 10:45:13 +0000

情况1:
索引：ALTER TABLE t_app_recommended_info ADD INDEX idx_uid_create_time_type (uid,create_time,type);
查询条件：select * from t_app_recommended_info where uid = 1252057754179211264 and create_time >'2022-09-01 00:00:00' and type =1 and params like '%"couponId":12582268875%' and params like '%"hmsr":"saomaqudao"%';
explain:key-len=12

OPTIMIZER_TRACE:refine_plan: "pushed_index_condition": "((`t_app_recommended_info`.`type` = 1) and (`t_app_recommended_info`.`uid` = 1252057754179211264) and (`t_app_recommended_info`.`create_time` > '2022-09-01 00:00:00'))",
情况2:
索引：ALTER TABLE t_app_recommended_info ADD INDEX idx_uid_type_createtime (uid,type,create_time);
查询条件：select * from t_app_recommended_info where uid = 1252057754179211264 and create_time >'2022-09-01 00:00:00' and type =1 and params like '%"couponId":12582268875%' and params like '%"hmsr":"saomaqudao"%';
explain:key-len=16

OPTIMIZER_TRACE:refine_plan: "pushed_index_condition": "((`t_app_recommended_info`.`type` = 1) and (`t_app_recommended_info`.`uid` = 1252057754179211264) and (`t_app_recommended_info`.`create_time` > '2022-09-01 00:00:00'))",
根据情况1和情况2的explain的key-len发现type（4字节）未使用到，但是根据OPTIMIZER_TRACE:refine_plan: 又发现使用到了，求解惑，怀疑是key-len的解释又问题，求大佬解释

mysql二进制日志（binglog）能否分开记录不同库的信息 (no replies)

Pingliang Liu — Thu, 05 May 2022 14:44:42 +0000

现在MySQL数据库中有创建了两库，库1，和库2，开启二进制日志后，不管是库1还是库2的信息都记录到同一个二进制日志。我现在想让库1的信息单独记录在一个二进制日志中，库2的信息单独记录在二进制日志中，二不是同一个二进制日志。这能否实现，如果要实现要怎么实现，求解。

json结合生成列索引，查询结果不一致，是否正确？ (4 replies)

Chen WeiXin — Mon, 09 May 2022 20:02:41 +0000

1.两种表现
1.1 这是能够查询到结果的SQL：
drop table jemp;
create table jemp(c json, g int generated always as (c->"$.id")) ;
create index idx1 on jemp(g);
insert into jemp(c) values('{"id":"1", "name":"Fred"}');
select c from jemp where c->'$.id' = 1;
mysql> explain select c from jemp where c->'$.id' = 1;
+----+-------------+-------+------------+------+---------------+------+---------+-------+------+----------+-------+
| id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
+----+-------------+-------+------------+------+---------------+------+---------+-------+------+----------+-------+
| 1 | SIMPLE | jemp | NULL | ref | idx1 | idx1 | 5 | const | 1 | 100.00 | NULL |
+----+-------------+-------+------------+------+---------------+------+---------+-------+------+----------+-------+
1 row in set, 1 warning (0.00 sec)

mysql> show warnings;
+-------+------+----------------------------------------------------------------------------------------------------+
| Level | Code | Message |
+-------+------+----------------------------------------------------------------------------------------------------+
| Note | 1003 | /* select#1 */ select `mysql`.`jemp`.`c` AS `c` from `mysql`.`jemp` where (`mysql`.`jemp`.`g` = 1) |
+-------+------+----------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

1.2 这是查询不到结果的SQL
drop table jemp;
create table jemp(c json, g int generated always as (c->"$.id")) ;
insert into jemp(c) values('{"id":"1", "name":"Fred"}');
select c from jemp where c->'$.id' = 1;
mysql> explain select c from jemp where c->'$.id' = 1;
+----+-------------+-------+------------+------+---------------+------+---------+------+------+----------+-------------+
| id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
+----+-------------+-------+------------+------+---------------+------+---------+------+------+----------+-------------+
| 1 | SIMPLE | jemp | NULL | ALL | NULL | NULL | NULL | NULL | 1 | 100.00 | Using where |
+----+-------------+-------+------------+------+---------------+------+---------+------+------+----------+-------------+
1 row in set, 1 warning (0.00 sec)

mysql> show warnings;
+-------+------+-------------------------------------------------------------------------------------------------------------------------+
| Level | Code | Message |
+-------+------+-------------------------------------------------------------------------------------------------------------------------+
| Note | 1003 | /* select#1 */ select `mysql`.`jemp`.`c` AS `c` from `mysql`.`jemp` where (json_extract(`mysql`.`jemp`.`c`,'$.id') = 1) |
+-------+------+-------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

2.原因
在有生成列索引的时候，优化器将where条件后的语句识别成生成列，然后走生成列索引查询；在没有生成列索引的时候，将整个where条件下压过滤，由于c->'$.id'查询到的是json，json string和1比较，将1 cast成json int，json string 大于json int，被过滤掉。

3.疑问
同一条SQL语句，有索引和没有索引查询结果不一致，这合理吗？
如果用户开始没有建立生成列索引，开始都是查询不到，某一天建立了生成列索引，突然查询到了结果，那不是很大可能影响生产？

mysql不定时的挂掉，然后莫名其妙的恢复正常访问 (no replies)

bc a — Sat, 23 Apr 2022 07:38:25 +0000

mysql8.0.27 centos8,0
每隔几天，mysql就链接不上，所有应用程序都报“wait millis 60000，active 1, maxActive 200，create 1, createElapseMillis 171626”，使用mysql -uxxx -p输入密码后确定，没有响应，没有返回结果。过30分钟或1个小时服务器自己可以恢复正常，程序连接上10+，内存16G，使用2G，1T硬盘，防火墙是关闭状态。请问有人遇见过没，望解答。

mysql 的where +单独列的问题。 (3 replies)

zhiqiang bai — Thu, 27 Jan 2022 04:40:16 +0000

select * from table where col;和select * from table;
到底有什么区别？区别在哪里？ select * from table where col;为什么会被执行成功，不报错。
有哪位大佬帮忙解答下，十分感谢。

【求助】MySQL8.0查询语句错误 (1 reply)

fei xu — Sun, 16 Jan 2022 15:08:54 +0000

MySQL8.0

-- DDL

CREATE TABLE `a3_category` (
`ID` bigint NOT NULL AUTO_INCREMENT,
`NAME` varchar(64) DEFAULT NULL,
PRIMARY KEY (`ID`)
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb3

CREATE TABLE `a3_item` (
`ID` bigint NOT NULL DEFAULT '0',
`IS_ACTIVE` int NOT NULL DEFAULT '1',
`CATEGORY` bigint NOT NULL,
`ICON` mediumtext COMMENT,
`NAME` varchar(64) NOT NULL,
`CODE` varchar(36) DEFAULT NULL,
`MEMBER_ID` bigint DEFAULT NULL,
`IS_DELETED` int NOT NULL DEFAULT '0',
PRIMARY KEY (`ID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb3

-- DML

INSERT INTO test.a3_item (ID, IS_ACTIVE, CATEGORY, ICON, NAME, CODE, MEMBER_ID, IS_DELETED) VALUES (-10, 1, -1, '1', 'mock1', 'mock1', 0, 0);
INSERT INTO test.a3_item (ID, IS_ACTIVE, CATEGORY, ICON, NAME, CODE, MEMBER_ID, IS_DELETED) VALUES (-9, 1, -1, '2', 'mock2', 'mock2', 0, 0);
INSERT INTO test.a3_item (ID, IS_ACTIVE, CATEGORY, ICON, NAME, CODE, MEMBER_ID, IS_DELETED) VALUES (-8, 1, -1, '3', 'mock3', 'mock3', 0, 0);
INSERT INTO test.a3_item (ID, IS_ACTIVE, CATEGORY, ICON, NAME, CODE, MEMBER_ID, IS_DELETED) VALUES (-7, 1, -2, '4', 'mock4', 'mock4', 0, 0);
INSERT INTO test.a3_item (ID, IS_ACTIVE, CATEGORY, ICON, NAME, CODE, MEMBER_ID, IS_DELETED) VALUES (-6, 1, -1, '5', 'mock5', 'mock5', 0, 0);
INSERT INTO test.a3_item (ID, IS_ACTIVE, CATEGORY, ICON, NAME, CODE, MEMBER_ID, IS_DELETED) VALUES (-5, 1, -1, '6', 'mock6', 'mock6', 0, 0);
INSERT INTO test.a3_item (ID, IS_ACTIVE, CATEGORY, ICON, NAME, CODE, MEMBER_ID, IS_DELETED) VALUES (-4, 1, -1, '7', 'mock7', 'mock7', 0, 0);
INSERT INTO test.a3_item (ID, IS_ACTIVE, CATEGORY, ICON, NAME, CODE, MEMBER_ID, IS_DELETED) VALUES (-3, 1, -1, '8', 'mock8', 'mock8', 0, 0);
INSERT INTO test.a3_item (ID, IS_ACTIVE, CATEGORY, ICON, NAME, CODE, MEMBER_ID, IS_DELETED) VALUES (-2, 1, -1, '9', 'mock9', 'mock9', 0, 0);
INSERT INTO test.a3_item (ID, IS_ACTIVE, CATEGORY, ICON, NAME, CODE, MEMBER_ID, IS_DELETED) VALUES (-1, 1, -1, '0', 'mock10', 'mock10', 0, 0);

INSERT INTO test.a3_category (ID, NAME) VALUES (1, 'IT Service');
INSERT INTO test.a3_category (ID, NAME) VALUES (2, 'Asset Service');

-- QUERY SQL
select count(1)
from a3_item item
join (select max(ID) ID
from a3_item
where IS_DELETED = 0
and IS_ACTIVE = 1
group by code
union
select max(ID) ID
from a3_item
where IS_DELETED = 0
group by code
having max(IS_ACTIVE) = 0) latest on latest.ID = item.ID
join a3_category on item.CATEGORY = a3_category.ID
where item.IS_DELETED = 0
and item.CATEGORY = 1
and (item.MEMBER_ID = 1 or item.MEMBER_ID = 0);

-- ERROR INFO
[08S01] Communications link failure The last packet successfully received from the server was 58 milliseconds ago. The last packet sent successfully to the server was 58 milliseconds ago. Communications link fail ...

服务器上运行SQL比笔记本还慢几百倍 (1 reply)

Herems Jing — Mon, 25 Oct 2021 09:14:16 +0000

服务器配置是：windows server, Xeon E5-2670 v3 2.3GHz + 8G内存。笔记本电脑是i7-8565U 1.8GHz + 8G内存.
mysql版本是一样的，v5.7.0，服务器的数据是从笔记本的mysqldump导进来的。
但是运行同样的语句，服务器比笔记本还慢很多。
比如跑一个语句，服务器要756秒，笔记本只要2.7秒。语句是“update a , b set a.tid=b.tid, a.tname=b.tname where a.m=b.m and (a.tid<>b.tid or a.tname<>b.tname)” 。表a有55万条记录，表b有200多条。
请教是什么原因导致的？该如何优化呢？

我有一个mysql相关博客（MySQL研究院）怎么关联到Planet MySQL呢 (no replies)

school MySQL — Wed, 11 Aug 2021 01:24:05 +0000

我有一个mysql相关博客（MySQL研究院）怎么关联到Planet MySQL呢，MySQL知识星球好像就是关联相关博客的呀

mysql官方的论坛人这么少吗 (no replies)

school MySQL — Tue, 10 Aug 2021 02:34:22 +0000

mysql官方的论坛人这么少吗,有没有人知道怎么在MySQL知识星球发文章呀

Planet MySQL（mysql知识星球）怎么发布文章啊 (no replies)

school MySQL — Tue, 10 Aug 2021 02:25:03 +0000

Planet MySQL（mysql知识星球）怎么发布文章啊？没看到入口啊

mysql8.0.16 Slow query (1 reply)

东山邢 — Wed, 04 Aug 2021 08:02:40 +0000

Querying both conditions is very slow.But two criteria alone are fast.
mysql> select count(1) from meteorological_data where create_time between '2021-07-28 00:00:00' and '2021-08-04 00:00:00' ;
+----------+
| count(1) |
+----------+
| 101627 |
+----------+
1 row in set (0.07 sec)

mysql> select count(1) from meteorological_data where equipment_no = 1000000195;
+----------+
| count(1) |
+----------+
| 45817 |
+----------+
1 row in set (0.08 sec)

mysql> select count(1) from meteorological_data where equipment_no = 1000000195 and create_time between '2021-07-28 00:00:00' and '2021-08-04 00:00:00';
+----------+
| count(1) |
+----------+
| 14 |
+----------+
1 row in set (19.71 sec)

What causes the pattern to be narrow?

库表在运行期间反复消失，重启数据库后又出现 (2 replies)

jm L — Fri, 12 Mar 2021 01:44:45 +0000

库表在运行期间反复消失

无法安装 (no replies)

Yunxi Yu — Tue, 09 Mar 2021 04:43:32 +0000

Macbook Windows状态下无法安装跟启用MySQL，怎么办

mtr用例main.mysql_binary_mode失败 (no replies)

linfeng chen — Mon, 02 Nov 2020 01:40:49 +0000

-INSERT INTO `A
-B` VALUES("A
+INSERT INTO `A
+B` VALUES("A
B");
-SELECT HEX(c1) FROM `A
+SELECT HEX(c1) FROM `A
B`;
HEX(c1)
410042
410D0A42

FLUSH LOGS;
-DROP TABLE `A
+DROP TABLE `A
B`;

RESET MASTER;
@@ -36,13 +36,13 @@
# In binary_mode, table name '0x410D0A42' and string '0x410042' can be
# handled correctly.
RESET MASTER;
-SELECT HEX(c1) FROM `A
+SELECT HEX(c1) FROM `A
B`;
HEX(c1)
410042
提示显示结果不对，显示隐藏字符后，发现执行结果文件里面有^M字符，mysql版本8.0.20,centos系统。

菜鸟新人 (no replies)

cheng Luo — Tue, 13 Oct 2020 02:57:06 +0000

SELECT json_extract('{"name":"abc"}','$.name');
mysql版本5.7.28 json解析后的数据为空，求解

开发者 (no replies)

sssss yzw — Thu, 17 Sep 2020 03:37:48 +0000

mysql8.0.20的优化器进行选择索引的时候不会考虑到索引下推吗

MySQL (1 reply)

biao yang — Mon, 14 Sep 2020 14:21:35 +0000

使用INSERT语句可能需要客户端/服务器DBMS中的特定安全权限。
请问这个特定安全权限怎么设置呀？