Showing entries 1 to 10 of 12
2 Older Entries »
Displaying posts with tag: Tungsten Clustering (reset)
How to Deal with Triggers in Your MySQL Database When Using Tungsten Replicator

Overview

Over the past few days we have been working with a number of customers on the best way to handle Triggers within their MySQL environment when combined with Tungsten Replicator. We looked at situations where Tungsten Replicator was either part of a Tungsten Clustering installation or a standalone replication pipeline.

This blog dives head first into the minefield of Triggers and Replication.

Summary and Recommendations

The conclusion was that there is no easy one-answer-fits-all solution – It really depends on the complexity of your environment and the amount of flexibility you have in being able to adjust. Our top level summary and recommendations are as follows:

If using Tungsten Clustering and you need to use Triggers:

  • Switch to …
[Read more]
Geo-Scale MySQL for Continuous Global Operations & Fast Response Times

Geo-scale MySQL – or how to build a global, multi-region MySQL cloud back-end capable of serving several hundred million player accounts

This blog introduces a series of blogs we’ll be publishing over the next few months that discuss a number of different customer use cases that our solutions support and that centre around achieving continuous MySQL operations with commercial-grade high availability (HA), geographically redundant disaster recovery (DR) and global scaling.

This first use case looks at a customer of ours who are a global gaming company with several hundred million world-wide player accounts.

What is the challenge?

How to reliably, and fast, cater to hundreds of millions of game players around the world? The challenge here is to serve a game application for a geographically-distributed audience; in other words, a pretty unique challenge.

It requires fast, local response times …

[Read more]
The Slow Software Movement

Those who build SaaS know that you’re actually providing an experience. You’re building long-term relationships and aiming for recurring revenue. Therefore, your product must be flexible, resilient, and consistent.

Many companies find it hard to take time, acquire the right ingredients, and design truly great software from the bottom-up. This is understandable given how fast the SaaS industry moves.

But firstly, who am I to be talking about this subject? My education was in Economics and Complex Systems, and I’ve been fortunate to gain exposure to various IT trends and tools working almost a decade mostly in Tech. I started interviewing customers at Continuent (majority SaaS) over five years ago, and I have listened to a number of …

[Read more]
Read the White Paper: Tungsten Clustering for MySQL, MariaDB & Percona Server Databases

We’re happy to announce that our white paper ‘Tungsten Clustering – Benefits & Configurations’ for MySQL, MariaDB and Percona Server is available to read on our website.

Tungsten Clustering is a one-of-a-kind software solution that provides clustering, disaster recovery and high availability for MySQL, MariaDB & Percona Server databases.

It allows enterprises running business-critical database applications to cost-effectively achieve continuous operations on a global scale with:

  • Commercial-grade high availability (HA)
  • Geographically redundant disaster recovery (DR)
  • Global operations with geographically distributed multi-master

[Read more]
Tungsten Clustering 5.4.0 and Tungsten Replicator 5.4.0 Released

Continuent is pleased to announce that the following new software releases are now available:

  • Tungsten Clustering version 5.4.0
  • Tungsten Replicator version 5.4.0

Releases 5.4.0 is significant in that it introduces MySQL 8 support, along with many new features, stability improvements and bug fixes.

Highlights common to both products:

Improvements, new features and functionality

  • Two new utility scripts have been added to the release to help with setting the Replicator position:
    • tungsten_find_position, which assists with locating information in the THL based on the provided MySQL binary log event position and outputs a dsctl set
[Read more]
Tungsten Clustering 6.1.0 and Tungsten Replicator 6.1.0 Released

Continuent is pleased to announce that the following new software releases are now available:

  • Tungsten Clustering version 6.1.0
  • Tungsten Replicator version 6.1.0

Release 6.1.0 is significant in that it introduces MySQL 8 support, along with many new features, stability improvements and bug fixes.

Highlights common to both products:

Improvements, new features and functionality

  • Two new utility scripts have been added to the release to help with setting the Replicator position:
    • tungsten_find_position, which assists with locating information in the THL based on the provided MySQL binary log event position and outputs a dsctl set command …
[Read more]
Your Data On The World Wide Web… Forever!

If you share your photos on social media, they will stay on the internet forever…

Many of us have heard or read this sentence during conversations with friends, in articles, online forums, TV shows, etc.

But how is it possible that we can’t seem to be able to fully remove our photos from the internet when we want to, and, taking this further, that our photos are never lost and always retrievable (which can both be a good and a bad thing)?

The behind-the-scenes, technical secret lies in data replication.

The very first moment when you share a photo on social media, that photo is uploaded into the closest available database server. In the second moment, that same photo is replicated into multiple other servers around the world.

This is what data …

[Read more]
Troubleshooting Data Differences in a MySQL Database Cluster

Overview The Skinny

From time to time we are asked how to check whether or not there are data discrepancies between Master/Slave nodes within a MySQL (or MariaDB) cluster that’s managed with Tungsten Clustering. This is always a challenging task, not least because we hope and believe that our replication mechanism would avoid such occurrences, that said there can be factors outside of our control that can appear to “corrupt” data – such as inadvertent execution of DML against a slave using a root level user account.

Tungsten Replicator, the core replication component in our Tungsten Clustering solution for MySQL (& MariaDB), is just that, a replicator – it takes transactions from the binary logs and replicates them around. The replicator isn’t a data synchronisation tool in that respect, the …

[Read more]
Tungsten Clustering 6.0.5 and Tungsten Replicator 6.0.5 Released

Continuent is pleased to announce that Tungsten Clustering 6.0.5 and Tungsten Replicator 6.0.5 are now available!

Our v6.0.5 release fixes a number of bugs and introduces some new features, with improvements across the board in a variety of different components.

Some of the key improvements include:

  • A new Clustering utility script has been added to the release, tungsten_reset_manager, which assists with the graceful reset of the manager’s dynamic state files on disk.
  • Fixed an issue where the tpm command would allocate inconsistent THL listener ports for the Composite Multimaster (CMM) topology.
  • MySQL ping commands are now reconnected/retried upon “server gone away” error (Proxy mode ONLY).
  • mysql_checker_query script was returning …
[Read more]
Tungsten Clustering 5.3.6 and Tungsten Replicator 5.3.6 Released

Continuent is pleased to announce that Tungsten Clustering 5.3.6 and Tungsten Replicator 5.3.6 are now available!

Our 5.3.6 release fixes a number of bugs and has been released to improve stability.

Highlights common to both products:

  • Now, instead of searching for a master with appropriate role (i.e. matching the slave preferred role) until timeout is reached, the replicator will loop twice before accepting connection to any host no matter what its role is. (CT-712)
  • Changing the state machine so that RESTORING is not a substate of OFFLINE:NORMAL, but instead of OFFLINE so that a transition from OFFLINE:NORMAL:RESTORING to ONLINE is not possible any longer. Now it will not be possible to transition from
    OFFLINE:RESTORING to ONLINE (CT-797)
  • When an heartbeat is inserted, it will now use the JVM timezone instead of hardcoded UTC. (CT-803)
  • Now skipping files that are not …
[Read more]
Showing entries 1 to 10 of 12
2 Older Entries »