Proxysql ha plam_2016_2_keynote

Percona Live Europe 2016Use ProxySQL to Improve Your

MySQL High Availability SolutionMarco Tusa Manager Consulting

Amsterdam, Netherlands | October 3 – 5, 2016

● Marco “The Grinch” • Open source enthusiast

About me

What is HA

What is HA9 0. 0 0 0 % (36 days) MySQL Replication 9 9. 9 0 0 % (8 hours) Linux Heartbeat with DRBD 9 9. 9 0 0 % (8 hours) RHCS with Shared Storage (Active/Passive) 9 9. 9 9 0 % (52 minutes) MHA with at least 3 nodes 9 9. 9 9 0 % (52 minutes) Linux Heartbeat with DRBD and Replication 9 9. 9 9 0 % (52 minutes) Linux Heartbeat with Shared Storage and Replication 9 9 .9 9 5 % (26 minutes) Multi Master (galera - percona cluster) 3 node minimum 9 9. 9 9 9 % (5 minutes) MySQL Cluster

What is HA

Objectively What we have is:

MySQL Group Replication

The telephone game

All talking

Black box:

Use the Right Tool for the Job…

What we need

ProxySQL

Understand the basics

Write / Read (Master/Slave)

Multiple Writers

Multiple WritersSharding &

Geographic Distribution

Mirroring

Query re-write

Understand the basics – how this is done?

Servers group by function

Servers group by functionHost Groups

Rules define what, where and how

Rules define what, where and howQuery Rules

Special Grouping for Replication

Special Grouping for ReplicationReplication Host Group

HostGroup (HG) & Replication HG

Query rules

Scheduler

Basic scenario

HG: 10U: app_RW

HG: 11U: app_R

HG: 12U: ETL_R

insert into mysql_users (username,password,active,default_hostgroup,default_schema) values ('app_RW','test',1,10,'test_schema');

insert into mysql_users (username,password,active,default_hostgroup,default_schema) values ('app_R','test',1,11,'test_schema');

insert into mysql_users (username,password,active,default_hostgroup,default_schema) values ('etl_R','test',1,12,’etl_schema'); LOAD MYSQL USERS TO RUNTIME;SAVE MYSQL USERS TO DISK;

Basic scenario - Users

INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight) VALUES ('192.168.1.5',10,3306,1000); INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight, max_replication_lag) VALUES ('192.168.1.6',11,3306,1000000,2); INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight, max_replication_lag) VALUES ('192.168.1.7',11,3306,1000000,2); INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight, max_replication_lag) VALUES ('192.168.1.5',11,3306,1,2); INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight) VALUES ('192.168.1.8',12,3306,10); INSERT INTO mysql_replication_hostgroups VALUES (10,11); LOAD MYSQL SERVERS TO RUNTIME; SAVE MYSQL SERVERS TO DISK;

Basic scenario – Servers / HG

insert into mysql_query_rules (username,destination_hostgroup,active,retries,match_digest,apply) values(’app_RW',10,1,3,'^SELECT.*FOR UPDATE',1); insert into mysql_query_rules (username,destination_hostgroup,active,retries,match_digest,apply) values(’app_RW',11,1,3,'^SELECT ',1); insert into mysql_query_rules (username,destination_hostgroup,active) values(’app_R',11,1); insert into mysql_query_rules (username,destination_hostgroup,active) values('etl_R',12,1);

LOAD MYSQL QUERY RULES TO RUNTIME;SAVE MYSQL QUERY RULES TO DISK;

Basic scenario – Query rules

Basic scenario – with ProxySQL

Writes

ReadsReads

READ_ONLY = 0 WRITE HG READ_ONLY = 1 READ HG

ProxySQL – Replication HG

READ_ONLY=0 READ_ONLY=1 READ_ONLY=1

HG 11 HG 11HG 10 & HG 11

READ_ONLY=0 READ_ONLY=1

HG 10 & HG:11 HG 11

READ_ONLY=0

HG 10 & HG 11

READ_ONLY=0 READ_ONLY=1

HG 10 & HG:11 HG 11

READ_ONLY=0

HG 10 & HG 11

ProxySQL + MHA (or any controller)

Writes

ReadsReads

Writes

ReadsReads

Writes

ReadsReads

No movable part like:

No movable part like:VIP

DNS (Route 53 or similar)

DNS (Route 53 or similar)No Crazy scripts to manage other proxy (ie HAProxy)

Better distributed HA

What timing with MHA?

MHA discovery time (ping x 3 times) -> ~9 sec

MHA discovery time (ping x 3 times) -> ~9 secMHA recovery (binlog) variable time

MHA Slave shift + Master READ-ONLY < 2 sec

ProxySQL will react as soon as READ_ONLY=0

Nothing all defaults

master_ip_failover_script=master_ip_failover master_ip_online_change_script=master_ip_online_change

Test it:masterha_master_switch --master_state=alive --conf=/etc/mha.cnf --orig_master_is_new_slave --interactive=0 --running_updates_limit=0

What is needed with MHA?

Given no VIP or centralize element.

Why better distributed HA?

Integration with PXC\Galera

Integration with PXC\Galera read_only wsrep_status wsrep_rejectqueries wsrep_donorrejectqueries wsrep_connected wsrep_desinccount wsrep_ready wsrep_provider wsrep_segment Number of nodes in by segment Retry loop

Online Offline_soft Offline_hard Shunned

Integration with PXC\Galera read_only wsrep_status wsrep_rejectqueries wsrep_donorrejectqueries wsrep_connected wsrep_desinccount wsrep_ready wsrep_provider wsrep_segment Number of nodes in by segment Retry loop

Online Offline_soft Offline_hard Shunned

But we also have Hostgroups Replication HG

HG: 10

HG: 12HG: 11

HG: 11HG: 12

Multiple writer vs Single writer

Multiple writer vs Single writerMulti writer based on weight and Hostgroups

Need Replication HG and READ_ONLY

Need Replication HG and READ_ONLYFailover is done without the need of performing actions on the nodes

Failover is done modifying the READ_ONLY value

Failover is done modifying the READ_ONLY valueSingle WRITER node isolation not guarantee

Single WRITER node isolation is guarantee

insert into mysql_users (username,password,active,default_hostgroup,default_schema) values ('app_RW','test',1,10,'test_schema');

insert into mysql_users (username,password,active,default_hostgroup,default_schema) values ('app_R','test',1,11,'test_schema');

insert into mysql_users (username,password,active,default_hostgroup,default_schema) values (‘appDR_R','test',1,12,’etl_schema'); LOAD MYSQL USERS TO RUNTIME;SAVE MYSQL USERS TO DISK;

Integration with PXC\Galera - Users

insert into mysql_query_rules (username,destination_hostgroup,active,retries,match_digest,apply) values(’app_RW',10,1,3,'^SELECT.*FOR UPDATE',1);

insert into mysql_query_rules (username,destination_hostgroup,active,retries,match_digest,apply) values(’app_RW',11,1,3,'^SELECT ',1);

insert into mysql_query_rules (username,destination_hostgroup,active) values(’app_R',11,1);

insert into mysql_query_rules (username,destination_hostgroup,active) values(‘appDR_R',12,1); LOAD MYSQL QUERY RULES TO RUNTIME;SAVE MYSQL QUERY RULES TO DISK;

Integration with PXC\Galera – QR

INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight)

VALUES ('192.168.1.5',10,3306,1000000000); 192.168.1.6 … 10000; 192.168.1.7 … 10

INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight) VALUES ('192.168.1.5',11,3306,1); 192.168.1.6 … 100000; 192.168.1.7 … 100000

INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight) VALUES ('192.168.1.8',12,3306,100); 192.168.1.9 … 100; LOAD MYSQL SERVERS TO RUNTIME; SAVE MYSQL SERVERS TO DISK;

Integration with PXC\Galera – HG MW

INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight) VALUES

('192.168.1.5',10,3306,100);

INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight) VALUES

('192.168.1.5',11,3306,1); INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight) VALUES

('192.168.1.6',11,3306,100); INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight) VALUES

('192.168.1.7',11,3306,100);

INSERT INTO mysql_servers (hostname,hostgroup_id,port,weight) VALUES ('192.168.1.8',12,3306,100); 192.168.1.9 … 100; INSERT INTO mysql_replication_hostgroups VALUES (10,11); LOAD MYSQL SERVERS TO RUNTIME; SAVE MYSQL SERVERS TO DISK;

Integration with PXC\Galera HG SW

ProxySQL is configured Now what?

Integration with PXC

Example scripthttps://github.com/Tusamarco/proxy_sql_toolsFull guide: https://goo.gl/vcDFZx

Set the script: INSERT INTO scheduler (id,active,interval_ms,filename,arg1) values (10,0,2000,"/var/lib/proxysql/galera_check.pl","-u=admin -p=admin -h=192.168.1.50 -H=500:W,501:R -P=3310 --execution_time=1 --retry_down=2 --retry_up=1 --main_segment=1 --debug=0 --log=/var/lib/proxysql/galeraLog"); LOAD SCHEDULER TO RUNTIME;SAVE SCHEDULER TO DISK; update scheduler set active=1 where id=10; LOAD SCHEDULER TO RUNTIME;

+--------------+-------------+--------+------------+---------+ | hostgroup_id | hostname | status | weight | comment | +--------------+-------------+--------+------------+---------+ | 10 | 192.168.1.5 | ONLINE | 1000000000 | | | 10 | 192.168.1.6 | ONLINE | 10000 | | | 10 | 192.168.1.7 | ONLINE | 10 | | | 11 | 192.168.1.5 | ONLINE | 1 | | | 11 | 192.168.1.6 | ONLINE | 100000 | | | 11 | 192.168.1.7 | ONLINE | 100000 | | | 12 | 192.168.1.8 | ONLINE | 100 | | | 12 | 192.168.1.9 | ONLINE | 100 | | +--------------+-------------+--------+------------+---------+

Integration with PXC MW

+--------------+-------------+--------+------------+---------+ | hostgroup_id | hostname | status | weight | comment | +--------------+-------------+--------+------------+---------+ | 10 | 192.168.1.5 |OFFLINE_SOFT | 1000000000 | 10_W_11_R_retry_up=0;10_W_11_R_retry_down=0; | 10 | 192.168.1.6 | ONLINE | 10000 | | | 10 | 192.168.1.7 | ONLINE | 10 | | | 11 | 192.168.1.5 | OFFLINE_SOFT | 1 | ... | | 11 | 192.168.1.6 | ONLINE | 100000 | | | 11 | 192.168.1.7 | ONLINE | 100000 | | | 12 | 192.168.1.8 | ONLINE | 100 | | | 12 | 192.168.1.9 | ONLINE | 100 | | +--------------+-------------+--------+------------+---------+

+---------------------------------+-------+| Variable_name | Value |+---------------------------------+-------+| wsrep_sst_donor_rejects_queries | ON |+---------------------------------+-------+

ProxySQL Think all is ok

Application writes will fail

+--------------+-------------+--------+------------+---------+ | hostgroup_id | hostname | status | weight | comment | +--------------+-------------+--------+------------+---------+ | 10 | 192.168.1.6 | ONLINE | 10000 | | | 10 | 192.168.1.7 | ONLINE | 10 | | | 11 | 192.168.1.6 | ONLINE | 100000 | | | 11 | 192.168.1.7 | ONLINE | 100000 | | | 12 | 192.168.1.8 | ONLINE | 100 | | | 12 | 192.168.1.9 | ONLINE | 100 | | | 9010 | 192.168.1.5 | ONLINE | 1000000000 | | | 9011 | 192.168.1.5 | ONLINE | 1 | | +--------------+-------------+--------+------------+---------+

WRITE Fail-over is automatically perform by ProxySQL

following the weight Until an active node exists the HG

WRITE Fail-over will not happen

Until READ_ONLY variable is modified on a reader HG node.

WRITER if DONOR will never be OFFLINE_SOFT

Integration with PXC SW

Integration with PXC\Galera SW manual

Integration with PXC\Galera SW Auto

Change state to: OFFLINE_SOFT = ~2 sec

HostGroup 9000 = ~2 sec

ProxySQL Shunned = ~1.2 sec (5 fails in 1sec)

Failover (auto) = ~3 sec

Integration with PXC - Timing

Avoid SPOF

Cost in time

So what.. 9 0. 0 0 0 % (36 days) MySQL Replication 9 9. 9 0 0 % (8 hours) Linux Heartbeat with DRBD 9 9. 9 0 0 % (8 hours) RHCS with Shared Storage (Active/Passive) 9 9. 9 9 0 % (52 minutes) MHA with at least 3 nodes 9 9. 9 9 0 % (52 minutes) Linux Heartbeat with DRBD and Replication 9 9. 9 9 0 % (52 minutes) Linux Heartbeat with Shared Storage and Replication 9 9 .9 9 5 % (26 minutes) Multi Master (galera - percona cluster) 3 node minimum 9 9. 9 9 9 % (5 minutes) MySQL Cluster

Brief summary

Improve service flexibility with r/w split;

Brief summary

Improve service flexibility with r/w split;Allow simple way to manage access to specific servers by

usage (like DW-ETL);

Brief summary

usage (like DW-ETL);Implement sharding;

Brief summary

Allow Query revrite/query fix/blocking without need to modify code;

Brief summary

Improve failover time;

Brief summary

Improve failover time;Reduce master downtime impact on reads;

Brief summary

Improve failover time;Reduce master downtime impact on reads;

Not SPOF (as vip)

Brief summary

Contacts

To contact Me

Marco.tusa@percona.com

marcotusa@tusacentral.net

To follow me

http://www.tusacentral.net/

http://www.percona.com/blog/

https://www.facebook.com/marco.tusa.94

@marcotusa

http://it.linkedin.com/in/marcotusa/

“Consulting = No mission refused!”

Proxysql ha plam_2016_2_keynote

Presentations & Public Speaking

Transcript of Proxysql ha plam_2016_2_keynote

Webinar slides: MySQL & MariaDB load balancing with ProxySQL & ClusterControl: introduction webinar

HA-FX24W / HA-FX22W / HA-EN15W / HA-EC25W Sehr geehrter ...

]s - Началоagup.varna.bg/.../article/492/a_2014_1_PROTOKOL_ESUT.pdfP O T O K O r. Ha Ha No Ha ' I sa Ha - Ha Ha crc ...

Webinar slides: High Availability in ProxySQL

HA HA HA GIF MANIA 02

vinod...ha ha ha..

HA HA HA GIFMANIA 01

P ersonality Development Seminar ha Ha ha ho Ha ho ha ho.

Proxysql sharding

The Proxy Wars: MySQL Router, ProxySQL, MariaDB MaxScale · The Proxy Wars: MySQL Router, ProxySQL, MariaDB MaxScale Colin Charles, Chief Evangelist, Percona Inc. colin.charles@percona.com

Proxysql use case scenarios plam 2016

ProxySQL Tutorial - PLAM 2016

Percona Live 2017 ProxySQL Sharding · Percona Live 2017 ProxySQL Sharding Marco tusa Santa Clara, California April 24th – 27th, 2017

Ministry of Energy, Mines and Natural Gas Geoscience and … · 2014. 4. 3. · $832.62/Ha $4066.32/Ha $ 176. /Ha $482.88/Ha $482.88/Ha $1622.77/Ha $4188.55/Ha $151.33/Ha $2512.88/Ha

HA-2520, HA-2522 , HA-2525 Datasheet - Renesas Electronics

ProxySQL Tutorial High Performance & High Availability Percona … · 2016-10-14 · ProxySQL Tutorial High Performance & High Availability Proxy for MySQL With a GPL license! Amsterdam,

HA HA HA GIF MANIA 03

20 Ha Ha Definitions

Consistent Reads Using ProxySQL and GTID...7 Master - Slave Replication Pain Points • Asynchronous replication • Replication lag is the major challenge• Semi-synchronous replication

HA and clustering solution: ProxySQL as an intelligent ... and clustering solution: ProxySQL as an intelligent router for Galera and Group Replication Rene Cannao ProxySQL. ... configuration