Showing entries 61 to 70 of 852
« 10 Newer Entries | 10 Older Entries »
Displaying posts with tag: Replication (reset)
Fun with Bugs #40 - Bugs fixed in MySQL 5.7.10

MySQL 5.7.10, the first release after MySQL 5.7 GA announcement, appeared almost a week ago. It's interesting to check what bugs reported by MySQL Community were fixed in this version, hence this post (that had to wait during the weekdays busy with usual support work). As usual, I'll concentrate mostly on InnoDB, replication and optimizer-related bug fixes and highlight names of those who reported and verified each bug.

Let's start with InnoDB. The following bugs reported by MySQL Community users were fixed:

  • Bug #78623 - "Small tablespaces with BLOBs take up to 80 times more space in 5.7 than in 5.6". This serious regression was reported by my colleague Laurynas Biveinis and verified by Umesh well before 5.7.9 …
[Read more]
MySQL HA Solution … We have it or not ?

Data is the most important asset any organization has especially those who belongs to web, mobile, social, enterprise and cloud applications.

Availability refers to the ability to cope with, and if necessary recover from, failures on the host, including failures of MySQL, the operating system, or the hardware and maintenance activity that may otherwise cause downtime.

Because each application has different operational and availability requirements, MySQL offers a range of certified and supported solutions, delivering the appropriate levels of High Availability (HA). 

Factors to consider for HA Solution: 

  • Operational Capabilities
  • Budgetary Constraints
  • The level of availability required (In terms of Time)
  • The type of application being deployed
    • Mission critical services …
[Read more]
How Lost connection to MySQL and Slave I/O thread: Failed reading log event are related ?

I am a MySQL DBA role as usual check the problems and seek a solution.
On one of the production host (MySQL v5.1.53), I started getting errors in this series:

[Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'binlog.000942' at postion 45042
[ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)
[Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'binlog.000928' at postition
[ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)

Some expert says you should increase the slave_net_timeout and some says to check value of  relay_log_space_limit but it is default already

slave_net_timeout = 3600
relay_log_space_limit = 0 (unlimited) 
max_allowed_packet = 128MB

I can see no heavy …

[Read more]
Fixing inconsistency on MySQL Slave of Galera Cluster

This blog post explores the syncing options for an inconsistent MySQL slave of Galera cluster node using pt-table-sync

MySQL and Docker on a Mac: networking oddity

This is a quick post only indirectly related to the series of articles about Docker that I have written recently.

Yesterday I was giving a presentation about Docker in Buenos Aires, and as usual I included a long live demo. Almost all went as expected. There was one step that I tried some time ago, and had always worked well, but when I tried to repeat it on stage, it failed miserably:

  • Step 1: run the container
$ docker run  -d --name mybox -e MYSQL_ROOT_PASSWORD=secret mysql/mysql-server …
[Read more]
State of automated recovery via Pseudo-GTID & Orchestrator @ Booking.com

This post sums up some of my work on MySQL resilience and high availability at Booking.com by presenting the current state of automated master and intermediate master recoveries via Pseudo-GTID & Orchestrator.

Booking.com uses many different MySQL topologies, of varying vendors, configurations and workloads: Oracle MySQL, MariaDB, statement based replication, row based replication, hybrid, OLTP, OLAP, GTID (few), no GTID (most), Binlog Servers, filters, hybrid of all the above.

Topologies size varies from a single server to many-many-many. Our typical topology has a master in one datacenter, a bunch of slaves in same DC, a slave in another DC acting as an …

[Read more]
Orchestrator & Pseudo-GTID for binlog reader failover

One of our internal apps at Booking.com audits changes to our tables on various clusters. We used to use tungsten replicator, but have since migrated onto our own solution.

We have a binlog reader (uses open-replicator) running on a slave. It expects Row Based Replication, hence our slave runs with log-slave-updates, binlog-format='ROW', to translate from the master's Statement Based Replication. The binlog reader reads what it needs to read, audits what it needs to audit, and we're happy.

However what happens if that slave dies?

In such case we need to be able to point our binlog reader to another slave, and it needs to be able to pick up auditing from the same point.

This sounds an awful lot like slave repointing in case of master/intermediate master failure, and …

[Read more]
MySQL-Docker operations. - Part 3: MySQL replication in Docker


Previous Episodes:

MySQL-Docker operations. - Part 1: Getting started with MySQL in DockerMySQL-Docker operations. - Part 2: Customizing MySQL in Docker
With the material covered in the first two articles, we have all the elements needed to set up replication in Docker. We just need to put the pieces together.
If you want to do everything by hand, it will only take a few minutes. The steps are not complicated. If you have followed the reasoning in the past episodes, you will know what to do.
Or, you can make your life easier by using the ready-made scripts available in Github as MySQL …

[Read more]
MySQL Group Replication now on more platforms

A new version of the Group Replication plugin for MySQL is available now. The newest release is available on Mac OS X, Solaris, and FreeBSD.

Additional platform support has been made possible via a new group communication implementation. This new communication system supports communication of messages between servers on many platforms, allowing MySQL to embrace the diversity of the MySQL community and enables Group Replication for more people on more platforms.…

MySQL-Docker operations. - Part 2: Customizing MySQL in Docker


Previous Episodes:


After seeing the basics of deploying a MySQL server in Docker, in this article we will lay the foundations to customising a node and eventually using more than one server, so that we can cover replication in the next one.
Enabling GTID: the dangerous approach.To enable GTID, you need to set five variables in the database server:

  • master-info-repository=table
  • relay-log-info-repository=table
  • enforce-gtid-consistency
  • gtid_mode=ON
  • log-bin=mysql-bin

For MySQL 5.6, you also need to set log-slave-updates, but we won't deal with such ancient versions here.
Using the method …

[Read more]
Showing entries 61 to 70 of 852
« 10 Newer Entries | 10 Older Entries »