170 Commits (cd352ff141ba2f2fc56ff397a8eccbc176e8b227)

Author	SHA1	Message	Date
Rahim Kanji	4f091109a9	If the 'read_only' value is successfully retrieved from the backend server, update server status from '*SHUNNED' to 'ONLINE' as this indicates that the server is now ONLINE.	3 years ago
Miro Stauder	b1be9b5a71	old gcc fixes	3 years ago
René Cannaò	ef9690967c	Merge branch 'v2.x' into v2.x_refactor_read_only_action_with_simulator	3 years ago
Rahim Kanji	8fa49d79df	* Added few types to make code more readable	3 years ago
Rahim Kanji	0268495d52	* Fixed the functionality of 'mysql-monitor_writer_is_also_reader'	3 years ago
Rahim Kanji	c7c71c99d3	Fixed logging and comments	3 years ago
Rahim Kanji	446c9ec0c8	Added logging	3 years ago
Rahim Kanji	afc06ab8dc	Merge remote-tracking branch 'Master/v2.x_refactor_replication_lag_action' into v2.x_refactor_replication_lag_action	3 years ago
Rahim Kanji	c673ef533f	Removed update code from copy and renamed method to copy_if_not_exists	3 years ago
Rahim Kanji	e0e06711d8	Some improvements and fixes	3 years ago
Rahim Kanji	55deb8ddac	Refactoring replication lag action method ... * Introduced support for handling of bulk servers * Commented mysql_servers_wrlock as this method does not use admin tables.	3 years ago
Rahim Kanji	aaa959d024	Refactor and optimize read-only actions method ... This commit optimizes the read-only actions method by removing the dependency on proxysql admin tables. Instead, a separate mapping container is maintained, which records the state of the HGM servers. This avoids the need to call the commit method on every change, which improves performance. The changes in this commit also ensure that the mapping container is properly updated when servers are added, removed or modified.	3 years ago
René Cannaò	d61c043bdc	Drafting mysql_hostgroup_attributes table	3 years ago
René Cannaò	71e2510ef6	Code cleanup on MySQL_HostGroups_Manager ... Some rework to try to reduce duplicated code	3 years ago
Javier Jaramago Fernández	37efc833e3	Change wording in doc for 'MySQL_HostGroups_Manager::runtime_mysql_servers'	4 years ago
Javier Jaramago Fernández	d8429ca71c	Replace resultset for Cluster request fetching 'runtime_mysql_servers' ... Query 'CLUSTER_QUERY_MYSQL_SERVERS' is now responded by 'runtime_mysql_servers' as it previously was. Documentation reasoning about the change has been added to 'MySQL_HostGroups_Manager::runtime_mysql_servers'.	4 years ago
Javier Jaramago Fernández	099c2a5f06	Cluster: Speedup of processing of MySQL Users and MySQL Servers ... - Cluster now syncs the server tables via 'incoming_*' tables generated during 'load_mysql_servers_to_runtime'. - Cluster now syncs 'mysql_users' table via a resultset generated via '__refresh_users'.	4 years ago
Javier Jaramago Fernández	3dacb77321	Perform atomic update of Cluster fetched module checksum epochs	4 years ago
René Cannaò	7940d867da	Merge pull request #3867 from sysown/v2.x-multilag ... Added mysql-monitor_replication_lag_group_by_host	4 years ago
Javier Jaramago Fernández	5569528b04	Move 'mysql_servers' from 'monitor' db into 'monitor_internal' db ... - Isolate 'mysql_servers' from 'monitor' into 'monitor_internal' db. - Make 'monitor_internal' accessible from Admin for debug builds.	4 years ago
René Cannaò	4bfe3e5878	Added mysql-monitor_replication_lag_group_by_host ... If variable mysql-monitor_replication_lag_group_by_host=false: (default) Monitor will perform 1 replication lag check per server per hostgroup. If variable mysql-monitor_replication_lag_group_by_host=true: Monitor will perform 1 replication lag check per server. This variable need to be set only in setups in which the same server is configured in many hostgroups, thus reducing the number of checks	4 years ago
René Cannaò	6ea642fc55	Merge pull request #3798 from sysown/v2.x-3797 ... Closes #3797: Monitoring not working properly for AWS aurora auto-discovered servers	4 years ago
Javier Jaramago Fernández	c50a7053ad	Fix monitoring not working for AWS Aurora auto-discovered instances #3797 ... - Monitoring actions 'ping' and 'connect' now make use of a new introduced table 'monitor.mysql_servers' instead of 'mysql_servers' table from Admin. - This table is kept in sync via a shared resulset in 'MySQL_HostGroups_Manager'.	4 years ago
Javier Jaramago Fernández	6d59956b5f	Change conn_pool metrics update functions to use 'const refs'	4 years ago
Javier Jaramago Fernández	bcb009fc24	Revert "Merge pull request #3645 from sysown/v2.x-2021" ... This reverts commit 9561cb3ef2, reversing changes made to 7edfec6f3f.	4 years ago
René Cannaò	a6edd02a9b	Revert "Merge branch 'v2.x' into v2.x-2021" ... This reverts commit 3a3931f2d4, reversing changes made to 4694ab775e.	4 years ago
René Cannaò	8cea730de0	Merge pull request #3661 from sysown/v2.x-3649 ... Allow to unshun a server from all hostgroups	4 years ago
René Cannaò	79d1d8742c	Testing unbalanced weight	4 years ago
Javier Jaramago Fernández	6a92cc9238	Added new command 'PROXYSQL_SIMULATOR' with support for simulating connection errors #3649	4 years ago
René Cannaò	4b04332473	Add optional mutex in MySrvC::connect_error()	4 years ago
René Cannaò	a752292b9e	Added function unshun_server_all_hostgroups() ... MySQL_HostGroups_Manager::unshun_server_all_hostgroups() scans all hostgroups looking for a specific server, and if shunned it will bring it back online	4 years ago
René Cannaò	dd71fcd81f	Shun "soft" and "hard" in group replication lag ... When shunning a node due to replication lag in a group replication cluster, we first shun the node as MYSQL_SERVER_STATUS_SHUNNED , then we shun it as MYSQL_SERVER_STATUS_SHUNNED_REPLICATION_LAG . In this way we prevent (for a short time) to kill connections on that backend. This backing off from that server can give the server enough time to sync up. See discussion in comments in https://github.com/sysown/proxysql/pull/3533	5 years ago
Javier Jaramago Fernández	b929758a87	Several improvements to 'group_replication_lag_action' ... 1. Introduced new global variable: 'monitor_groupreplication_max_transaction_behind_for_read_only', that modifies the behavior of 'group_replication_lag'. 2. Improved logic making use of 'MyHGC_find' instead of directly searching 'MyHostGroups' structure. 3. Improved 'group_replication_lag' documentation with new implementation updates. 4. Introduced changes to 'update_group_replication_set_writer' preserving writters placed in 'OFFLINE_SOFT' state.	5 years ago
Javier Jaramago Fernández	0850c4d596	Improved the documentation for 'group_replication_lag_action'	5 years ago
Javier Jaramago Fernández	53bf18b428	Changed setting readonly servers 'OFFLINE' due to replication lag behavior in favor of general server 'SHUNNING'	5 years ago
René Cannaò	257949f623	Removing MySQL_HostGroups_Manager::server_add() ... This function was deprecated in 2016	5 years ago
René Cannaò	6c7503f85f	Improve debugging when unable to reach hostgroup ... When we generate an error "Max connect timeout reached while reaching hostgroup" for the client, now the error log is more verbose.	5 years ago
René Cannaò	26790c3679	Merge pull request #3349 from sysown/v2.1.1-MonRo ... Optimizations for instances with a lot of hostgroups	5 years ago
René Cannaò	f7754a5e00	HostGroups lookup using unordered_map ... HostGroups are stored in an array of pointers. This commit allows the lookup using an unordered_map if the number of Hostgroups is greater than 100. For less number of hostgroups, a sequential scan seems more efficient. This also introduce a test for micro benchmark.	5 years ago
René Cannaò	532a0397f7	Faster MySQL_HostGroups_Manager::read_only_action ... This commit rewrites MySQL_HostGroups_Manager::read_only_action() in way to reduce the calls to SQLite. It relies on two new std::set() : - read_only_set1: if the server is already in a writer hostgroup - read_only_set2: a cache to track the first time that a server has RO=0 Added also an index on MySQL_HostGroups_Manager, ON mysql_servers (hostname,port)	5 years ago
Javier Jaramago Fernández	f31d046868	Removed unused class member 'MySQL_HostGroups_Manager::p_err_map_access'	5 years ago
Javier Jaramago Fernández	d507880cbb	Added new metric 'proxysql_myhgm_auto_increment_multiplex_total' tracking the number of times that 'auto_increment_delay_multiplex' is triggered	5 years ago
Javier Jaramago Fernández	84f4c96afa	Multiple changes to multiple metrics definitions ... - Labelling has been simplified to group metrics which are part of a common group. - Help has been fixed to reflect this labelling change. - Doxygen doc and comment marks has been added to signal metrics grouping.	5 years ago
René Cannaò	aaddb4e568	Port of #3001 to 2.1.0 , related to #3000 ... A client connection can use a backend connection with a session variable set by a different client	6 years ago
René Cannaò	507a68db29	Variable mysql-monitor_replication_lag_count ... Renamed variable mysql-monitor_replication_lag_retries to mysql-monitor_replication_lag_count to match other variables naming convention. As it is a counter, it minimum value is changed to 1. Maximum value sets to 10. Use of thread storage variable mysql_thread___monitor_replication_lag_count instead of GloMTH->variables.monitor_replication_lag_retries to avoid dirty reads .	6 years ago
Javier Jaramago Fernández	a2727739e4	Added new variable 'mysql-monitor_replication_lag_retries' ... This new variable controls the number of retries that replication lag needs to exceed 'max_replication_lag' in order to set a server SHUNNED.	6 years ago
René Cannaò	33d8db02a6	Change the mapping logic for SESSION_TRACK_GTIDS ... Changing the mapping logic in SESSION_TRACK_GTIDS in frontend and backend connections. Up to now, frontend and backend `SESSION_TRACK_GTIDSs match. This is now changed: * backend connections are by default set to `mysql-default_session_track_gtids` * if `mysql-default_session_track_gtids=OFF` (the default) , `session_track_gtids` is not changed on backend * if the client asks for `session_track_gtids=OFF` , proxysql ignores it (it just acknowledge it) * if the client asks for `session_track_gtids=OWN_GTID` , proxysql will apply it * if the client asks for `session_track_gtids=ALL_GTIDS` , proxysql will switch to OWN_GTID and generate a warning * if the backend doesn't support `session_track_gtids` (for example in MySQL 5.5 and MySQL 5.6), proxysql won't apply it. It knows checking server capabilities This commit also deprecates function `MySQL_Session::handler_again___verify_backend__generic_variable()` ProxySQL is now also able to know when proxysql binlog reader is perhaps in use tracking all gtid_port in mysql_servers. This feature in future will be used to deprecate `mysql-default_session_track_gtids`	6 years ago
René Cannaò	0a78949d98	Merge branch 'v2.1.0' into v2.0.11-prometheus	6 years ago
val	eb638a1b16	fix for galera set writer	6 years ago
Javier Jaramago Fernández	7f8b07a0db	Created new metric counters for registering 'mysql_errors'	6 years ago