One thing that we announced in the GA release of MySQL Cluster
that we now support using 3 and 4 replicas. Actually the NDB software
was designed to support 1 through 4 replicas from the very get go in the
1990s. The reason it has not been supported is simply that we haven't
had any regular testing effort attached to it. Thus we haven't felt that
we can support such an important feature without having proper testing
What we did in the development of MySQL Cluster 8.0 is that we have
added a number of new configurations with both 3 replicas and with
4 replicas. These configurations will now be used in our daily testing
In the process of working on this we found some issues with arbitration
already in MySQL Cluster 7.6. This issue was fixed in 7.6 already.
So the way to decide how to handle a node failure in 7.6 and …
One thing that we announced in the GA release of MySQL Cluster
MySQL 8.0.19 came out this week and can he downloaded here.
One of the first things I do when a new release happens is
look at the release notes. The release note cover the
changes from the previous versions and the latest edition edition details some
interesting new stuff.
MySQL now enables administrators to configure user accounts such that too many consecutive login failures due to incorrect passwords cause temporary account locking. The required number of failures and the lock time are configurable per account, using the FAILED_LOGIN_ATTEMPTS and PASSWORD_LOCK_TIME options of the CREATE USER and ALTER USER statements.
YEAR(4) and …
In this blog post, we will continue to explore Vitess and test an example database provided in its repository. This is Part III of the previously discussed installation of Vitess on minikube environment, so please make sure to follow those steps to bring the cluster up to the following level.
$ kubectl get pods,jobs NAME READY STATUS RESTARTS AGE po/etcd-global-kbbcqlgvp9 1/1 Running 0 43m po/etcd-zone1-lpc5zmdxxn 1/1 Running 0 43m po/my-release-etcd-operator-etcd-backup-operator-6684dd6d8c-pr4n4 1/1 Running 0 1h po/my-release-etcd-operator-etcd-operator-86d94989d6-w9lpx 1/1 Running …[Read more]
FEMP is an acronym that stands for FreeBSD (operating system), Nginx (HTTP server pronounced Engine-x), MySQL (database server), and PHP (programming language to process dynamic PHP content). In this tutorial, we'll set up components of a FEMP stack on a FreeBSD 12.1 server using pkg, the FreeBSD package manager.
As you probably noticed MySQL Cluster 8.0 was released yesterday
as a GA release.
One important thing that we changed in the GA release is that we made it possible to
set DataMemory to up to 16 TB.
We are currently working with Intel with machines that can handle 6 TB of memory
and using these machines we have already been able to load more than 5 TB of user
data in the DBT2 benchmark. We will publish more details on the results of those
benchmark investigations later.
Given that we have also improved support for disk data so much in MySQL Cluster 8.0
it means that it is perfectly sensible to store 10s of TB of data in each data node and
even up to 100 TB. So this means that a cluster with 144 data nodes would be able to
store all the way up to 5 PB of data even with 3 replicas.
The changes that made this possible is actually done already in MySQL …
In MySQL 8.0.1, we introduced support for recursive common table expressions (CTE). There are quite a few blog entries showcasing the feature, starting from this one, and there is also a complete documentation. Today, I would like to present a solution to a problem which nearly everybody meets when writing queries with recursive CTE’s: when infinite recursion happens, how to debug ?…
Facebook Twitter LinkedIn
At 13th January 2020, MySQL Community has released the very latest MySQL 8.x version ( 8.0.19 ). The MySQL 8.0.19 has released with the good amount of bug fixes and the cool features . InnoDB ReplicaSet is one of them and most interesting feature for me . In this blog I am going to explain about the configuration of the MySQL InnoDB ReplicaSet and how to do the switchover smoothly with InnoDB ReplicaSet .
What is InnoDB ReplicaSet ?
from MySQL document,
The AdminAPI includes support for InnoDB ReplicaSet, that enables you to administer a set of MySQL instances running asynchronous GTID-based replication in a similar way to InnoDB cluster. A InnoDB ReplicaSet consists of a single primary and multiple secondaries
Note : For configure the InnoDB ReplicaSet , the servers should be configured with the GTID .
InnoDB ReplicaSet configuration …[Read more]
We are pleased to announce the release of MySQL Cluster 8.0.19, a new GA, along with 7.6.13, 7.5.17, 7.4.27, and 7.3.28. MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: In-Memory storage – Real-time performance (with optional checkpointing to disk) Transparent Auto-Sharding – Read & write scalability Active-Active/Multi-Master geographic replication 99.9999% […]
In this blog post, I’d like to share some experiences in setting up a Vitess environment for local tests and development on OSX/macOS. As previously, I have presented How To Test and Deploy Kubernetes Operator for MySQL(PXC) in OSX/macOS, this time I will be showing how to Run Vitess on Kubernetes.
Since running Kubernetes on a laptop is only experimental, I had faced several issues going through straight forward installation steps so I had to apply a few workarounds to the environment. This setup will have only minimum customization involved.
For a high-level overview of Vitess, please visit Part I of this series, …[Read more]
The promise of DBaaS like RDS is to reduce operational overhead (among other things) and one of the stellar cases is upgrades (major and minor). The suggested procedure involves just a couple of steps. For example, using AWS Console, you can enable “Auto minor upgrade” or modify the DB instance and schedule the upgrade to run in the next maintenance window.
But, both these options are risky because the upgrade process will start during the maintenance window but it is NOT guaranteed that the upgrade will be completed within the specified duration.
RDS performs a few extra steps to ensure the data consistency and rollback, making the minor version upgrade a time-consuming process:
- It takes a backup (if automated backups are enabled) prior to starting the upgrade process.
- Performs slow shutdown after setting …