Tag: MySQL

Feed: Planet MySQL; Author: MySQL Performance Blog; In this blog, I want to evaluate Group Replication Scaling capabilities in cases when we increase the number of nodes and increase user connections.For testing, I will deploy multi-node bare metal servers, where each node and client are dedicated to an individual server and connected between themselves by a 10Gb network.Also, I will use 3-nodes and 5-nodes Group Replication setup.Hardware specifications: System | Supermicro; SYS-F619P2-RTN; v0123456789 (Other) Service Tag | S292592X0110239C Platform | Linux Release | Ubuntu 18.04.4 LTS (bionic) Kernel | 5.3.0-42-generic Architecture | CPU = 64-bit, OS = 64-bit Threading | ... Read More

Feed: Planet MySQL; Author: Krunal Bauskar; By and large this would be a topic of interest for most of us including me when I started to explore this space. Before we dwell into the numbers let’s first understand some basic differences between 2 architectures. Beyond being CISC and RISC let’s look at the important differences from MySQL perspective. Strong vs Weak memory model (weak memory model needs proper memory barrier while writing lock-free code). Underlying hardware specific specialized instructions. For example: both now support crc32c hardware instructions but being low-level they are different ways to invoke them. For more differences ... Read More

Feed: Actian. Author: Lewis Carr. In December, January, and February, I posted a short series of blogs on Flat file systems. The series of blogs focus on the continued use of flat files and why they are no longer viable for use in the future.The first installment focused on flat files and why embedded software application developers readily adopted them. Then in the second installment, I discussed why embedded developers are reluctant to use databases. The third installment looked at why developers cling to the flat file systems. The final installment provided a checklist for embedded developers migrating off flat files ... Read More

Feed: Planet MySQL; Author: MySQL Performance Blog; This is a three-part blog series that focuses on dealing with an unexpected high traffic event as it is happening. Part one can be found here, and part two can be found here.  13. Configure MySQL Server ProperlyComplexity:MediumPotential Impact: High A poorly configured MySQL Server can cause severe issues, especially under high load during a traffic spike, yet getting the basics right is not that hard. While MySQL Server has more than 400 variables you can tune, you rarely need to change more than 10-20 of them to get 95% of the possible performance for ... Read More

Feed: Clustrix Blog. Author: Shane Johnson. If you needed an on-premises data warehouse today, would you choose a version of Postgres released in 2005 (Postgres 8.0.2)? How about a version of MySQL released in 2005 (MySQL 5.0.15)? Perhaps you’d ask Oracle if you could use Oracle Database 10g Release 2 even though it was released in 2005 and reached end-of-life a decade ago?I didn’t think so. You know better, and so do I. Amazon? Not so much. They built Redshift on ParAccel Analytic Database (PADB) in 2013, itself built on Postgres 8.0.2. ParAccel would go on to be acquired by ... Read More

Feed: Planet MySQL; Author: MySQL Performance Blog; Percona Server for MySQL 8.0.19 includes the experimental simple LDAP authentication plugin, which allows for direct authentication using an LDAP server. Similarly to the data masking plugin added in 8.0.18, this plugin was also added as a community contribution from Francisco Miguel Biete.Authenticating with LDAPIn earlier versions, Percona Server for MySQL supported the built-in authentication mechanism of MySQL and also included a port of the PAM plugin from MySQL enterprise.As LDAP servers can be configured as backends for PAM, this already provided a way to authenticate SQL users using LDAP, by adding PAM ... Read More

Feed: Planet MySQL; Author: MySQL Performance Blog; This is a three-part blog series that focuses on dealing with an unexpected high traffic event as it is happening. Part one of this series talked about the first six things you can do, and in part two, we will be discussing numbers seven through twelve.7. Get More MemoryComplexity: LowPotential Impact: HighIf your data does not fit into memory well, your MySQL performance is likely to be severely limited. If your data already fits in well, adding even more memory will not provide any performance improvements.Even when you’re running on very fast storage, ... Read More

Feed: Planet MySQL; Author: Dave Stokes; MySQL 8.0.19 introduced the ability to lock an account on a MySQL instance after too many failed logins.  This is not turned on by default, the locking period is measured in days (more below), and I would urge caution as not to 'denial of service' yourself out of your server. SyntaxCREATE USER 'foobar'@'localhost'IDENTIFIED by 'password'FAILED_LOGIN_ATTEMPTS 3PASSWORD_LOCK_TIME 2; Data And if you look at the mysql.user entry you will seeUser_attributes: {"Password_locking": {"failed_login_attempts": 3, "password_lock_time_days": 2}} Example $mysql -u foobar -p Enter password: ERROR 1045 (28000): Access denied for user 'foobar'@'localhost' (using password: YES) $ mysql ... Read More

Feed: Planet MySQL; Author: Mike Frank; For an encrypt only or decrypt/encrypt applications The following is an example of how to allow applications to asymmetrically encrypt data using a public key. In MySQL 8.0.19 support for the SECRET datatype was added to our Keyring technology. With this technology, users can securely manage their own keys using: Oasis KMIP protocol implementations: Other APIs for Key Management: Prerequisite MySQL Enterprise Edition 8.0.19 or higher select @@version; select @@version; Lets Get Going As administrator (Example running this as admin – root@localhost)If not installed – install MySQL Keyring To check – SELECT PLUGIN_NAME, PLUGIN_STATUS ... Read More

Feed: Planet MySQL; Author: The Pythian Group; While testing in an orchestrator lab I saw that none of my Orchestrator on-raft nodes were coming online after a reboot. This is the status report from SystemD. $ sudo systemctl status orchestrator * orchestrator.service - orchestrator: MySQL replication management and visualization Loaded: loaded (/etc/systemd/system/orchestrator.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2020-04-03 09:30:05 UTC; 30s ago Docs: https://github.com/github/orchestrator Main PID: 957 (code=exited, status=1/FAILURE) Apr 03 09:30:05 orchestrator-1 systemd[1]: Started orchestrator: MySQL replication management and visualization. Apr 03 09:30:05 orchestrator-1 orchestrator[957]: 2020-04-03 09:30:05 ERROR dial tcp 127.0.0.1:3306: connect: connection refused ... Read More