This is a quick setup guide of 10-steps to install and configure (multiple) MySQL instance on 3307 port, and make it slave from MySQL running on port 3306.
The post Setting-up second MySQL instance & replication on Linux in 10 steps first appeared on Change Is Inevitable.
I reckon there’s little sense in running 2 or more Percona XtraDB Cluster (PXC) nodes in a single physical server other than for educational and testing purposes – but doing so is still useful in those cases. The most popular way of achieving this seems to be with server virtualization, such as making use of Vagrant boxes. But in the same way you can have multiple instances of MySQL running in parallel on the OS level in the form of concurrent mysqld processes, so too can you have multiple Percona XtraDB Cluster nodes. And the way to achieve this is precisely the same: using dedicated datadirs and different ports for each node.
Which ports?4 tcp ports are used by Pecona …
[Read more]The need to have multiple instances of MySQL (the well-known mysqld process) running in the same server concurrently in a transparent way, instead of having them executed in separate containers/virtual machines, is not very common. Yet from time to time the Percona Support team receives a request from a customer to assist in the configuration of such an environment. MySQL provides a tool to facilitate the execution of multiple instances called mysqld_multi:
“mysqld_multi is designed to manage several mysqld processes that listen for connections on different Unix socket files and TCP/IP ports. It can start or stop servers, or report their current status.”
For tests and development purposes, …
[Read more]The need to have multiple instances of MySQL (the well-known mysqld process) running in the same server concurrently in a transparent way, instead of having them executed in separate containers/virtual machines, is not very common. Yet from time to time the Percona Support team receives a request from a customer to assist in the configuration of such an environment. MySQL provides a tool to facilitate the execution of multiple instances called mysqld_multi:
“mysqld_multi is designed to manage several mysqld processes that listen for connections on different Unix socket files and TCP/IP ports. It can start or stop servers, or report their current status.”
For tests and development purposes, …
[Read more]A customer called with an emergency issue: A server that normally runs many MySQL instances wouldn’t start them up. Not only would it not start all of them, it wouldn’t even start the first one. The multiple instances were started through the mysql_multi init script. Perhaps you already know what was wrong!
It turns out that this server’s /etc/init.d/mysql_multi wouldn’t start unless it found the text “mysqld_multi” in the /etc/my.cnf file. Not a [mysqld_multi] config file section, but the text string “mysqld_multi”. It was using this text as a proxy for “I found a [mysqld_multi] configuration section.” This was a rather brittle test, as you can imagine.
After reading the source, I determined that the my.cnf file was fine and the configuration should not be changed, and I could not understand what had changed since it was previously working. Perhaps an automated upgrade or a similar change to the system had …
[Read more]
Please do not assume Perl is always installed on all platforms.
In particular not on Windows! Just as it is probably a bad idea
to assume that Windows DOS commands work on Linux! Come on
now!
Why am I making a fuzz you ask, do I have a problem with you
writing stuff in Perl (personally, I don't even like Perl, but
that's another issue)? Nope. But somewhat modern software really
should not assume that you have Perl, or DOS, or some other
arcane, not terribly standardized piece of software around for a
server to do it's job. And MySQL still have a way to go to be
reasonably good on Windows. Downloading the lastest RC, 5.5.7,
MySQLhas managed to screw up at least two things, at least, in my
mind. But maybe that's just me: