234 Commits (cf85780f03b9600a38b1cb60ce1808cb64bfe011)

Author	SHA1	Message	Date
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ò	848ddb2177	Added variable mysql-connect_timeout_client ... This also fix bug #1132	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ò	4748c7d052	Various bug fixes related to deprecated mysql-default_ variables ... Extended `mysql_variable_st` to add a new variable `is_global_variable`. Using this variable we define the global variables. Modified `mysql_tracked_variables[]` to also specify `is_global_variable`. Removed `default_charset` from `MySQL_Threads_Handler::variables` to use `mysql_tracked_variables[]` instead. Removed `default_charset` also from `mysql_thread_variables_names[]`. Fixed `MySQL_Threads_Handler::get_variable_string()` : it was *not* returning `mysql-default_` variables. `MySQL_Threads_Handler::set_variable()` adds `mysql-default_` variables only if `is_global_variable` is set. In `MySQL_Threads_Handler::set_variable()` replaced a `strcasecmp()` with `strcmp()` for `mysql-default_` variables. `MySQL_Threads_Handler::get_variables_list()` returns only `mysql-default_` variables with `is_global_variable` enabled. `MySQL_Threads_Handler::has_variable()` for `mysql-default_` variables returns true only if variable has `is_global_variable` enabled. `MySQL_Thread::refresh_variables()` does not refresh `mysql-default_` variables if `is_global_variable` is not enabled. `MySQL_Thread::MySQL_Thread()` initializes to NULL all `mysql_thread___default_variables[]` variables. Completely disabled in `ProxySQL_Admin::flush_mysql_variables___database_to_runtime()` the logic applied to all charset variables. In the same methos was implemented the logic described in #1785 : `mysql-default_charset` and `mysql-default_collation_connection` must be compatible: * if only one is present, the other is configured automatically * if not compatible, `mysql-default_charset` is configured from `mysql-default_collation_connection`	6 years ago
Javier Jaramago Fernández	cbf11dfcff	Fix crashes related to accesses to worker threads during initialization / shutdown stages	6 years ago
Javier Jaramago Fernández	68891d3703	Merge branch 'v2.1.0' of github.com:sysown/proxysql into v2.1.0-266_0-3	6 years ago
René Cannaò	0a78949d98	Merge branch 'v2.1.0' into v2.0.11-prometheus	6 years ago
Javier Jaramago Fernández	f82f239808	Added support for grouping queries in 'stats_mysql_query_digest'	6 years ago
René Cannaò	543b96facf	Merge pull request #2651 from sysown/v2.0.11-aux ... V2.0.11 aux	6 years ago
Javier Jaramago Fernández	7c561bc701	Added serveral 'global_variables' metrics	6 years ago
Javier Jaramago Fernández	5feea37abb	Moved third-party prometheus included headers before project includes	6 years ago
Javier Jaramago Fernández	a4e4e57343	Moved all 'metrics_maps' to source files	6 years ago
Javier Jaramago Fernández	864535d3f9	Added support for GCC 4.8 and removed per-module metrics initialization functions ... - GCC 4.8 and 5 have issues with uniform initialization syntax, for this reason, all it's uses have been replaced with assignements. - Per-module metrics initialization functions are no longer required, they have been replaced with the new generic ones.	6 years ago
René Cannaò	8cc88ce58e	Migration of threads status variables as array	6 years ago
Javier Jaramago Fernández	b6bca5a3ee	Added metrics help and replaced metrics impl with new array based one for 'mysql_threads_handler' module	6 years ago
Javier Jaramago Fernández	3256fb50d8	Changed metric name, fixed metric update and standarized the metrics update callback	6 years ago
Javier Jaramago Fernández	c319db2c3d	Added new prometheus metrics mimicking current ones	6 years ago
val	d0d7018e34	rollback session_track_gtids	6 years ago
val	b0ca1a030f	make MySQL_Variables a global variable	6 years ago
Valentin Rakush	61c1913334	Character set handling implementation	6 years ago
René Cannaò	c28deb7c7d	Generalize the use of session variables ... Added new array mysql_tracked_variables[] that defines the tracked variables. Ideally, tracking a new session variable will requires adding only a couple of lines of code. Removed session variables from mysql_thread_variables_names: - now both MySQL_Threads_Handler::get_variables_list() and MySQL_Threads_Handler::has_variable() rely on mysql_tracked_variables[] Simplified MySQL_Variables, as it now also uses mysql_tracked_variables[] . Simplify parser in MySQL_Session Generalized code to handle two variables together: - sql_auto_is_null - sql_safe_updates Migrating more session variables to new algorithm - collation_connection - net_write_timeout - max_join_size Migrating more session variables to new algorithm - collation_connection - net_write_timeout - max_join_size	6 years ago
René Cannaò	7dd76aed94	Merge pull request #2637 from sysown/v2.0.11-warmup ... V2.0.11 warmup	6 years ago
René Cannaò	8a0e1c1748	Simplifying MySQL_Thread::run() phase 6	6 years ago
René Cannaò	9c2750027d	Simplifying MySQL_Thread::run() phase 5	6 years ago
René Cannaò	da21ca1b24	Simplifying MySQL_Thread::run() phase 4	6 years ago
René Cannaò	72912f0b88	Simplifying MySQL_Thread::run() phase 3	6 years ago
René Cannaò	64bc42a122	Simplifying MySQL_Thread::run() phase 2	6 years ago
René Cannaò	75606bb94d	Simplifying MySQL_Thread::run() phase 1	6 years ago
val	b1339faefd	Revert "Generalize the use of session variables" ... This reverts commit d242771a25.	6 years ago
val	eb08620181	Revert "Character set handling implementation" ... This reverts commit 796ea5b215.	6 years ago
René Cannaò	29142e6e4f	Global connection warming support ... Port of PR #2496 to 2.0.11	6 years ago
Valentin Rakush	796ea5b215	Character set handling implementation	6 years ago
René Cannaò	d242771a25	Generalize the use of session variables ... Added new array mysql_tracked_variables[] that defines the tracked variables. Ideally, tracking a new session variable will requires adding only a couple of lines of code. Removed session variables from mysql_thread_variables_names: - now both MySQL_Threads_Handler::get_variables_list() and MySQL_Threads_Handler::has_variable() rely on mysql_tracked_variables[] Simplified MySQL_Variables, as it now also uses mysql_tracked_variables[] . Simplify parser in MySQL_Session Generalized code to handle two variables together: - sql_auto_is_null - sql_safe_updates Migrating more session variables to new algorithm - collation_connection - net_write_timeout - max_join_size Migrating more session variables to new algorithm - collation_connection - net_write_timeout - max_join_size	6 years ago
René Cannaò	e9dc7a9b60	Implementation of SQLI fingerprints whitelist ... libsqlinjection generates a lot of false positives. This commit introduces a new table: mysql_firewall_whitelist_sqli_fingerprints This table can list fingerprints generated by libsqlinjection: if the fingerprint is listed in this table, proxysql will consider it as a false positive. This commit also enables SQLi algorithm only if the query is not already explicitly whitelisted.	6 years ago
René Cannaò	8954b46a02	Error log now lists the SQL injection query ... Also added status variable automatic_detected_sql_injection to count detected SQL injection	6 years ago
René Cannaò	e12a3b2792	Support for automatic SQL injection detection ... Library libjection is being used. New variable mysql-automatic_detect_sqli defines if the feature is enabled or not. If an SQL injection is detected: - the client connection is immediately terminated - an entry in the error log is reported	6 years ago
René Cannaò	57e0b2eb2f	Merge pull request #2403 from sysown/v2.0.9-whitelist ... V2.0.9 whitelist	6 years ago
René Cannaò	485d313514	Further development of firewall whitelist. ... * introduced 2 new variables: - mysql-firewall_whitelist_enabled : defines if the firewall with whitelist algorithm is enabled or not - firewall_whitelist_errormsg : error message returned to the client if an error message is not already set * Query_Processor returns firewall_whitelist_mode to the calling MySQL_Session, but the logging on error log currently happens within the Query_Processor itself * if mysql-firewall_whitelist_enabled is turned on and a user it is not found in mysql_firewall_whitelist_users , the default behavior is that query is rejected * lookup on mysql_firewall_whitelist_users happens for username@ip (specific IP) and username@'' (all IPs) . Match on network subnet is currently not implemented * implemented SAVE MYSQL FIREWALL FROM RUNTIME * fixed implementation of SAVE MYSQL FIREWALL TO DISK * runtime configuration can be viewed in runtime_mysql_firewall_whitelist_rules and runtime_mysql_firewall_whitelist_users	6 years ago
René Cannaò	45e701b54d	Code cleanup and speeding compile time	6 years ago
René Cannaò	a9f5e360c1	Upgrade to MariaDB Connector 3.1.4	6 years ago
Valentin Rakush	1ffd3616c9	Group replication monitoring: count transactions behind events	6 years ago
Valentin Rakush	15f121d82f	handle unknown character set	6 years ago
René Cannaò	50876113f7	Renaming variable aurora_only_read_from_replicas into aurora_max_lag_ms_only_read_from_replicas	6 years ago
René Cannaò	35705f769a	Adding variable aurora_only_read_from_replicas ... If AWS Aurora is used and max_lag_ms , send traffic only to replicas if at least N replicas are good candidates.	6 years ago
Valentin Rakush	1008b7d0c5	unit8_t conversion	6 years ago
René Cannaò	be3bb9629d	Add variable mysql-log_unhealthy_connections ... Added new variable mysql-log_unhealthy_connections. Enabled by default. If disabled, warnings `Closing unhealthy client connection` are suppressed.	6 years ago
Valentin Rakush	b13c320210	digests number: converting numbers to ? for digest calculation	7 years ago
René Cannaò	5f8e2acbb9	Change the default for tx_isolation	7 years ago
Valentin Rakush	202cae4c39	set tx_isolation implementation	7 years ago