greatsql的docker不定期的自动重启
greatsql的docker版本8.0.32-25，操作系统是麒麟V10，目前情况是docker无法正常运行，不定期的重启，错误日志如下2025-02-21T11:14:24.028248+08:00 3288 'wait_timeout' period of 600 seconds was exceeded for `root`@`%`. The idle time since last command was too long.
2025-02-21T11:14:24.028409+08:00 3288 Aborted connection 3288 to db: 'oscape_db' user: 'root' host: '127.0.0.1' (The client was disconnected by the server because of inactivity.).
2025-02-21T11:15:00.012782+08:00 3303 Assertion failure: row0pread.cc:1350:is_queue_empty() thread 281465153449856
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: about forcing recovery.
2025-02-21T03:15:00Z UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID=bc39de400860a943996e7b04e4952d1d68b3ff6d
Build ID: Not Available
Server Version: 8.0.32-25 GreatSQL (GPL), Release 25, Revision 79f57097e3f
Thread pointer: 0xfffcf800bc20
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 = fffdb67ce5e8 thread_stack 0x80000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x30)
/usr/sbin/mysqld(print_fatal_signal(int)+0x360)
/usr/sbin/mysqld(my_server_abort()+0x90)
/usr/sbin/mysqld(my_abort()+0x14)
/usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x26c)
/usr/sbin/mysqld(Parallel_reader::dispatch_ctx(row_prebuilt_t*)+0x3b0)
/usr/sbin/mysqld(ha_innobase::pq_worker_scan_next(void*, unsigned char*)+0x11c)
/usr/sbin/mysqld(handler::ha_pq_next(unsigned char*, void*)+0x224)
/usr/sbin/mysqld(PQblockScanIterator::Read()+0x24)
/usr/sbin/mysqld(FilterIterator::Read()+0x28)
/usr/sbin/mysqld(NestedLoopIterator::Read()+0xd0)
/usr/sbin/mysqld(Query_expression::ExecuteIteratorQuery(THD*)+0x2f8)
/usr/sbin/mysqld(pq_worker_exec(void*)+0x74)
/usr/sbin/mysqld()
/lib64/libpthread.so.0(+0x7898)
/lib64/libc.so.6(+0xd1ddc)
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (fffd6838c570): is an invalid pointer
Connection ID (thread ID): 3303
Status: NOT_KILLED
Please help us make Percona Server better by reporting any
bugs at https://bugs.percona.com/
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
2025-02-21T11:15:00.937810+08:00 0 The syntax 'log_slow_slave_statements' is deprecated and will be removed in a future release. Please use log_slow_replica_statements instead.
2025-02-21T11:15:00.937853+08:00 0 The syntax 'slave_parallel_type' is deprecated and will be removed in a future release. Please use replica_parallel_type instead.
2025-02-21T11:15:00.937861+08:00 0 The syntax '--replica-parallel-type' is deprecated and will be removed in a future release.
2025-02-21T11:15:00.937873+08:00 0 The syntax 'slave_parallel_workers' is deprecated and will be removed in a future release. Please use replica_parallel_workers instead.
2025-02-21T11:15:00.937885+08:00 0 The syntax 'slave_preserve_commit_order' is deprecated and will be removed in a future release. Please use replica_preserve_commit_order instead.
2025-02-21T11:15:00.937896+08:00 0 The syntax 'slave_checkpoint_period' is deprecated and will be removed in a future release. Please use replica_checkpoint_period instead.
2025-02-21T11:15:00.938019+08:00 0 The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead.
2025-02-21T11:15:00.938480+08:00 0 Insecure configuration for --secure-log-path: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2025-02-21T11:15:00.938527+08:00 0 BuildID=bc39de400860a943996e7b04e4952d1d68b3ff6d
2025-02-21T11:15:00.938535+08:00 0 Basedir set to /usr/.
2025-02-21T11:15:00.938547+08:00 0 /usr/sbin/mysqld (mysqld 8.0.32-25) starting as process 1
2025-02-21T11:15:00.958668+08:00 0 option 'innodb-autoextend-increment': unsigned value 1073741824 adjusted to 1000.
2025-02-21T11:15:00.959917+08:00 0 Using Linux native AIO
2025-02-21T11:15:00.959954+08:00 0 Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.
2025-02-21T11:15:00.960282+08:00 0 Plugin 'FEDERATED' is disabled.
2025-02-21T11:15:00.960361+08:00 0 Plugin 'ndbcluster' is disabled.
2025-02-21T11:15:00.960385+08:00 0 Plugin 'ndbinfo' is disabled.
2025-02-21T11:15:00.960401+08:00 0 Plugin 'ndb_transid_mysql_connection_map' is disabled.
2025-02-21T11:15:00.961906+08:00 1 InnoDB initialization has started.
2025-02-21T11:15:00.961955+08:00 1 Atomic write enabled
2025-02-21T11:15:00.961989+08:00 1 PUNCH HOLE support available
2025-02-21T11:15:00.962007+08:00 1 Uses event mutexes
2025-02-21T11:15:00.962018+08:00 1 GCC builtin __atomic_thread_fence() is used for memory barrier
2025-02-21T11:15:00.962029+08:00 1 Compressed tables use zlib 1.2.13
2025-02-21T11:15:00.963177+08:00 1 File purge : set file purge path : /data/GreatSQL/#file_purge
2025-02-21T11:15:00.963248+08:00 1 Using hardware accelerated crc32 and polynomial multiplication.
2025-02-21T11:15:00.963570+08:00 1 Directories to scan './'
2025-02-21T11:15:00.963613+08:00 1 Scanning './'
2025-02-21T11:15:00.982627+08:00 1 Completed space ID check of 1154 files.
2025-02-21T11:15:00.983454+08:00 1 Initializing buffer pool, total size = 1.000000G, instances = 8, chunk size =128.000000M
2025-02-21T11:15:01.008721+08:00 1 Completed initialization of buffer pool
2025-02-21T11:15:01.012392+08:00 0 If the mysqld execution user is authorized, page cleaner and LRU manager thread priority can be changed. See the man page of setpriority().
2025-02-21T11:15:01.013161+08:00 1 Using './#ib_16384_0.dblwr' for doublewrite
2025-02-21T11:15:01.013595+08:00 1 Using './#ib_16384_1.dblwr' for doublewrite
2025-02-21T11:15:01.019294+08:00 1 Double write buffer files: 2
2025-02-21T11:15:01.019328+08:00 1 Double write buffer pages per instance: 4
2025-02-21T11:15:01.019364+08:00 1 Using './#ib_16384_0.dblwr' for doublewrite
2025-02-21T11:15:01.019388+08:00 1 Using './#ib_16384_1.dblwr' for doublewrite
2025-02-21T11:15:01.066718+08:00 1 The latest found checkpoint is at lsn = 557059052775 in redo log file ./#innodb_redo/#ib_redo2200.
2025-02-21T11:15:01.066778+08:00 1 The log sequence number 363361311611 in the system tablespace does not match the log sequence number 557059052775 in the redo log files!
2025-02-21T11:15:01.066794+08:00 1 Database was not shutdown normally!
2025-02-21T11:15:01.066806+08:00 1 Starting crash recovery.
2025-02-21T11:15:01.067391+08:00 1 Starting to parse redo log at lsn = 557059052676, whereas checkpoint_lsn = 557059052775 and start_lsn = 557059052544
2025-02-21T11:15:01.148101+08:00 1 Doing recovery: scanned up to log sequence number 557064048813
2025-02-21T11:15:01.203333+08:00 1 Log background threads are being started...
2025-02-21T11:15:01.203710+08:00 1 Applying a batch of 924 redo log records ...
2025-02-21T11:15:01.207747+08:00 1 10%
2025-02-21T11:15:01.208329+08:00 1 20%
2025-02-21T11:15:01.208372+08:00 1 30%
2025-02-21T11:15:01.208397+08:00 1 40%
2025-02-21T11:15:01.208742+08:00 1 50%
2025-02-21T11:15:01.211731+08:00 1 60%
2025-02-21T11:15:01.212116+08:00 1 70%
2025-02-21T11:15:01.212227+08:00 1 80%
2025-02-21T11:15:01.212257+08:00 1 90%
2025-02-21T11:15:01.212790+08:00 1 100%
2025-02-21T11:15:01.713353+08:00 1 Apply batch completed!
2025-02-21T11:15:02.424180+08:00 1 Using undo tablespace './undo_001'.
2025-02-21T11:15:02.424299+08:00 1 Using undo tablespace './undo_002'.
2025-02-21T11:15:02.424611+08:00 1 Opened 2 existing undo tablespaces.
2025-02-21T11:15:02.424673+08:00 1 GTID recovery trx_no: 395895090
2025-02-21T11:15:02.426136+08:00 1 Parallel initialization of rseg complete
2025-02-21T11:15:02.426167+08:00 1 Time taken to initialize rseg using 4 thread: 1496 ms.
2025-02-21T11:15:02.426934+08:00 1 Removed temporary tablespace data file: "ibtmp1"
2025-02-21T11:15:02.426955+08:00 1 Creating shared tablespace for temporary tables
2025-02-21T11:15:02.427007+08:00 1 Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2025-02-21T11:15:02.511468+08:00 1 File './ibtmp1' size is now 12 MB.
2025-02-21T11:15:02.511573+08:00 1 Scanning temp tablespace dir:'./#innodb_temp/'
2025-02-21T11:15:02.697290+08:00 1 Created 128 and tracked 128 new rollback segment(s) in the temporary tablespace. 128 are now active.
2025-02-21T11:15:02.697504+08:00 1 Percona XtraDB (http://www.percona.com) 8.0.32-23 started; log sequence number 557064048823
2025-02-21T11:15:02.697629+08:00 1 InnoDB initialization has ended.
2025-02-21T11:15:02.701091+08:00 1 Data dictionary restarting version '80023'.
2025-02-21T11:15:02.795907+08:00 1 Reading DD tablespace files
2025-02-21T11:15:02.883535+08:00 1 Scanned 1156 tablespaces. Validated 1156.
2025-02-21T11:15:02.985349+08:00 1 Using data dictionary with version '80023'.
2025-02-21T11:15:03.013169+08:00 0 Plugin mysqlx reported: 'IPv6 is available'
2025-02-21T11:15:03.013929+08:00 0 Plugin mysqlx reported: 'X Plugin ready for connections. bind-address: '::' port: 33060'
2025-02-21T11:15:03.013958+08:00 0 Plugin mysqlx reported: 'X Plugin ready for connections. socket: '/var/lib/mysql/mysqlx.sock''
2025-02-21T11:15:03.127497+08:00 0 Recovering after a crash using /data/GreatSQL/binlog
2025-02-21T11:15:05.436548+08:00 0 Starting XA crash recovery...
2025-02-21T11:15:05.439095+08:00 0 Crash recovery finished in binlog engine. No attempts to commit, rollback or prepare any transactions.
2025-02-21T11:15:05.439147+08:00 0 Crash recovery finished in InnoDB engine. No attempts to commit, rollback or prepare any transactions.
2025-02-21T11:15:05.439159+08:00 0 XA crash recovery finished.
2025-02-21T11:15:05.443347+08:00 0 DDL log recovery : begin
2025-02-21T11:15:05.443491+08:00 0 DDL log recovery : end
2025-02-21T11:15:05.444006+08:00 0 Loading buffer pool(s) from /data/GreatSQL/ib_buffer_pool
2025-02-21T11:15:05.447871+08:00 0 GTID compression after recovery.
2025-02-21T11:15:05.451370+08:00 0 Waiting for purge to start
2025-02-21T11:15:05.677060+08:00 0 Buffer pool(s) load completed at 250221 11:15:05
2025-02-21T11:15:08.059170+08:00 0 Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2025-02-21T11:15:08.059303+08:00 0 Skipping generation of SSL certificates as certificate files are present in data directory.
2025-02-21T11:15:08.060242+08:00 0 CA certificate ca.pem is self signed.
2025-02-21T11:15:08.060278+08:00 0 Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2025-02-21T11:15:08.060313+08:00 0 Skipping generation of RSA key pair through --sha256_password_auto_generate_rsa_keys as key files are present in data directory.
2025-02-21T11:15:08.060327+08:00 0 Skipping generation of RSA key pair through --caching_sha2_password_auto_generate_rsa_keys as key files are present in data directory.
2025-02-21T11:15:08.060459+08:00 0 Server hostname (bind-address): '*'; port: 3306
2025-02-21T11:15:08.060506+08:00 0 IPv6 is available.
2025-02-21T11:15:08.060519+08:00 0 - '::' resolves to '::';
2025-02-21T11:15:08.060535+08:00 0 Server socket created on IP: '::'.
2025-02-21T11:15:08.074892+08:00 0 Insecure configuration for --pid-file: Location '/data/GreatSQL' in the path is accessible to all OS users. Consider choosing a different directory.
2025-02-21T11:15:08.077777+08:00 0 unknown variable 'loose-gdb_parallel_load=1'.
2025-02-21T11:15:08.106399+08:00 0 Failed to start slave threads for channel ''.
2025-02-21T11:15:08.108261+08:00 7 Event Scheduler: scheduler thread started with id 7
2025-02-21T11:15:08.108276+08:00 0 /usr/sbin/mysqld: ready for connections. Version: '8.0.32-25'socket: '/data/GreatSQL/mysql.sock'port: 3306GreatSQL (GPL), Release 25, Revision 79f57097e3f.
2025-02-21T11:15:08.108368+08:00 0 Plugin mysqlx reported: 'Using SSL configuration from MySQL Server'
2025-02-21T11:15:08.108960+08:00 0 Plugin mysqlx reported: 'Using OpenSSL for TLS connections'
2025-02-21T11:15:08.109084+08:00 0 X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/lib/mysql/mysqlx.sock
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
2025-02-21T13:30:00.013859+08:00 220 Assertion failure: row0pread.cc:1350:is_queue_empty() thread 281462427348864
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: about forcing recovery.
2025-02-21T05:30:00Z UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID=bc39de400860a943996e7b04e4952d1d68b3ff6d
Build ID: Not Available
Server Version: 8.0.32-25 GreatSQL (GPL), Release 25, Revision 79f57097e3f
Thread pointer: 0xfffc840050c0
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 = fffd13ffe5e8 thread_stack 0x80000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x30)
/usr/sbin/mysqld(print_fatal_signal(int)+0x360)
/usr/sbin/mysqld(my_server_abort()+0x90)
/usr/sbin/mysqld(my_abort()+0x14)
/usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x26c)
/usr/sbin/mysqld(Parallel_reader::dispatch_ctx(row_prebuilt_t*)+0x3b0)
/usr/sbin/mysqld(ha_innobase::pq_worker_scan_next(void*, unsigned char*)+0x11c)
/usr/sbin/mysqld(handler::ha_pq_next(unsigned char*, void*)+0x224)
/usr/sbin/mysqld(PQblockScanIterator::Read()+0x24)
/usr/sbin/mysqld(FilterIterator::Read()+0x28)
/usr/sbin/mysqld(NestedLoopIterator::Read()+0xd0)
/usr/sbin/mysqld(Query_expression::ExecuteIteratorQuery(THD*)+0x2f8)
/usr/sbin/mysqld(pq_worker_exec(void*)+0x74)
/usr/sbin/mysqld()
/lib64/libpthread.so.0(+0x7898)
/lib64/libc.so.6(+0xd1ddc)
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (fffcd0015c70): is an invalid pointer
Connection ID (thread ID): 220
Status: NOT_KILLED
Please help us make Percona Server better by reporting any
bugs at https://bugs.percona.com/
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
2025-02-21T13:30:00.887325+08:00 0 The syntax 'log_slow_slave_statements' is deprecated and will be removed in a future release. Please use log_slow_replica_statements instead.
2025-02-21T13:30:00.887373+08:00 0 The syntax 'slave_parallel_type' is deprecated and will be removed in a future release. Please use replica_parallel_type instead.
2025-02-21T13:30:00.887382+08:00 0 The syntax '--replica-parallel-type' is deprecated and will be removed in a future release.
2025-02-21T13:30:00.887393+08:00 0 The syntax 'slave_parallel_workers' is deprecated and will be removed in a future release. Please use replica_parallel_workers instead.
2025-02-21T13:30:00.887406+08:00 0 The syntax 'slave_preserve_commit_order' is deprecated and will be removed in a future release. Please use replica_preserve_commit_order instead.
2025-02-21T13:30:00.887417+08:00 0 The syntax 'slave_checkpoint_period' is deprecated and will be removed in a future release. Please use replica_checkpoint_period instead.
2025-02-21T13:30:00.887536+08:00 0 The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead.
2025-02-21T13:30:00.887970+08:00 0 Insecure configuration for --secure-log-path: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2025-02-21T13:30:00.888028+08:00 0 BuildID=bc39de400860a943996e7b04e4952d1d68b3ff6d
2025-02-21T13:30:00.888036+08:00 0 Basedir set to /usr/.
2025-02-21T13:30:00.888048+08:00 0 /usr/sbin/mysqld (mysqld 8.0.32-25) starting as process 1
2025-02-21T13:30:00.908912+08:00 0 option 'innodb-autoextend-increment': unsigned value 1073741824 adjusted to 1000.
2025-02-21T13:30:00.910170+08:00 0 Using Linux native AIO
2025-02-21T13:30:00.910214+08:00 0 Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.
2025-02-21T13:30:00.910558+08:00 0 Plugin 'FEDERATED' is disabled.
2025-02-21T13:30:00.910646+08:00 0 Plugin 'ndbcluster' is disabled.
2025-02-21T13:30:00.910671+08:00 0 Plugin 'ndbinfo' is disabled.
2025-02-21T13:30:00.910686+08:00 0 Plugin 'ndb_transid_mysql_connection_map' is disabled.
2025-02-21T13:30:00.912374+08:00 1 InnoDB initialization has started.
2025-02-21T13:30:00.912409+08:00 1 Atomic write enabled
2025-02-21T13:30:00.912438+08:00 1 PUNCH HOLE support available
2025-02-21T13:30:00.912456+08:00 1 Uses event mutexes
2025-02-21T13:30:00.912467+08:00 1 GCC builtin __atomic_thread_fence() is used for memory barrier
2025-02-21T13:30:00.912477+08:00 1 Compressed tables use zlib 1.2.13
2025-02-21T13:30:00.913664+08:00 1 File purge : set file purge path : /data/GreatSQL/#file_purge
2025-02-21T13:30:00.913744+08:00 1 Using hardware accelerated crc32 and polynomial multiplication.
2025-02-21T13:30:00.914061+08:00 1 Directories to scan './'
2025-02-21T13:30:00.914108+08:00 1 Scanning './'
2025-02-21T13:30:00.935857+08:00 1 Completed space ID check of 1154 files.
2025-02-21T13:30:00.936614+08:00 1 Initializing buffer pool, total size = 1.000000G, instances = 8, chunk size =128.000000M
2025-02-21T13:30:00.963869+08:00 1 Completed initialization of buffer pool
2025-02-21T13:30:00.967510+08:00 0 If the mysqld execution user is authorized, page cleaner and LRU manager thread priority can be changed. See the man page of setpriority().
2025-02-21T13:30:00.968343+08:00 1 Using './#ib_16384_0.dblwr' for doublewrite
2025-02-21T13:30:00.968812+08:00 1 Using './#ib_16384_1.dblwr' for doublewrite
2025-02-21T13:30:00.975298+08:00 1 Double write buffer files: 2
2025-02-21T13:30:00.975343+08:00 1 Double write buffer pages per instance: 4
2025-02-21T13:30:00.975372+08:00 1 Using './#ib_16384_0.dblwr' for doublewrite
2025-02-21T13:30:00.975396+08:00 1 Using './#ib_16384_1.dblwr' for doublewrite
2025-02-21T13:30:01.022740+08:00 1 The latest found checkpoint is at lsn = 557215471603 in redo log file ./#innodb_redo/#ib_redo2200.
2025-02-21T13:30:01.022803+08:00 1 The log sequence number 363361311611 in the system tablespace does not match the log sequence number 557215471603 in the redo log files!
2025-02-21T13:30:01.022818+08:00 1 Database was not shutdown normally!
2025-02-21T13:30:01.022830+08:00 1 Starting crash recovery.
2025-02-21T13:30:01.023410+08:00 1 Starting to parse redo log at lsn = 557215471281, whereas checkpoint_lsn = 557215471603 and start_lsn = 557215471104
2025-02-21T13:30:01.106868+08:00 1 Doing recovery: scanned up to log sequence number 557220713984
2025-02-21T13:30:01.116421+08:00 1 Doing recovery: scanned up to log sequence number 557221481074
2025-02-21T13:30:01.143510+08:00 1 Log background threads are being started...
2025-02-21T13:30:01.143911+08:00 1 Applying a batch of 966 redo log records ...
2025-02-21T13:30:01.147886+08:00 1 10%
2025-02-21T13:30:01.149001+08:00 1 20%
2025-02-21T13:30:01.149094+08:00 1 30%
2025-02-21T13:30:01.149187+08:00 1 40%
2025-02-21T13:30:01.149669+08:00 1 50%
2025-02-21T13:30:01.152655+08:00 1 60%
2025-02-21T13:30:01.153761+08:00 1 70%
2025-02-21T13:30:01.153876+08:00 1 80%
2025-02-21T13:30:01.153944+08:00 1 90%
2025-02-21T13:30:01.154564+08:00 1 100%
2025-02-21T13:30:01.654983+08:00 1 Apply batch completed!
2025-02-21T13:30:02.402112+08:00 1 Using undo tablespace './undo_001'.
2025-02-21T13:30:02.402261+08:00 1 Using undo tablespace './undo_002'.
2025-02-21T13:30:02.402584+08:00 1 Opened 2 existing undo tablespaces.
2025-02-21T13:30:02.402649+08:00 1 GTID recovery trx_no: 396014179
2025-02-21T13:30:02.404052+08:00 1 Parallel initialization of rseg complete
2025-02-21T13:30:02.404087+08:00 1 Time taken to initialize rseg using 4 thread: 1442 ms.
2025-02-21T13:30:02.405119+08:00 1 Removed temporary tablespace data file: "ibtmp1"
2025-02-21T13:30:02.405145+08:00 1 Creating shared tablespace for temporary tables
2025-02-21T13:30:02.405195+08:00 1 Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2025-02-21T13:30:03.047428+08:00 1 File './ibtmp1' size is now 12 MB.
2025-02-21T13:30:03.047559+08:00 1 Scanning temp tablespace dir:'./#innodb_temp/'
2025-02-21T13:30:03.219298+08:00 1 Created 128 and tracked 128 new rollback segment(s) in the temporary tablespace. 128 are now active.
2025-02-21T13:30:03.219538+08:00 1 Percona XtraDB (http://www.percona.com) 8.0.32-23 started; log sequence number 557221481084
2025-02-21T13:30:03.219678+08:00 1 InnoDB initialization has ended.
2025-02-21T13:30:03.223666+08:00 1 Data dictionary restarting version '80023'.
2025-02-21T13:30:03.321443+08:00 1 Reading DD tablespace files
2025-02-21T13:30:03.421021+08:00 1 Scanned 1156 tablespaces. Validated 1156.
2025-02-21T13:30:03.537927+08:00 1 Using data dictionary with version '80023'.
2025-02-21T13:30:03.572368+08:00 0 Plugin mysqlx reported: 'IPv6 is available'
2025-02-21T13:30:03.573027+08:00 0 Plugin mysqlx reported: 'X Plugin ready for connections. bind-address: '::' port: 33060'
2025-02-21T13:30:03.573059+08:00 0 Plugin mysqlx reported: 'X Plugin ready for connections. socket: '/var/lib/mysql/mysqlx.sock''
2025-02-21T13:30:03.688850+08:00 0 Recovering after a crash using /data/GreatSQL/binlog
2025-02-21T13:30:04.021163+08:00 0 Starting XA crash recovery...
2025-02-21T13:30:04.023676+08:00 0 Crash recovery finished in binlog engine. No attempts to commit, rollback or prepare any transactions.
2025-02-21T13:30:04.023730+08:00 0 Crash recovery finished in InnoDB engine. No attempts to commit, rollback or prepare any transactions.
2025-02-21T13:30:04.023743+08:00 0 XA crash recovery finished.
2025-02-21T13:30:04.029559+08:00 0 DDL log recovery : begin
2025-02-21T13:30:04.029659+08:00 0 DDL log recovery : end
2025-02-21T13:30:04.030147+08:00 0 Loading buffer pool(s) from /data/GreatSQL/ib_buffer_pool
2025-02-21T13:30:04.034212+08:00 0 GTID compression after recovery.
2025-02-21T13:30:04.037516+08:00 0 Waiting for purge to start
2025-02-21T13:30:04.268877+08:00 0 Buffer pool(s) load completed at 250221 13:30:04
2025-02-21T13:30:04.695845+08:00 0 Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2025-02-21T13:30:04.695905+08:00 0 Skipping generation of SSL certificates as certificate files are present in data directory.
2025-02-21T13:30:04.696943+08:00 0 CA certificate ca.pem is self signed.
2025-02-21T13:30:04.697243+08:00 0 Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2025-02-21T13:30:04.697285+08:00 0 Skipping generation of RSA key pair through --sha256_password_auto_generate_rsa_keys as key files are present in data directory.
2025-02-21T13:30:04.697299+08:00 0 Skipping generation of RSA key pair through --caching_sha2_password_auto_generate_rsa_keys as key files are present in data directory.
2025-02-21T13:30:04.697446+08:00 0 Server hostname (bind-address): '*'; port: 3306
2025-02-21T13:30:04.697485+08:00 0 IPv6 is available.
2025-02-21T13:30:04.697499+08:00 0 - '::' resolves to '::';
2025-02-21T13:30:04.697515+08:00 0 Server socket created on IP: '::'.
2025-02-21T13:30:04.767456+08:00 0 Insecure configuration for --pid-file: Location '/data/GreatSQL' in the path is accessible to all OS users. Consider choosing a different directory.
2025-02-21T13:30:04.776689+08:00 0 unknown variable 'loose-gdb_parallel_load=1'.
2025-02-21T13:30:04.825814+08:00 0 Failed to start slave threads for channel ''.
2025-02-21T13:30:04.827585+08:00 7 Event Scheduler: scheduler thread started with id 7
2025-02-21T13:30:04.827630+08:00 0 /usr/sbin/mysqld: ready for connections. Version: '8.0.32-25'socket: '/data/GreatSQL/mysql.sock'port: 3306GreatSQL (GPL), Release 25, Revision 79f57097e3f.
2025-02-21T13:30:04.827714+08:00 0 Plugin mysqlx reported: 'Using SSL configuration from MySQL Server'
2025-02-21T13:30:04.828306+08:00 0 Plugin mysqlx reported: 'Using OpenSSL for TLS connections'
2025-02-21T13:30:04.828419+08:00 0 X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/lib/mysql/mysqlx.sock
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
2025-02-21T13:40:06.358100+08:00 15 'wait_timeout' period of 600 seconds was exceeded for `root`@`%`. The idle time since last command was too long.
2025-02-21T13:40:06.358334+08:00 15 Aborted connection 15 to db: 'oscape_db' user: 'root' host: '127.0.0.1' (The client was disconnected by the server because of inactivity.).
2025-02-21T13:40:09.388723+08:00 13 'wait_timeout' period of 600 seconds was exceeded for `root`@`%`. The idle time since last command was too long.
2025-02-21T13:40:09.388922+08:00 13 Aborted connection 13 to db: 'oscape_db' user: 'root' host: '127.0.0.1' (The client was disconnected by the server because of inactivity.).
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
观察日志发现都是Assertion failure: row0pread.cc:1350:is_queue_empty() thread引起的，请问是什么问题？
这是触发了InnoDB并行查询bug导致的，请设置 force_parallel_execute = OFF，不要启用该特性。
关联帖子：https://greatsql.cn/forum.php?mod=viewthread&tid=881&highlight=queue
关联手册：https://greatsql.cn/docs/8.0.32-26/6-oper-guide/8-troubleshooting.html#greatsql-%E4%B8%AD%E8%BF%90%E8%A1%8C%E4%B8%80%E4%BA%9B%E6%9F%A5%E8%AF%A2-sql-%E4%BC%9A-hang-%E4%BD%8F%E4%B8%80%E7%9B%B4%E6%97%A0%E5%93%8D%E5%BA%94
页:
[1]