The below description was added to the MySQL Cluster 7.4 source
code
and describes how new nodes are added into the heartbeat protocol
at
startup of a node.
The protocol to include our node in the heartbeat protocol starts
when
we call execCM_INFOCONF. We start by opening communication to all
nodes
in the cluster. When we start this protocol we don't know
anything about
which nodes are up and running and we don't which node is
currently the
president of the heartbeat protocol.
For us to be successful with being included in the heartbeat
protocol we
need to be connected to all nodes currently in the heartbeat
protocol. It
is important to remember that QMGR (the source code module
that
controls the heartbeat handling) sees a node as alive if it is
included
in the heartbeat protocol. Higher level notions of aliveness is
handled
primarily by …
In the previous tutorial, we have learned about the basics of Vagrant. In this tutorial, we will move to next level and will learn more about Vagrant and setting up LAMP development environment in Vagrant. To start with, LAMP stands for: Linux (OS/Kernel), Apache (Web Server), MySQL (Database), PHP (Scripting Language). It is an open-source Web development environment which lets you create web applications. It is generally also referred as Web Stack.
Last week we announced our new query and metric listing and detail pages, which provide deep drilldown into individual queries and metrics for exploration and analysis. Today I want to show you one of the new features included in the Metric detail page. We have used it in a variety of scenarios for customers and for our internal analysis. We’ll cover some of the usage cases and success stories in future blog posts; here I’ll just give an overview of the capability.
To begin with, suppose you found a metric with an interesting shape and wanted to know something about it. This is very typical, by the way – you will see a bump or notch in a graph and wonder what it means, what else bumped or notched or behaved oddly around this time. Here’s our metric. In this case, CPU makes a good demo:
Look, ma! There’s a bump in …
[Read more]MariaDB 10.0.17 was recently released, and is available for download here:
https://downloads.mariadb.org/mariadb/10.0.17/
This is the eighth GA release of MariaDB 10.0, and 18th overall release of MariaDB 10.0.
For the most part, there are not a whole lot of new changes to report for this release, but there is a new version of the Audit Plugin and many other engines have been updated as well.
Here are the main items of note:
- The new version of the Audit Plugin is 1.2 is included with
the following new features:
- In the audit log passwords are now masked, i.e. the password characters are replaced with asterisks.
- It’s now possible to filter logging to include only DDL (CREATE, ALTER, etc.) or DML (INSERT, UPDATE, etc.) statements.
- For more information …
MariaDB 10.0.16 was recently released (~1.5 months ago on 1/27/2015 – sorry for the delay on my end – I was just extra busy in my spare time recently), and is available for download here:
https://downloads.mariadb.org/mariadb/10.0.16/
This is the seventh GA release of MariaDB 10.0, and 17th overall release of MariaDB 10.0.
For the most part, there are not a whole lot of changes to report for this release, but there are 2 enhancements of note – one being the JSON table type (still *experimental*) and the other a new variable to aid with index statistics calculations on large tables, as well as some security fixes.
Here are the main items of note:
- Updates to the CONNECT handler (supporting the …
When looking at Percona live Santa Clara 2015 agenda I saw two intriguing conferences : - JSON support in MySQL 5.7 – Docstore: document database for MySQL at Facebook
Both conference are talking about supporting a native JSON type in MySQL ! This sounds really great. I have never seen any blog post or github [...]
The MySQL Utilities Team is pleased to announce a new alpha
release of MySQL Utilities. This release includes a number of
improvements for useabilty, stability, and a few enhancements. A
complete list of all improvements can be found in our release notes.
New Enhancements!
This release represents a stable release of the product. Along
with several defect patches, we also include the following
enhancements.
Improved support for MySQL 5.7 early releases
Improved output for mysqldbcompare
Improved SSL support
New Utilities!
This release also has three new utilities for you to try
out:
mysqlslavetrx - skip transactions on one or more slaves to solve
errant transactions and consistency errors - …
The MySQL Utilities Team is pleased to announce the general
availability (GA) release of MySQL Utilities. This release
includes a number of improvements for useabilty, stability, and a
few enhancements. A complete list of all improvements can be
found in our release notes.
New Enhancements! This release represents a stable release
of the product. Along with several defect patches, we also
include the following enhancements.
- Improved support for MySQL 5.7 early releases
- Improved output for mysqldbcompare
- Improved SSL support
How Can I Download MySQL Utilities?
You can download MySQL Utilities 1.5.2 GA from the following link
using one of the pre-built installation repositories including a
source download.
…
In the MySQL team, we are planning to remove sql-bench from the MySQL 5.7 sources.
As the README file denotes, SQL Bench is a benchmark utility that supports MySQL 3.20 and 3.21, PostgreSQL 6.#, mSQL 2.# and Solid Server 2.2. It has not been well maintained for recent versions, and we are no longer using it internally as part of our testing process.
Our aim in making this change is to:
- Improve the manageability of our git repository by reducing its size.
- By keeping unmaintained code bundled with MySQL, it can lead users into negative impressions of our product. We have worked very hard at improving stability, and want to remove lurking pitfalls for our users.
The source code to sql-bench will remain in the …
[Read more]As the systemd integration keeps on getting forward. It is hardly to be ignored by us MySQL folks :)
Lets have a look into a simple problem, you are not going to solve like you used to solve it. (At least on Centos7 installing the MariaDB package)
Increasing table_open_cache
was only a configuration
issue. As mysqld
was started as root and then
switching to the unix user mysql
. On Centos7 this
was not working anymore. As MariaDB/MySQL ist startet with a
service file starting the process as user mysql:
[Service]
Type=simple
User=mysql
Group=mysql
..
As not root (having the right capability) it will be not able to change the open files limit. In the error log you are going to find something like:
150303 11:57:02 [Warning] Changed limits: max_open_files: 1024
max_connections: 214 table_cache: 400
Reading the …
[Read more]