首页 > 其他分享 >[MY-013183] [InnoDB] Assertion failure: dict0dict.cc:1869:table->get_ref_count() == 0

[MY-013183] [InnoDB] Assertion failure: dict0dict.cc:1869:table->get_ref_count() == 0

时间:2024-02-04 10:13:44浏览次数:35  
标签:count 02 00 013183 get 2024 mysql slave MY

背景:
执行alter table TABLE_NAME drop partition PART_NAME;时执行过程中执行了ctrl+c导致mysql服务器崩溃自动重启。


mysql错误日志内容:

2024-02-02T10:30:32.424737+08:00 460639464 [ERROR] [MY-013183] [InnoDB] Assertion failure: dict0dict.cc:1869:table->get_ref_count() == 0 thread 139776684840704
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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
02:30:32 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f204ba5cd40 thread_stack 0x100000
/usr/local/mysql/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2e) [0x1f3d69e]
/usr/local/mysql/bin/mysqld(print_fatal_signal(int)+0x2bf) [0xed588f]
/usr/local/mysql/bin/mysqld(my_server_abort()+0x6e) [0xed59ce]
/usr/local/mysql/bin/mysqld(my_abort()+0xa) [0x1f37e7a]
/usr/local/mysql/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x312) [0x21c3212]
/usr/local/mysql/bin/mysqld() [0x227a230]
/usr/local/mysql/bin/mysqld(dict_partitioned_table_remove_from_cache(char const*)+0x129) [0x227a429]
/usr/local/mysql/bin/mysqld() [0x2020b2b]
/usr/local/mysql/bin/mysqld() [0xe262d7]
/usr/local/mysql/bin/mysqld(mysql_alter_table(THD*, char const*, char const*, HA_CREATE_INFO*, TABLE_LIST*, Alter_info*)+0x4287) [0xe396f7]
/usr/local/mysql/bin/mysqld(Sql_cmd_alter_table::execute(THD*)+0x4bb) [0x12345eb]
/usr/local/mysql/bin/mysqld(mysql_execute_command(THD*, bool)+0x9e0) [0xd8a4a0]
/usr/local/mysql/bin/mysqld(dispatch_sql_command(THD*, Parser_state*)+0x3ee) [0xd8defe]
/usr/local/mysql/bin/mysqld(dispatch_command(THD*, COM_DATA const*, enum_server_command)+0xd14) [0xd8f174]
/usr/local/mysql/bin/mysqld(do_command(THD*)+0x103) [0xd91233]
/usr/local/mysql/bin/mysqld() [0xec6790]
/usr/local/mysql/bin/mysqld() [0x23ff6d5]
/lib64/libpthread.so.0(+0x7dd5) [0x7f3ecdf7bdd5]
/lib64/libc.so.6(clone+0x6d) [0x7f3ecc50aead]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f180009ff00): is an invalid pointer
Connection ID (thread ID): 460639464
Status: KILL_QUERY

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-02-02T10:30:57.669240+08:00 0 [Warning] [MY-011068] [Server] The syntax 'log_slow_slave_statements' is deprecated and will be removed in a future release. Please use log_slow_replica_statements instead.
2024-02-02T10:30:57.669286+08:00 0 [Warning] [MY-011069] [Server] The syntax '--relay-log-info-file' is deprecated and will be removed in a future release.
2024-02-02T10:30:57.669988+08:00 0 [Warning] [MY-011069] [Server] The syntax '--master-info-repository' is deprecated and will be removed in a future release.
2024-02-02T10:30:57.670010+08:00 0 [Warning] [MY-011069] [Server] The syntax '--relay-log-info-repository' is deprecated and will be removed in a future release.
2024-02-02T10:30:57.670040+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-02-02T10:30:57.670103+08:00 0 [Warning] [MY-011068] [Server] The syntax 'skip_slave_start' is deprecated and will be removed in a future release. Please use skip_replica_start instead.
2024-02-02T10:30:57.671600+08:00 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead.
2024-02-02T10:30:57.671639+08:00 0 [System] [MY-010116] [Server] /usr/local/mysql/bin/mysqld (mysqld 8.0.29) starting as process 45527
2024-02-02T10:30:57.680966+08:00 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2024-02-02T10:30:57.709186+08:00 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-02-02T10:31:45.675474+08:00 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-02-02T10:31:45.986971+08:00 0 [Warning] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-001287 - 'validate password plugin' is deprecated and will be removed in a future release. Please use validate_password component instead
2024-02-02T10:31:45.987174+08:00 0 [Warning] [MY-010918] [Repl] 'rpl_semi_sync_master' is deprecated and will be removed in a future release. Please use rpl_semi_sync_source instead.
2024-02-02T10:31:45.987732+08:00 0 [Warning] [MY-010918] [Repl] 'rpl_semi_sync_slave' is deprecated and will be removed in a future release. Please use rpl_semi_sync_replica instead.
2024-02-02T10:31:46.505965+08:00 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2024-02-02T10:31:46.517272+08:00 0 [System] [MY-010232] [Server] XA crash recovery finished.
2024-02-02T10:31:47.040446+08:00 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-02-02T10:31:47.040501+08:00 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-02-02T10:31:47.041787+08:00 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/data' in the path is accessible to all OS users. Consider choosing a different directory.
2024-02-02T10:31:47.071384+08:00 5 [Warning] [MY-010897] [Repl] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
2024-02-02T10:31:47.072534+08:00 5 [System] [MY-010562] [Repl] Slave I/O thread for channel '': connected to master 'repl@mysql_slave:3306',replication started in log 'mysql_bin.004465' at position 800269497
2024-02-02T10:31:47.078238+08:00 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /tmp/mysqlx.sock
2024-02-02T10:31:47.078281+08:00 0 [System] [MY-010931] [Server] /usr/local/mysql/bin/mysqld: ready for connections. Version: '8.0.29'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Server - GPL.
2024-02-02T10:31:53.771859+08:00 7 [Warning] [MY-011153] [Repl] Timeout waiting for reply of binlog (file: mysql_bin.005745, pos: 802), semi-sync up to file , position 0.
2024-02-02T10:34:37.588388+08:00 7 [ERROR] [MY-010584] [Repl] Slave SQL for channel '': Worker 1 failed executing transaction '317b9252-5078-11ee-ad48-5098b8d4ef02:2372' at master log mysql_bin.004465, end_log_pos 800416129; Could not execute Update_rows event on table zabbix.triggers; Can't find record in 'triggers', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log mysql_bin.004465, end_log_pos 800416129, Error_code: MY-001032
2024-02-02T10:34:37.637103+08:00 6 [ERROR] [MY-010586] [Repl] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql_bin.004465' position 800354498


2024-02-02T12:18:51.778342+08:00 0 [ERROR] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-001158 - Got an error reading communication packets
2024-02-02T12:19:00.781894+08:00 5 [System] [MY-010558] [Repl] Slave for channel '': received end packet from server due to dump thread being killed on master. Dump threads are killed for example during master shutdown, explicitly by a user, or when the master receives a binlog send request from a duplicate server UUID <4aa9c61c-a1ee-11ed-9240-5098b8d4f1c6> : Error
2024-02-02T12:19:00.782182+08:00 5 [Warning] [MY-010897] [Repl] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
2024-02-02T12:19:00.782442+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 1 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:19:02.622056+08:00 24 [ERROR] [MY-011161] [Repl] Semi-sync master failed on net_flush() before waiting for replica reply.
2024-02-02T12:19:07.621970+08:00 6485 [Warning] [MY-011153] [Repl] Timeout waiting for reply of binlog (file: mysql_bin.005745, pos: 92875), semi-sync up to file mysql_bin.005745, position 92499.
2024-02-02T12:20:00.782875+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 2 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:21:00.783466+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 3 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:22:00.784221+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 4 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:23:00.785083+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 5 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:24:00.785720+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 6 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:25:00.786408+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 7 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:26:00.786915+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 8 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:27:00.787314+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 9 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:28:00.788033+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 10 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:29:00.788540+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 11 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:30:00.789377+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 12 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:31:00.790085+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 13 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:32:00.790473+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 14 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:33:00.790915+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 15 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:34:00.792210+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 16 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:35:00.794116+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 17 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:35:04.228362+08:00 12823 [ERROR] [MY-010584] [Repl] Slave SQL: Could not execute Update_rows event on table zabbix.triggers; Can't find record in 'triggers', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log FIRST, end_log_pos 800416129, Error_code: MY-001032
2024-02-02T12:36:00.794635+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 18 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:36:20.319340+08:00 13428 [ERROR] [MY-010584] [Repl] Slave SQL: Could not execute Update_rows event on table zabbix.triggers; Can't find record in 'triggers', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log FIRST, end_log_pos 800416129, Error_code: MY-001032
2024-02-02T12:37:00.795211+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 19 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:38:00.796524+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 20 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:38:12.375627+08:00 14196 [ERROR] [MY-010584] [Repl] Slave SQL: Could not execute Update_rows event on table zabbix.triggers; Can't find record in 'triggers', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log FIRST, end_log_pos 800416129, Error_code: MY-001032
2024-02-02T12:39:00.797014+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 21 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:40:00.797560+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 22 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:41:00.798218+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 23 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:42:00.798692+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 24 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:43:00.800761+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 25 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:44:00.801214+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 26 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:45:00.801791+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 27 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:46:00.802230+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 28 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:47:00.802857+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 29 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:48:00.803336+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 30 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003
2024-02-02T12:48:04.293524+08:00 18633 [ERROR] [MY-010584] [Repl] Slave SQL: Could not execute Update_rows event on table zabbix.triggers; Can't find record in 'triggers', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log FIRST, end_log_pos 800416129, Error_code: MY-001032
2024-02-02T12:49:00.803975+08:00 5 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error reconnecting to master 'repl@mysql_slave:3306' - retry-time: 60 retries: 31 message: Can't connect to MySQL server on 'mysql_slave:3306' (111), Error_code: MY-002003

标签:count,02,00,013183,get,2024,mysql,slave,MY
From: https://www.cnblogs.com/haha029/p/18005649

相关文章

  • 无涯教程-getDate()函数
    JavaScriptdategetDate()方法根据当地时间返回指定日期的月份。getDate返回的值是1到31之间的整数。getDate()-语法Date.getDate()getDate()-返回值返回今天的日期和时间。getDate()-示例vardt=newDate("December25,199523:15:00");console.log("getDate(......
  • C. Did We Get Everything Covered?
    C.DidWeGetEverythingCovered?Youaregiventwointegers$n$and$k$alongwithastring$s$.Yourtaskistocheckwhetherallpossiblestringsoflength$n$thatcanbeformedusingthefirst$k$lowercaseEnglishalphabetsoccurasasubsequenceof......
  • get and build the qt in open source version
    GettingthesourcecodeFirst,cdintothedirectorywhereyouwantthe"qt5"directorytolive.Then,clonethetop-levelQt5gitrepository:$gitclonegit://code.qt.io/qt/qt5.gitor(ifyou'rebehindafirewallandwanttousethehtt......
  • 字符串构建问题——cf_921_C. Did We Get Everything Covered?
    目录问题概述思路想法参考代码include<bits/stdc++.h>defineFAST_IOios::sync_with_stdio(false),cin.tie(0),cout.tie(0)defineendl'\n'definepllpair<longlong,longlong>definepiipair<int,int>definevivectordefinevlvectordefinelllo......
  • C++编程练习||Account类:创建一个名为Account的类,银行可以使用它表示客户的银行帐户||I
    1.Account类题目:创建一个名为Account的类,银行可以使用它表示客户的银行帐户。这个类应该包括一个类型为double的数据成员,表示帐户余额。这个类提供一个构造函数,它接受初始余额并用它初始化数据成员。这个构造函数应当确认初始余额的有效性,保证它大于或等于0。否则,余额应设置为0......
  • Java并发基础:CountDownLatch全面解析!
    内容概要CountDownLatch的优点在于能够简洁高效地协调多个线程的执行顺序,确保一组线程都完成后才触发其他线程的执行,适用于资源加载、任务初始化等场景。它提供了清晰的等待/通知机制,易于理解和使用,是提升多线程程序性能和可靠性的重要工具。核心概念CountDownLatch是java.util......
  • file_get_contents 避免出现按个 ssl -60 的报错 ,不进行数据验证 或者 使用php.ini 进
    1,使用不去验证数据$stream_opts=["ssl"=>["verify_peer"=>false,"verify_peer_name"=>false,]];$user_info=json_decode(file_get_contents($user_info_url,false,stream_context_create($stream_opts)));2,配置php.ini......
  • Python requests.get所有参数顺序、Python requests.post所有参数顺序
    request.get所有参数顺序:url(必选)、params、allow_redirects、auth、cert、cookies、headers、proxies、stream、timeout、verify -------------------------------------------------------------------------------------------------------------------------------------......
  • phpMyAdmin 未授权Getshell
    前言做渗透测试的时候偶然发现,phpmyadmin少见的打法,以下就用靶场进行演示了。0x01漏洞发现环境搭建使用metasploitable2,可在网上搜索下载,搭建很简单这里不多说了。发现phpmyadmin,如果这个时候无法登陆,且也没有前台的漏洞,可以继续在这个phpmyadmin目录下做文章。发现setup......
  • 聊聊ClickHouse MergeTree引擎的固定/自适应索引粒度
    ​ 前言我们在刚开始学习ClickHouse的MergeTree引擎时,就会发现建表语句的末尾总会有SETTINGSindex_granularity=8192这句话(其实不写也可以),表示索引粒度为8192。在每个datapart中,索引粒度参数的含义有二:每隔index_granularity行对主键组的数据进行采样,形成稀疏索引,并存储......