Home News Feeds Planet MySQL
Newsfeeds
Planet MySQL
Planet MySQL - https://planet.mysql.com

  • Percona Live 2018: Securing Access to Facebook’s Databases
    We’re moving along at Percona Live 2018, and there are still packed and energetic talks after lunch. My next session was with Andrew Regner, Production Engineer at Facebook. His talk was on securing access to Facebook’s databases. Since the beginning, Facebook has used a conventional username/password to secure access to production MySQL instances. Over the last few years, they’ve been working on moving to x509 TLS client certificate authenticated connections. Given the many types of languages and systems at Facebook that use MySQL in some way, this required a massive amount of changes for a lot of teams. This talk is both a technical overview of how their new solution works and hard-learned tricks for getting an entire company to change their underlying MySQL client libraries. After his talk, I had a chance to quickly talk with Andrew about his efforts to move the security process for Facebook’s databases. Check it out below. The post Percona Live 2018: Securing Access to Facebook’s Databases appeared first on Percona Database Performance Blog.

  • Percona Live 2018: Migrating to Vitess at (Slack) Scale
    Percona Live 2018 is moving along, and the first person I got a chance to talk with is Michael Demmer, Senior Staff Engineer at Slack. His talk was on Migrating to Vitess at (Slack Scale). MySQL is the backbone of Slack’s data storage infrastructure. It handles billions of queries per day across thousands of sharded database hosts. Slack is migrating this system to use Vitess’ flexible sharding and topology management instead of simple application-based shard routing and manual administration. This effort aims to provide an architecture that scales to meet the growing demands of our largest customers and features while under pressure to maintain a stable and performant service. This talk presented the core motivations behind our decision, why Vitess won out as the best option, and how Slack laid the groundwork for the migration within our development teams. Michael then presented some challenges and surprises (both good and bad) found during their transition, and the contributions to the Vitess project that mitigated them. Finally, he discussed the future plans for their migration, and suggested improvements to the Vitess ecosystem to aid other adoption efforts. I spoke briefly with Michael after his talk, check it out below: The post Percona Live 2018: Migrating to Vitess at (Slack) Scale appeared first on Percona Database Performance Blog.

  • Reading the log positions of a snapshot consistently
    MySQL 8.0.11 introduced a new performance schema table named log_status, which provides consistent information about MySQL server instance log positions from replication and transactional storage engines. Used in conjunction with other MySQL 8.0 feature (the backup lock), this new feature will allow backup tools to take backup with minimal impact in DML throughput, but ensuring consistent snapshot with respect to GTIDs, replication, binary logs and transactional storage engine logs.…

  • Try MariaDB Server 10.3 in Docker
    Try MariaDB Server 10.3 in Docker rasmusjohansson Wed, 04/25/2018 - 13:07 There are times when you may want to test specific software or a specific version of software. In my case, I wanted to play with MariaDB Server 10.3.6 Release Candidate and some of the new, upcoming features. I didn’t want to have a permanent installation of it on my laptop so I chose to put it in a Docker container that I can easily copy to another place or remove. These are the steps I had to take to get it done. I won’t go through how to install Docker itself. There is good documentation for it, which can be found here: https://docs.docker.com/install/ After the installation is completed, make sure Docker is up and running by opening a terminal and typing in a terminal window: docker info There are a lot of other alternatives to see that Docker is up and running, but “info” provides useful information about your Docker environment. After Docker is set up, it’s time to create a container running MariaDB Server. The easy way to do it is to use the MariaDB Dockerfiles available on Docker Hub. These images are updated fairly quickly when a new release is made of MariaDB. It’s this easy to get MariaDB Server 10.3 RC up and running by using the Dockerfile: docker pull mariadb:10.3 docker run --name mariadbtest -e MYSQL_ROOT_PASSWORD=mypass -d mariadb:10.3 Check that MariaDB started correctly by looking at the logs: docker logs mariadbtest The last row in the log will also tell you what version of MariaDB is running. For documentation on this, refer to Installing and using MariaDB via Docker in the MariaDB documentation. In my case, I wanted to test out the latest version of MariaDB that wasn’t yet at the time of writing available in the Dockerfile on Docker Hub. I will next go through the steps to create and populate a container without using a Dockerfile. To get going we’ll need a new container. We need the container to be based on a operating system that is supported for MariaDB. I’ll base it off Ubuntu Xenial (16.04). docker run -i -t ubuntu:xenial /bin/bash When running that command, Docker will download the Ubuntu Xenial Docker image and use it as the base for the container. The /bin/bash at the end will take us into the shell of the container. Inside the container I want to install MariaDB 10.3. I used the repository configuration tool for MariaDB to get the right configuration to add to the clean Xenial installation I now have. The tool gave me the following three commands to run. add-apt-repository 'deb [arch=amd64,i386,ppc64el] http://mirror.netinch.com/pub/mariadb/repo/10.3/ubuntu xenial main' apt update apt install mariadb-server The last command will start installing MariaDB, which will ask for a root password for MariaDB to be defined. Once that is done and the installation finishes we can exit from the container and save the configuration that we’ve done. The container id, which is needed as an argument for the commit command is easily fetched from the shell prompt , root@[container id]. exit docker commit [container id] rasmus/mariadb103 It’s pretty useful to be able to have the database data stored outside the container. This is easily done by first defining a place for the data on the host machine. In my case, I chose to put it in /dbdata in my home directory. We want to expose it as the /data directory inside the container. We start the container with this command. docker run -v="$HOME/dbdata":"/data" -i -t -p 3306 rasmus/mariadb103 /bin/bash Inside the container, let’s start the MariaDB server and run the normal installation and configuration scripts. /usr/bin/mysqld_safe & mysql_install_db mysql_secure_installation After this we can test connecting to MariaDB 10.3 and hopefully everything works. mysql -p Welcome to the MariaDB monitor.  Commands end with ; or \g. Your MariaDB connection id is 16 Server version: 10.3.6-MariaDB-1:10.3.6+maria~xenial-log mariadb.org binary distribution Now I want to save the configuration so far to easily be able to start from state whenever needed. First, I exit the MariaDB monitor and then shutdown MariaDB. exit mysqladmin -p shutdown Then another exit will get us out of the container and then we can save the new version of the container by running the below docker commit command in the host terminal. Again, take the container id from the shell prompt of the container. exit docker commit -m "mariadb 10.3.6" -author="Rasmus" [container id] rasmus/mariadb103:"basic configuration" Tadaa, done! MariaDB 10.3.6 is now available in a Docker container and I can start playing with the cool new features of MariaDB Server 10.3 like System Versioned Tables. To start the container, I just run: docker run -v="$HOME/dbdata":"/data" -i -t -p 3306 rasmus/mariadb103:”basic configuration” /bin/bash   How to MariaDB Releases There are times when you may want to test specific software or a specific version of software. In my case, I wanted to play with MariaDB Server 10.3.6 Release Candidate and some of the new, upcoming features. I didn’t want to have a permanent installation of it on my laptop so I chose to put it in a Docker container that I can easily copy to another place or remove. These are the steps I had to take to get it done. Login or Register to post comments

  • a critical piece is missing for Oracle MySQL 8 (GA) …
    Oracle MySQL 8.0 has been declared GA but a critical piece is missing … MySQL 8 is a fantastic release embedding the work of brilliant Oracle engineering. I will not detail all the great features of MySQL 8 as there are a lot of great presentations around it. https://mysqlserverteam.com/whats-new-in-mysql-8-0-generally-available/ One of my main concern regarding [...]

Banner
Copyright © 2018 andhrabay.com. All Rights Reserved.
Joomla! is Free Software released under the GNU/GPL License.