Git Product home page Git Product logo

polardb / polardbx Goto Github PK

View Code? Open in Web Editor NEW
73.0 73.0 20.0 196 KB

PolarDB-X is a cloud native distributed SQL Database designed for high concurrency, massive storage, complex querying scenarios.

Makefile 83.81% Dockerfile 2.64% Shell 13.55%
cloud-native distributed-transactions enterprise-class high-availability high-concurrency horizontal-scaling htap massive-datasets mysql relational-databases

polardbx's People

Contributors

agapple avatar free6om avatar zeratulllll avatar zhiliyao avatar zhiliyao-polarx avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

polardbx's Issues

failed to make the code after following the readme guide in ubuntu

Hello guys, maybe the mirror of alibaba is broken on this file. I failed to do a make following the starter guide as below

https://mirrors.aliyun.com/apache/maven/maven-3/3.8.6/binaries/apache-maven-3.8.6-bin.tar.gz



olarx@wayne-VirtualBox:~/wayne/PolarDB-X$ make
if [ ! -d /opt/apache-maven-3.8.6 ]; then \
	sudo wget https://mirrors.aliyun.com/apache/maven/maven-3/3.8.6/binaries/apache-maven-3.8.6-bin.tar.gz -P /tmp && \
	sudo tar xf /tmp/apache-maven-3.8.6-bin.tar.gz -C /opt && \
	sudo rm -f /tmp/apache-maven-3.8.6-bin.tar.gz && \
	sudo ln -fs /opt/apache-maven-3.8.6 /opt/maven && \
	echo 'export M2_HOME=/opt/maven' | sudo tee /etc/profile.d/maven.sh && \
	echo 'export PATH=${M2_HOME}/bin:${PATH}' | sudo tee -a /etc/profile.d/maven.sh && \
	sudo chmod +x /etc/profile.d/maven.sh && \
	echo '<mirror>' | sudo tee /opt/maven/conf/settings.xml && \
	echo '<id>aliyunmaven</id>' | sudo tee -a /opt/maven/conf/settings.xml && \
	echo '<mirrorOf>*</mirrorOf>' | sudo tee -a /opt/maven/conf/settings.xml && \
	echo '<name>aliyun public</name>' | sudo tee -a /opt/maven/conf/settings.xml && \
	echo '<url>https://maven.aliyun.com/repository/public</url>' | sudo tee -a /opt/maven/conf/settings.xml && \
	echo '</mirror>' | sudo tee -a /opt/maven/conf/settings.xml; \
fi
--2023-03-16 11:55:31--  https://mirrors.aliyun.com/apache/maven/maven-3/3.8.6/binaries/apache-maven-3.8.6-bin.tar.gz
Resolving mirrors.aliyun.com (mirrors.aliyun.com)... 240e:e9:a807:0:203::3a5, 240e:e9:a807:0:203::3a6, 222.186.149.100, ...
Connecting to mirrors.aliyun.com (mirrors.aliyun.com)|240e:e9:a807:0:203::3a5|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-03-16 11:55:31 ERROR 404: Not Found.

make: *** [Makefile:210: deps] Error 8
polarx@wayne-VirtualBox:~/wayne/PolarDB-X$ 

怎么没有自定义分片函数?

比如内容表和内容评论表,因为热门内容评论多,冷门热门评论少,如果按照内容ID去拆分评论表,那么数据容易不均匀。因此希望能够自定义分片函数。比如每个内容的最新1万条评论按照内容ID分片存储。1万条之后的内容移到冷数据存储,由于不是固定的分片规则,所以需要在内容表加一个记录该内容对应的评论所在的冷库分片的位置。查询的时候,如果是查询1万条后的评论则先根据内容ID查分片位置再查评论数据。
虽然后面的自定义分片及查询可以通过代码实现,但还是想了解一下在polardbx里能否通过配置实现。

follow the readme guide then failed to start polardbx

follow the exactly steps in the readme, build is OK, it try to start Dameon, below is the error log

2023-03-28T04:28:56.480017Z 1 [Warning] [MY-011825] [InnoDB]   [GTID INFO] Reading from undo log :
2023-03-28T04:29:20.122832Z 0 [Warning] [MY-000000] [Server] Plugin polarx_rpc reported: 'PolarX RPC disabled by database initialization.'
2023-03-28T04:29:20.122934Z 0 [ERROR] [MY-011237] [Server] Plugin mysqlx reported: 'Startup failed with error "Galaxy X disabled."'
2023-03-28T04:29:32.616570Z 0 [Warning] [MY-010015] [Repl] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2023-03-28T04:29:34.422236Z 0 [Warning] [MY-000067] [Server] unknown variable 'loose_implicit_primary_key=1'.
2023-03-28T04:29:34.422316Z 0 [Warning] [MY-000067] [Server] unknown variable 'loose_innodb_doublewrite_pages=64'.
2023-03-28T04:29:34.422381Z 0 [Warning] [MY-000067] [Server] unknown variable 'loose_innodb_log_optimize_ddl=OFF'.
2023-03-28T04:29:34.428355Z 0 [Warning] [MY-000067] [Server] unknown variable 'loose_innodb_multi_blocks_enabled=ON'.


2023-03-28T04:30:46.865099Z 0 [Warning] [MY-000000] [Server] Plugin polarx_rpc reported: 'Listen on port 34886.'
2023-03-28T04:30:46.868003Z 0 [Warning] [MY-000000] [Server] Plugin polarx_rpc reported: 'Listen on port 34886.'
2023-03-28T04:30:46.868163Z 0 [Warning] [MY-000000] [Server] Plugin polarx_rpc reported: 'Listen on port 34886.'
2023-03-28T04:30:46.868315Z 0 [Warning] [MY-000000] [Server] Plugin polarx_rpc reported: 'Listen on port 34886.'
2023-03-28T04:30:46.868461Z 0 [Warning] [MY-000000] [Server] Plugin polarx_rpc reported: 'Listen on port 34886.'
2023-03-28T04:30:46.868603Z 0 [Warning] [MY-000000] [Server] Plugin polarx_rpc reported: 'Listen on port 34886.'
2023-03-28T04:30:46.870796Z 0 [Warning] [MY-000000] [Server] Plugin polarx_rpc reported: 'Listen on port 34886.'
2023-03-28T04:30:46.952362Z 0 [Warning] [MY-000000] [Server] Plugin polarx_rpc reported: 'Listen on port 34886.'
2023-03-28T04:30:46.975550Z 0 [ERROR] [MY-011237] [Server] Plugin mysqlx reported: 'Startup failed with error "Galaxy X disabled."'
2023-03-28T04:30:48.650789Z 0 [System] [MY-010229] [Server] Starting crash recovery...
2023-03-28T04:30:48.680268Z 0 [System] [MY-010232] [Server] Crash recovery finished.
2023-03-28T04:30:48.682545Z 0 [Warning] [MY-000000] [Server] Recover consensus index is 0
2023-03-28T04:30:48.879960Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2023-03-28T04:30:49.061243Z 0 [Warning] [MY-000067] [Server] unknown variable 'loose_implicit_primary_key=1'.
2023-03-28T04:30:49.063805Z 0 [Warning] [MY-000067] [Server] unknown variable 'loose_innodb_doublewrite_pages=64'.
2023-03-28T04:30:49.064017Z 0 [Warning] [MY-000067] [Server] unknown variable 'loose_innodb_log_optimize_ddl=OFF'.
2023-03-28T04:30:49.064187Z 0 [Warning] [MY-000067] [Server] unknown variable 'loose_innodb_multi_blocks_enabled=ON'.

2023-03-28T04:30:46.952362Z 0 [Warning] [MY-000000] [Server] Plugin polarx_rpc reported: 'Listen on port 34886.'
2023-03-28T04:30:46.975550Z 0 [ERROR] [MY-011237] [Server] Plugin mysqlx reported: 'Startup failed with error "Galaxy X disabled."'
2023-03-28T04:30:48.650789Z 0 [System] [MY-010229] [Server] Starting crash recovery...
2023-03-28T04:30:48.680268Z 0 [System] [MY-010232] [Server] Crash recovery finished.
2023-03-28T04:30:48.682545Z 0 [Warning] [MY-000000] [Server] Recover consensus index is 0
2023-03-28T04:30:48.879960Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2023-03-28T04:30:49.061243Z 0 [Warning] [MY-000067] [Server] unknown variable 'loose_implicit_primary_key=1'.
2023-03-28T04:30:49.063805Z 0 [Warning] [MY-000067] [Server] unknown variable 'loose_innodb_doublewrite_pages=64'.
2023-03-28T04:30:49.064017Z 0 [Warning] [MY-000067] [Server] unknown variable 'loose_innodb_log_optimize_ddl=OFF'.
2023-03-28T04:30:49.064187Z 0 [Warning] [MY-000067] [Server] unknown variable 'loose_innodb_multi_blocks_enabled=ON'.
2023-03-28T04:30:49.066666Z 0 [Warning] [MY-000067] [Server] unknown variable 'loose_innodb_numa_interleave=OFF'.
2023-03-28T04:30:49.066887Z 0 [Warning] [MY-000067] [Server] unknown variable 'loose_persist_binlog_to_redo=OFF'.
2023-03-28T04:30:49.067050Z 0 [Warning] [MY-000067] [Server] unknown variable 'loose_persist_binlog_to_redo_size_limit=1048576'.
[2023-03-27 23:31:09.736963] [ERROR] Server 1 : Paxos state change from FOLL to CAND !!
[2023-03-27 23:31:09.736963] [ERROR] Server 1 : Start new requestVote: new term(2)
[2023-03-27 23:31:09.736963] [ERROR] Server 1 : Paxos state change from CAND to LEDR !!
[2023-03-27 23:31:09.736963] [ERROR] Server 1 : become Leader (currentTerm 2, lli:1, llt:2)!!
2023-03-28T04:31:10.237835Z 0 [System] [MY-010931] [Server] /home/polarx/PolarDB-X/build/run/galaxyengine/u01/mysql/bin/mysqld: ready for connections. Version: '8.0.18'  socket: '/home/polarx/PolarDB-X/build/run/galaxyengine/data/run/mysql.sock'  port: 4886  Source distribution.
2023-03-28T04:31:16.509171Z 5 [Warning] [MY-000000] [Server] Apply thread start, recover status = 0, start apply index = 0, rli consensus index = 0.
2023-03-28T04:31:16.511682Z 5 [Warning] [MY-000000] [Server] Apply thread group relay log file name = '/home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/mysql-bin.000001', pos = 252, rli apply index = 0.
2023-03-28T07:30:04.613949Z 0 [Warning] [MY-011069] [Server] The syntax 'avoid_temporal_upgrade' is deprecated and will be removed in a future release.
2023-03-28T07:30:04.613985Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2023-03-28T07:30:04.615811Z 0 [Warning] [MY-011069] [Server] The syntax '--log-bin-use-v1-row-events' is deprecated and will be removed in a future release.
2023-03-28T07:30:04.615894Z 0 [Warning] [MY-011069] [Server] The syntax '--master-info-file' is deprecated and will be removed in a future release.
2023-03-28T07:30:04.615922Z 0 [Warning] [MY-011069] [Server] The syntax '--relay-log-info-file' is deprecated and will be removed in a future release.
2023-03-28T07:30:04.615934Z 0 [Warning] [MY-011069] [Server] The syntax 'show_old_temporals' is deprecated and will be removed in a future release.
2023-03-28T07:30:04.615974Z 0 [Warning] [MY-010084] [Server] options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if --slow-query-log is not set
2023-03-28T07:30:04.615975Z 0 [Warning] [MY-010086] [Server] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-03-28T07:30:04.616084Z 0 [System] [MY-010116] [Server] /home/polarx/PolarDB-X/build/run/galaxyengine/u01/mysql/bin/mysqld (mysqld 8.0.18) starting as process 267509
2023-03-28T07:30:04.628804Z 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.
2023-03-28T07:30:05.348950Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:06.353923Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:07.358742Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:08.361339Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:09.364619Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:10.368657Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:11.375651Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:12.377427Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:13.379927Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:14.381480Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:15.383196Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:16.385161Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:17.389275Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:18.394699Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:19.397456Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:20.399159Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:21.402483Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:22.405196Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:23.408958Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:24.426559Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:25.429365Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:26.435364Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:30:27.438240Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11

2023-03-28T07:31:30.677258Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:31:31.680747Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:31:32.695760Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:31:33.703799Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:31:34.709318Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:31:35.729317Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:31:36.733377Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:31:37.755249Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:31:38.763232Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:31:39.764226Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:31:40.766785Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:31:41.772921Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:31:42.778830Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:31:43.784406Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:31:44.793401Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:31:45.799095Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T07:31:45.799689Z 1 [ERROR] [MY-012592] [InnoDB] Operating system error number 11 in a file operation.
2023-03-28T07:31:45.801530Z 1 [ERROR] [MY-012596] [InnoDB] Error number 11 means 'Resource temporarily unavailable'
2023-03-28T07:31:45.801864Z 1 [ERROR] [MY-012215] [InnoDB] Cannot open datafile '/home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1'
2023-03-28T07:31:45.802043Z 1 [ERROR] [MY-012959] [InnoDB] Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2023-03-28T07:31:45.802208Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Cannot open a file.
2023-03-28T07:31:46.131493Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2023-03-28T07:31:46.141460Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2023-03-28T07:31:46.141837Z 0 [ERROR] [MY-010119] [Server] Aborting
2023-03-28T07:31:46.157201Z 0 [System] [MY-010910] [Server] /home/polarx/PolarDB-X/build/run/galaxyengine/u01/mysql/bin/mysqld: Shutdown complete (mysqld 8.0.18)  Source distribution.
2023-03-28T10:39:48.781928Z 0 [Warning] [MY-011069] [Server] The syntax 'avoid_temporal_upgrade' is deprecated and will be removed in a future release.
2023-03-28T10:39:48.781961Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2023-03-28T10:39:48.782021Z 0 [Warning] [MY-011069] [Server] The syntax '--log-bin-use-v1-row-events' is deprecated and will be removed in a future release.
2023-03-28T10:39:48.782097Z 0 [Warning] [MY-011069] [Server] The syntax '--master-info-file' is deprecated and will be removed in a future release.
2023-03-28T10:39:48.782123Z 0 [Warning] [MY-011069] [Server] The syntax '--relay-log-info-file' is deprecated and will be removed in a future release.
2023-03-28T10:39:48.782134Z 0 [Warning] [MY-011069] [Server] The syntax 'show_old_temporals' is deprecated and will be removed in a future release.
2023-03-28T10:39:48.782167Z 0 [Warning] [MY-010084] [Server] options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if --slow-query-log is not set
2023-03-28T10:39:48.782169Z 0 [Warning] [MY-010086] [Server] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-03-28T10:39:48.782235Z 0 [System] [MY-010116] [Server] /home/polarx/PolarDB-X/build/run/galaxyengine/u01/mysql/bin/mysqld (mysqld 8.0.18) starting as process 287054
2023-03-28T10:39:48.784923Z 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.
2023-03-28T10:39:49.231151Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:39:50.232598Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:39:51.234561Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:39:52.236537Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:39:53.238283Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:39:54.289826Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:39:55.322194Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:39:56.325625Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:39:57.330454Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:39:58.369560Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:39:59.381330Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:40:00.383139Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:40:01.384126Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:40:02.389972Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:40:03.404949Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:40:04.407080Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:09.672781Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:10.683610Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:11.686579Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:12.690822Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:13.694986Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:14.697298Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:15.699650Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:16.702494Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:17.705129Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:18.708497Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:19.713231Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:20.719700Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:21.723806Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:22.729398Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:23.733407Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:24.744283Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:25.748735Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:26.756356Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:27.757232Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:28.763594Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:29.766652Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock /home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1 error: 11
2023-03-28T10:41:29.768730Z 1 [ERROR] [MY-012592] [InnoDB] Operating system error number 11 in a file operation.
2023-03-28T10:41:29.768888Z 1 [ERROR] [MY-012596] [InnoDB] Error number 11 means 'Resource temporarily unavailable'
2023-03-28T10:41:29.773204Z 1 [ERROR] [MY-012215] [InnoDB] Cannot open datafile '/home/polarx/PolarDB-X/build/run/galaxyengine/data/mysql/ibdata1'
2023-03-28T10:41:29.773422Z 1 [ERROR] [MY-012959] [InnoDB] Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2023-03-28T10:41:29.773612Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Cannot open a file.
2023-03-28T10:41:30.274844Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2023-03-28T10:41:30.306192Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2023-03-28T10:41:30.309188Z 0 [ERROR] [MY-010119] [Server] Aborting
2023-03-28T10:41:30.323223Z 0 [System] [MY-010910] [Server] /home/polarx/PolarDB-X/build/run/galaxyengine/u01/mysql/bin/mysqld: Shutdown complete (mysqld 8.0.18)  Source distribution.

DDL任务无法删除或取消

1、创建表:
CREATE TABLE test (
col1 varchar(255) DEFAULT NULL,
col2 varchar(255) NOT NULL,
id int(11) NOT NULL AUTO_INCREMENT,
PRIMARY KEY (id,col2)
) ENGINE = InnoDB DEFAULT CHARSET = utf8 ;

2、删除col2主键字段
ALTER TABLE test
DROP PRIMARY KEY,
DROP COLUMN col2,
ADD PRIMARY KEY (id) USING BTREE;

报错:Failed to execute the DDL task. Caused by: Illegal Capacity: -1

4、执行SHOW FULL DDL有条DDL任务执行失败,状态为:PAUSED

5、执行 CANCEL DDL job_id无法取消DDL任务

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.