I’m learning so much each week from just running the OpenLampTech developer newsletter to reading the great content shared within. There is always something to learn and I am thankful for your reading each week.

Custom WooCommerce and Shopify Solutions

Discover useful WooCommerce and Shopify custom solutions for your online store today at affordable prices!

Learn More

If you are not yet subscribed, head on over and grab a free subscription and get the weekly OpenLampTech publication delivered straight to your inbox.

In OpenLampTech issue #75, we are looking at …

Introducing schemadiff, an internal library in Vitess that has been one of its best-kept secrets until now. At its core, schemadiff is a declarative, programmatic library that can produce a diff in SQL format of two entities: tables, views, or full blown database schemas. But it then goes beyond that to normalize, validate, export, and even apply schema changes, all declaratively and without having to use a MySQL server. Let's dive in to understand its functionality and capabilities.

In this article, we will discuss errant Transaction /GTID and how we can solve them with the Orchestrator tool.

Orchestrator is a MySQL high availability and replication management tool that runs as a service and provides command line access, HTTP API, and Web interface. I will not go into the details of the Orchestrator but will explore one of the features that can help us solve the errant GTID in a replication topology.

What are errant transactions?

Simply stated, they are transactions executed directly on a replica. Thus they only exist on a specific replica. This could result from a mistake (the application wrote to a replica instead of writing to the source) or by design (you need additional tables for reports).

What problem can errant transactions cause?

The major problem it causes during a planned change in a MySQL replication topology is that the transaction is not present in the binlog and hence …

The latest MySQL release has been published on April 18th, 2023 (my eldest daughter’s birthday).This new version of MySQL brings a new service that I’m excited to play with: Performance Schema Server Telemetry Traces Service. MySQL 8.0.33 contains bug fixes and contributions from our great MySQL community.

I would like to thank all contributors on behalf of the entire Oracle MySQL team !

MySQL 8.0.33 contains patches from Mikael Ronström, Evgeniy Patlan, Dmitry Lenev, HC Duan, Marcelo Altmann, Facebook, Nico Pay, Dan McCombs, Yewei Xu, Niklas Keller, Mayank Mohindra and Alex Xing.

Let’s have a look at all these contributions:

MySQL NDB Cluster

• #103814 – ClusterJ partition key scratch buffer size too small – …

The latest MySQL release has been published on April 18th, 2023. This new version of MySQL brings a new service that I’m excited to play with: Performance Schema Server Telemetry Traces Service. MySQL 8.0.33 contains bug fixes and contributions from our great MySQL community. I would like to thank all contributors on behalf of the […]

As we approach end of life for MySQL 5.7 later this year, many businesses are currently working towards upgrading to MySQL 8. Such major version upgrades are rarely simple, but thankfully there are tools that can help smooth the process and ensure a successful upgrade.

It should be noted that while the technical aspects of the upgrade process are beyond the scope of this blog post, it is crucial to create a testing environment to verify the upgrade before proceeding to upgrade your production servers, particularly with MySQL 8. 

As there is no procedure for downgrading from MySQL 8 other than restoring a backup, testing and validation are more critical than previous major version …

The KubeCon around the Kubernetes technology was one of the events I dreamed to attend since I’m focusing on the CloudNative solutions. I had the great opportunity to attend the KubeCon & CloundNativeCon in Amsterdam with my colleague Benoît Entzmann.

There is now CNCF-hosted Co-located events adding more topics and interesting sessions. This is community-driven, vendor-neutral events hosted and managed by the CNCF. ArgoCD, Cilium, Linkerd have now their own conference. Here is the list of CNCF-hosted Co-located events.

Unfortunately, all the above events were already sold out when we decided to come at the KubeCon.

During the 1st day Keynote, Chris Aniszczyk CTO of the CNCF mentioned that for this year, the increase of the number of participants was just amazing reaching more than 10’000 people. The number of CNCF projects also increased a lot. I feel that the main message of this Keynote is that …

MySQL released version 8.0.33 on April 18th, featuring some attention-catching features.  This blog post is a quick review of the release notes looking for the exciting items, and comments in italics are solely my own.

User-defined collations are now deprecated and will be removed in a future version.  This is probably not a show-stopper for most and probably a scary situation for those dependent on them as there may not be an alternative.  Hopefully, UTF8MB4 is good enough.

The Performance Shema now has a Server Telemetry Traces service. This interface provides plugins and components a way to retrieve notifications related to SQL statements’ lifetime. We are directed to the Server telemetry traces service section in the MySQL Source Code documentation

The SSL library has been updated to OpenSSL version …

“The customer is always right” – that’s a saying that serious businesses actually say sometimes, with a serious and straight face. It’s one of those sayings rooted in good intentions and immediately polluted with the messy reality of the real world.

When you’re working in Database or even Network Engineering, the real answer is far more complicated and nuanced, but it’s much closer to “the customer is always wrong”. That is not to say that the Database or Network Engineer is right, either, though.

Usually the customer (in this case usually a Software Engineer) comes to us, or more likely pages us, with something like “the database is down”. Why? Because they got an error message like “The server has gone away” or “Too many connections” or “Host unreachable” or any number of error messages which are simultaneously too descriptive, and completely unhelpful. Such error messages are good at leading people …

MySQL Shell 8.0.33 was released last week. Apart from several bugfixes, there are some new, important, and long-desired features related to security, concurrency control, and performance settings. Passwordless authentication (certificate-based authentication) The AdminAPI enables an easy set-up and maintenance of MySQL deployments, either for High Availability or Disaster Recovery. Security is crucial and InnoDB Cluster has support for […]