In the previous blog, we were able to setup a MySQL NDB Cluster replication between one source and one replica cluster. In this blog, we will discuss about replication between one source and three replica clusters.

Note: With MySQL version (8.0.21), we have started changing the term “master” to “source”, the term “slave” to “replica”. So in this blog we will refer these terms ‘source’ and ‘replica’ wherever applicable.

The main advantage of this type of topology is good for giving ‘local’ reads in geographically distant areas as well as increased redundancy in case of issues.

Let’s create four MySQL NDB Cluster with the following environment, from which one will be termed as ‘source’ cluster while the rest will be ‘replica’ clusters.

• MySQL NDB Cluster version (Latest GA version)
• 1 Management node
• 4 Data nodes …

In this blog series, we will discuss various MySQL NDB Cluster replication topologies possible with a demonstration. We will start with a simple case i.e. one source (formerly called master) and one replica (formerly called slave).

Note: With MySQL version (8.0.21), we have started changing the term “master” to “source”, the term “slave” to “replica”. So in this blog we will refer these terms ‘source’ and ‘replica’ wherever applicable.

Let’s create two MySQL NDB Cluster with the following environment, from which one will be termed as ‘source’ cluster while the other one will be ‘replica’ cluster. For now, let’s stick to the identical environment from both the cluster. Later in the following blog series, we will change the environments and will run the replication.

• MySQL NDB Cluster version (Latest GA version)
• 1 Management node
• 4 Data nodes …

The article provides a detailed overview of how to create a database in MySQL using different methods and tools (including the Command Line, Workbench, and dbForge Studio for MySQL). MySQL is a relational database management system based on SQL. It is developed, distributed, and supported by the Oracle Corporation. MySQL is free and open-source software […]

The post Creating a New Database in MySQL: Tutorial with Examples appeared first on Devart Blog.

This blog post is the third part of the series of blogs about indexes in MySQL. In the second part of the blog post series about MySQL indexes, we covered indexes and storage engines and touched upon some PRIMARY KEY considerations. The discussion included how to match a column prefix, some FULLTEXT index considerations, and how you should use B-Tree indexes with wildcards and how to use ClusterControl to monitor your queries' performance, subsequently, indexes. 

In this blog post, we will go into some more details about indexes in MySQL: we will …

The architecture of the world’s most popular open source database system is very important for the Information Technology people. There are many reasons for MySQL’s popularity around the world, but one of the main reasons is its architecture, while there are many big players such as Oracle, Microsoft SQL and DB2, MySQL’s architecture makes it as unique and preferred choice for most of the developers. In this article, we are going to discuss about of the internal architecture of the MySQL relational database management system. The article is for novice database administrators, database developers, software developers and those who are interested to work with MySQL database.Major components The MySQL architecture describes how the different components of a MySQL system relate to one another. The MySQL architecture is basically a client – server system. MySQL database server is the server and the applications which are connecting to MySQL …

Join us on May 20, 2021 at 9AM PST for a live webinar focused on the new MySQL 8.0 features. The webinar will cover the key new features introduced in MySQL 8.0 up to the recently released 8.0.24 and 8.0.25.

The latest versions introduce several new improvements and updates for Optimizer, GIS, InnoDB, Performance schema, Replication, Group Replication, Router, MTR Testsuite, and more. The webinar will highlight the key benefits of each and best practices on how to use them.

Register now

• Date: May 20, 2021 @9AM PST
• Speaker: Harsh Nayak 

Additional Resources:

Top MySQL 8.0.24 blogs:

Overview:  …

Join us on May 20, 2021 at 9AM PST for a live webinar focused on the new MySQL 8.0 features. The webinar will cover the key new features introduced in MySQL 8.0 up to the recently released 8.0.24 and 8.0.25. The latest versions introduce several new improvements and updates for Optimizer, GIS, InnoD...

The MySQL Engineering team is proud to announce the Data Import feature in MySQL Database Service (MDS) and HeatWave.

The new Data Import enables faster and easier migrations to the MySQL Database Service. You can migrate from virtually any MySQL source, like AWS RDS/Aurora or MySQL on-premise, and from different versions, including 8.0, 5.7, or 5.6, directly to MySQL Database Service.

To migrate your existing MySQL databases, you perform two easy steps, in sequence or in parallel:

1. Use MySQL Shell to export data from an existing MySQL source into an OCI Object Storage bucket;
2. In MDS, create a new MySQL DB System referencing the bucket using a Pre-Authenticated Request (PAR). The data is imported automatically!

Together with MySQL Shell, MDS Data Import functionality dramatically reduces …

The MySQL Engineering team is proud to announce the Data Import feature in MySQL Database Service (MDS) and HeatWave. The new Data Import enables faster and easier migrations to the MySQL Database Service. You can migrate from virtually any MySQL source, like AWS RDS/Aurora or MySQL on-premise, and ...

MySQL is heavily tunable and some of the configuration can have significant impact on its performance. During my experiment for numa scalability I encountered one such configuration. Default configuration tends to suggest heavy contention for write workload but once tuned it helps scale MySQL by more than 2x.

Understanding the problem

I started testing write-workloads with different numa levels (1 numa [32 cores]/2 numa [64 cores]/ 4 numa [128 cores]) and observed a weird behavior.

• With increasing compute power we expected throughput to grow. The pattern is observed when we move from 1 numa to 2 numa but there is significant throughput loss (despite double compute power) when switched from 2 numa to 4 numa.
• This is exactly what we call as NUMA SCALABILITY BOTTLENECK (vs a SCALABILITY BOTTLENECK that tends to achieve optimal performance with a given set of compute and io …