Showing entries 8666 to 8675 of 44126
« 10 Newer Entries | 10 Older Entries »
MariaDB Galera Cluster 10.0.22 and Connector updates

The MariaDB project is pleased to announce the immediate availability of MariaDB Galera Cluster 10.0.22 and updates to MariaDB Connector/J, MariaDB Connector/C, and MariaDB Connector/ODBC. See the release notes and changelogs for details on each release. Download MariaDB Galera Cluster 10.0.22 Release Notes Changelog What is MariaDB Galera Cluster? MariaDB APT and YUM Repository Configuration […]

The post MariaDB Galera Cluster 10.0.22 and Connector updates appeared first on MariaDB.org.

Building MaxScale from source on CentOS 7

Thu, 2015-11-19 09:03markusmakela

We’ve gotten a few questions on detailed installation tutorials for specific systems. So I decided to write one for CentOS 7 which is a pretty common OS. For this I’m using a fresh installation of CentOS 7 on a virtual machine.

Installing needed packages

The first things we need to get are tools required for getting MaxScale and building it. The Development Tools group in Yum has most of the required tools we need to build MaxScale. We also need a few other packages to build MaxScale.

The list of required packages for each distribution can be found from the documentation: Building-MaxScale-from-Source-Code

Installing packages:

yum groupinstall "Development Tools"
yum install gcc gcc-c++ ncurses-devel …
[Read more]
InnoDB holepunch compression vs the filesystem in MariaDB 10.1

InnoDB holepunch experiments After excellent blogs by Mark Callaghan (see links below), I decided to use some of my time to experiment how different filesystems behave if the holepunch feature is used in MariaDB 10.1. First of all, MariaDB 10.1 does not use holepunch by default even if a table is page compressed (a term […]

The post InnoDB holepunch compression vs the filesystem in MariaDB 10.1 appeared first on MariaDB.org.

“About the unix philosophy, and why I broke it – and then how I moved back to the old track”

I am always fascinated by the cleanliness of UNIX. One tool only should do one thing, but it has to be the best in that way. The operating system itself will glue all the modules together and give you a complex feel of a system, you don’t have to take care of huge, bloated software, don’t have to deal with mysterious bugs, which are appearing random. Just small bricks of clever software and the rest are on you.

Recently I broke this, and frankly, I am not sure if it was a bad decision, or not.

With MySQL, if you want a point in time recovery after a disaster, you should back up not only the database but the binary logs themselves, as I have mentioned it in my last blog post. I added a feature to the binlogstreamer: it can clean up the binary logs after a given amount of time.

Let’s see how many ways we have to get rid of the old, unwanted …

[Read more]
Amazon EBS volume lazy loading: how it influences MySQL recovery performance

Amazon EBS volumes come with a very cool feature called "lazy loading". In a nutshell: if a volume is created from an existing snapshot, it can become available almost immediately without waiting for all data to be restored. This allows for extremely fast provisioning of large data sets as long as you don't explicitly require the entire data set to be present before you start using it.
When an EBS volume is restored from snapshot, its blocks are fetched from Amazon S3. It happens either lazily in the background or explicitly on demand (think of a pagefault-like mechanism) and of course, fetching pieces of data from Amazon S3 is going to be one-two orders of magnitude slower than reading blocks directly from a volume.
In this short article, I will try to give you an idea of how this may impact the crash recovery time of your MySQL databases. Why talk about this? Depending on the workload and data set layout, crash recovery of a MySQL …

[Read more]
Open-sourcing PinLater: An asynchronous job execution system

PinLater is an asynchronous job execution system we built as a replacement for our original solution based on Pyres. We’ve been using PinLater in production for over two years, and it’s one of our most mission critical systems. Usage of PinLater spans from core actions like Pinning, image thumbnail generation and when Pinners follow other Pinners, boards or topics, to larger batch operations like email delivery, push notifications and visual discovery workflows. We now operate more than 10 different clusters all on Amazon EC2. In aggregate, there are more than 500 job queues processing north of six million jobs per minute. Today we’re excited to announce PinLater as our latest …

[Read more]
About the unix philosophy, and why I broke it – and then how I moved back to the old track

I am always fascinated about the cleanliness  of UNIX . One tool only should do one thing, but it has to be the best in that way. The operating system itself will glue all the modules together and give you a complex feel of a system, you don’t have to take care of huge, bloated software, don’t […]

Become a ClusterControl DBA: Making your DB components HA via Load Balancers

Choosing your HA topology

There are various ways to retain high availability with databases. You can use Virtual IPs (VRRP) to manage host availability, you can use resource managers like Zookeeper and Etcd to (re)configure your applications or use load balancers/proxies to distribute the workload over all available hosts.

The Virtual IPs need either an application to manage them (MHA, Orchestrator), some scripting (KeepaliveD, Pacemaker/Corosync) or an engineer to manually fail over and the decision making in the process can become complex. The Virtual IP failover is a straightforward and simple process by removing the IP address from one host, assigning it to another and use arping to send a gratuitous ARP response. In theory a Virtual IP can be moved in a second but it will take a few seconds before the failover management application is sure the host has failed and acts accordingly. In reality this should be …

[Read more]
The client library, part 3: Building MySQL client applications

The client library — libmysqlclient — is part of the same source code repository as the server. It comes both as a dynamic link library (.so), also called a shared library, and as a static link library (.a). During the 5.7 development cycle, we’ve made several improvements to the library, which has resulted in a bump from ABI version 18 to version 20.…

December 9: INetU Webinar with Baron Schwartz - Best Practices for a High-Performing MySQL Database

On Wednesday, December 9 at 11 AM ET, please join us and INetU for a special webinar about Best Practices for a High-Performing MySQL Database with VividCortex & INetU.

Baron Schwartz (VividCortex founder and CEO), Michele Corvino (INetU Product Manager), and Jim DeHart (INetU Systems Engineer) will be discussing best practices for keeping MySQL databases at peak performance. INetU – the best customer-rated cloud hosting company in the industry – knows the importance of keeping databases running without hitch. Complexity within systems increases as applications grow, which means that as complications arise, there are more risks for end users. Leveraging a database performance tool like VividCortex allows users to take care of …

[Read more]
Showing entries 8666 to 8675 of 44126
« 10 Newer Entries | 10 Older Entries »