Showing entries 1 to 10 of 61
10 Older Entries »
Displaying posts with tag: MaxScale (reset)
Column Level Masking on MySQL

Data is an invaluable asset to any organisation and every data should not be viable to all DB users. I had a requirement from one of our Support client to hide (mask) a few columns to the end user. Those columns contains sensitive information like payment details and mobile numbers.

In this blog post I am going to explain the how data masking features in Maxscale can be benefitted in such use case.

Maxscale Masking

Masking filter was introduced on the Maxscale 2.1 version . Below is a simple scenario. The columns “name” and “mobile” from the table student has to be masked.

[root@labs7.mydbops.com ~]# maxscale --version                                                           MaxScale 2.3.6

#Table Structure 

mysql> show create table student\G
*************************** 1. row ***************************
       Table: …
[Read more]
Using MariaDB MaxScale for Archiving MariaDB Database with Mq and Tee filters

Archiving MariaDB Database with Mq and Tee filters

This whitepaper is about how to use MariaDB MaxScale filters for Archiving MariaDB database. We have considered two MariaDB / MySQL servers in this exercise, one is the MariaDB Production Database Server and other one for Archiving MariaDB Production Database Server . We have also accommodated RabbitMQ and MariaDB MaxScale servers in their respective Instances .

 

Instance Details IP
MariaDB Production Database Server 192.168.56.101
MariaDB Archive Database Server 192.168.56.102

Our use case is a MariaDB Production Database Server and MariaDB archive Database Server where only INSERT, UPDATE AND …

[Read more]
Summary – Mydbops Database Meetup (Apr-2019)

Conglomeration, Collaboration and Celebration of Database Administrators

Founders of Mydbops envisioned contributing knowledge back to the community. This vision is shaping up in its 3rd edition of the Meetup held on Saturday the 27th of April, 2019. This meetup edition had drawn a good amount of members from the Open Source Database Administrative Community, to the venue.  The core agenda was set on “High Availability concepts in ProxySQL and Maxscale”. There were also presentations in MongoDB Internals along with MySQL Orchestrator and its implementation excellence at Ola (ANI Technologies Pvt. Ltd.)

The participants from various organisations like MariaDB, TeleDNA, CTS, OLA, Infosys, …

[Read more]
MariaDB MaxScale Masking Basics and Examples

I wanted to take a moment to write up a post on MariaDB MaxScale’s masking basics and include some real-world examples.

We have nice documentation on the subject, and Dipti wrote a nice blog post on it as well. I just wanted to provide my take on it, and hopefully build upon what is already there and offer some additional insights.

To provide a 50-foot overview, the masking filter makes it possible to obfuscate the returned value of a particular column.

3 quite common columns where this would be very beneficial: Social Security Number (“SSN”), Date of Birth (“DOB”), and Credit Card Number (“CCNUM”).

To use masking, it assumes you already have a MaxScale service up and running. For instance, the readwrite …

[Read more]
Viewing the Originating Host or IP Address with MaxScale’s Proxy Protocol

If you use MaxScale to route queries from various servers to some MariaDB server(s), when viewing the processlist on the MariaDB server, you will see MaxScale’s host for any “host” information related to that connection or its queries.

When tracking down problematic queries, it can be helpful to know what originating host of that query.

MaxScale’s proxy protocol to the rescue.

The proxy protocol was introduced in MaxScale 2.2 and MariaDB 10.3.

To enable it, it is quite simple (essentially just 2 changes).

1. In MariaDB, you need to set the variable proxy_protocol_networks in your my.cnf file (you can specify comma-separated IP addresses and/or subnetworks, as well as localhost and ::1):

proxy-protocol-networks=::1, 192.168.0.0/16, localhost

This one, which I will use as-is, is the example from the …

[Read more]
Presentation : MySQL Load balancers and its solution

MySQL load balancers becomes a trend setters in Market for High availability and Scalability. They offer variety of solutions for database. What can be the best load balancer ? It varies from case to case. This presentation was made at Mydbops meetup on 04-08-2018 covers the basics of load balancers with their advantages/ disadvantages and use cases.

Scale-with-Maxscale-part5 (Multi-Master)

This is the 5th blog in series of Maxscale blog, Below is the list of our previous blogs, Which provides deep insight for Maxscale and its use cases for different architectures.

[Read more]
Scale with Maxscale part-4 (Amazon Aurora)

This is part-4 of the Maxscale Blog series

  1. Maxscale and Galera
  2. Maxscale Basic Administration
  3. Maxscale for Replication

Maxscale started supporting Amazon Aurora lately from its version 2.1 which comes with a BSL license, we are good until we use only 3 nodes, …

[Read more]
Maxscale Data Archiving with filters Mq & Tee ( Mirror)

Introduction –

          Maxscale is an excellent Proxy from Mariadb Corporation, which providing the High Availability, Realtime RW split with replication Glaera cluster Amazon RDS Amazon Aurora, binlog streaming and many more advanced features, here in this blog we will discuss one such feature, 

In this blog post, i am going to share my recent activity with Maxscale. We had to help one of our client to archive only the DML ( CREATE & INSERT ) data into archive server from specific table.

Problem Statement –

Our client is having only one standalone ( Master ) setup and a Archive server , they need to archive one …

[Read more]
Making Maxscale/ProxySQL Highly Available ( 2 > 1 )

As Mydbops we are implementing Load Balancer using Maxscale or ProxySQL ( Our presentation ) for lot our client,  but these load balancers will become a SPOF (Single Point of failure) .  We have tried to explore services like HAProxy, Nginx, and Keepalived etc. Except Keepalived, all the services need to run on the standalone instance and  did not satisfy our exact need.

Keepalived does not requires any standalone instance, it can be deployed and configured with a minimal effort and provide the HA Solutions to the DB Infra. This approach not only fits for our DB setup, we can implement same …

[Read more]
Showing entries 1 to 10 of 61
10 Older Entries »