-
Notifications
You must be signed in to change notification settings - Fork 441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2 nodes of galera cluster (3 nodes totally) restart periodically #398
Comments
I am wondering why the official mariadb image can NOT be configured as cluster easily. and why should we use the wrapper image such as https://hub.docker.com/r/bitnami/mariadb-galera/ or https://hub.docker.com/r/toughiq/mariadb-cluster? I can NOT find any docker-stack.yml which uses "official mariadb image" to deploy mariadb cluster, isn't it a bad thing? |
Occasionally, I checked the description of wsrep-node-address, I removed it, the cluster is started successfully. |
Glad you got it going, I do need to revisit the review of #377 soon. |
`2024-12-18 13:13:21 0 [Note] WSREP: Start replication Your assistance in bug reporting will enable us to fix this for the next release. We will try our best to scrape up some info that will hopefully help Server version: 10.5.26-MariaDB-ubu2004-log source revision: 7a5b8bf0f5470a13094101f0a4bdfa9e1b9ded02 Thread pointer: 0x7fe59c000c58 Trying to get some variables. Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains We think the query pointer is invalid, but we will try to print it anyway. Writing a core file... Kernel version: Linux version 5.4.0-202-generic (buildd@lcy02-amd64-104) (gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.2)) #222-Ubuntu SMP Fri Nov 8 14:45:04 UTC 2024 |
is anyone know what the root cause about the above issue? |
I can't see this as an existing issue so can you create a new issue on https://jira.mariadb.org following https://mariadb.com/kb/en/reporting-bugs. There are two issues:
I can't tell if there's a real possibility that this node is already having a SST in progress from another donor machine, it seems unlikey. But recommend removing this file.
Please include the logs from all nodes. |
Dear experts:
I use bellow docker-stack.yml to start galera cluster with 3 nodes, but 2 nodes of galera cluster (3 nodes totally) restart periodically:
The commands to create network and start the servie stack:
But mariadb02 and mariadb03 restart periodically with bellow errors:
Is there any possible bugs in the docker-stack.yml???
I spent more than 1 week on this issue, please help me!
The text was updated successfully, but these errors were encountered: