xenon
xenon copied to clipboard
The MySQL Cluster Autopilot Management with GTID and Raft
切主后主从不同步
在我的k8s集群里,pod自动发生重启后发生切主。切主后老master会跟新master有主从不同步的情况,sql线程会有1062、1146这样的报错。请问下这是怎么产生的呢?切主后是怎么重新建立主从关系,设置的位点是什么呢?
日志报错
**主节点xenon启动之后日志报错:** 2022/08/04 20:55:44.287645 **[ERROR] server.mysql.start.slave.error[Error 1200: The server is not configured as slave; fix in config file or with** CHANGE MASTER TO] 2022/08/04 20:55:44.287653 [INFO] server.mysql.check.replication.user... 2022/08/04 20:55:44.287816 [INFO] server.mysql.setup.done...
-bash-4.2$ ./xenon -c /etc/xenon/xenon.json xenon:[{Tag: Time:2021/12/03 03:09:25 Git: GoVersion:go1.17.3 Platform:linux amd64}] panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x6fa242] goroutine 1...
xenoncli cluster status查看集群状态时报错: cluster.go:224: **unexpected error: open /home/mysql/config.path: no such file or directory** 2022/08/04 17:45:11.955666 [PANIC] **open /home/mysql/config.path: no such file or directory** panic: [PANIC] open /home/mysql/config.path: no such file...
1. Correct some minor errors in the readme file. 2. Add icons to make it more readable.
你好 、 xenon 研发同学。 部署好的 xenon+mysql 集群已经运行了一段时间, 发现执行 /data/xenon/bin/xenoncli cluster mysql 命令会出现cluster.go:480: unexpected error: get.client.error[dial tcp 192.168.39.167:8801: i/o timeout],如下图所示。  但是过一会执行命令 ,出现 如下情况  后面我把这个 xenon 程序stop ,然后start 。发现xenon的状态是 INVALID...
### version: * Xenon :1.1.4 * MySQL: 8.0.26 ### Error Messages: ```shell tail -f /etc/xenon/log/xenon.log [ERROR] FOLLOWER[ID:192.168.66.101:8801, V:59, E:0].mysql.DisableSemiSyncMaster.error[Error 1193: Unknown system variable 'rpl_semi_sync_master_enabled'] ``` ### Guess: It is suspected...
2021/06/23 16:28:33.908122 [INFO] mysql.slave.status:&{ 0 false false } 2021/06/23 16:28:33.908290 [INFO] mysql.master.status:&{mysql-bin.000017 236 true true 31f483d7-d324-11eb-b1da-000c29a5210a:1-2, 4496becd-d324-11eb-b5d0-000c29d747f6:1-26 0 }