[WIP] Cluster improvements #3305
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ProxySQL will now automatically generate a UUID during start up. The UUID can be either passed through the command line using -U or --uuid, or saved on disk in a new table named global_settings. The new table is used to distinguish it from global_variables that is replicated. Table global_settings isn't replicated by Cluster. If UUID is not present, it is automatically generated and saved.
…XYSQL CLUSTER_NODE_UUID command
|
retest this please |
|
|
|
retest this please |
3 core nodes 6 satellite nodes
When a cluster node (client) connects to another cluster node, it advertises its UUID but also exports its `admin-mysql_ifaces` . The receiving cluster can use this information to try to guess how to connect to the node that initialized the connection, for example to collect metrics. This is visible in table `stats_proxysql_servers_clients_status` .
|
retest this please |
|
retest this please |
renecannao
changed the title
It also enables monitoring for cluster test
|
retest this please |
1 similar comment
|
retest this please |
This TAP test assumes that there are a cluster of 10 proxysql nodes
|
retest this please |
1 similar comment
|
retest this please |
|
retest this please |
1 similar comment
|
retest this please |
Similar to commit f8ce413
This mutex was largely deprecated by sql_query_global_mutex . Its presence now was causing a possibl deadlock.
|
retest this please |
Query_Processor::get_current_query_rules_fast_routing_count() now allows to quickly execute this query is ran on Admin: SELECT COUNT(*) FROM runtime_mysql_query_rules_fast_routing
|
retest this please |
|
retest this please |
2 similar comments
|
retest this please |
|
retest this please |
|
retest this please |
1 similar comment
|
retest this please |
…mysql servers tables are going to be written. Before this commit we were calling GloAdmin->mysql_servers_wrlock() at the beginning of the synchronization. This was not ideal as we should call GloAdmin->mysql_servers_wrlock() only if we are really going to write the tables. In other words, only if the resultsets are fetched from the remote peer, and if their checksums didn't change in the meantime.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.