Showing entries 1 to 10 of 132
10 Older Entries »
Displaying posts with tag: Continuent Tungsten (reset)
The People and Values Behind Great Software-as-a-Service (SaaS)

Great SaaS – starts with great software. My company has been working on this mission since 2004.

It took a few years to get our solution right – to offer a geo-distributed MySQL database backend for billion-dollar businesses. And it took a few more years to polish it.

Today, we continue to improve it day-in, day-out.

But there is no doubt the patience and perseverance pays off:

While the number of Tungsten-clustered databases in-production is in the thousands, we average only one (1) new support request per day, and, because of this, we provide an average response time less than three (3) minutes.

Not enough is said about the people and values behind great software; so that’s what I want to talk about here. Continuent is an agile, globally-distributed, remote team that is much greater than the sum of its parts. Our software helps global enterprises …

[Read more]
New Webinar: Multi-Region AWS Aurora vs Continuent Tungsten for MySQL & MariaDB

We’re pleased to share our webinar “Multi-Region AWS Aurora vs Continuent Tungsten for MySQL & MariaDB”, recorded live on Thursday, April 18th, 2019.

Our colleague Matt Lang walks you through a comparison of building a global, multi-region MySQL / MariaDB / Percona cloud back-end using AWS Aurora versus Continuent Tungsten.

If you’d like to find out how multi-region AWS Aurora deployments can be improved – then this webinar is for you!

We hope you enjoy it!

 

Recorded:

Thursday, April 18th at 10am PST / 1pm EST / 4pm BST / 5pm CEST

 

Recording: follow this link to watch

 

Slides:

[Read more]
Webinar: Multimaster MySQL / MariaDB

In case you missed the Multimaster webinar recorded live on Thursday, March 28th, 2019:

Learn how NewVoiceMedia built a global, multi-region MySQL cloud back-end to support a high-volume cloud contact center. 

 

Agenda:

Find out how to deploy Multimaster MySQL / MariaDB / Percona with the following design criteria:

  • Geographically distributed, low-latency data
  • Fast local response times for read & write traffic
  • Full ACID compliance – atomic operations, guaranteed consistency, isolation, and durability
  • Local rapid-failover, automated high availability

 

Speaker:

Chris Parker

Director of Professional Services – EMEA/APAC, is based in the UK, and has over 20 …

[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]
Webinar: Geo-Scale MySQL & MariaDB in AWS

For those of you who missed the webinar, “Geo-Scale MySQL in AWS,” recorded live on Thursday, March 14th, 2019:

Learn how to build a global, multi-region MySQL / MariaDB / Percona cloud back-end capable of serving hundreds of millions of online multiplayer game accounts.

 

Agenda:

Find out how Riot Games serves a globally distributed audience with low-latency, fast response times for read traffic, rapid-failover automated high availability, simple administration, system visibility, and stability.

 

Speaker:

Eric M. Stone

COO at Continuent, is a veteran of fast-paced, large-scale enterprise environments with 35 years of Information Technology experience. With a focus on HA/DR, from building data centers and trading floors to world-wide deployments, Eric has …

[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]
Tungsten Clustering 6.0.4 and Tungsten Replicator 6.0.4 Released

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

Our v6.0.4 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:

  • When installing from an RPM, the installation would automatically restart the Connector during the installation. This behavior can now be controlled by setting the parameter --no-connectors within the configuration to prevent tpm from restarting the Connectors during the automated update processing.
  • Cross-site Replicators within a composite multimaster deployment can now be configured to point to slaves by default, and to prefer slaves over masters during operation using the new --policy-relay-from-slave=true option
  • You can now enable an option so …
[Read more]
Continuent Clustering 5.3.3/5.3.4 and Tungsten Replicator 5.3.3/5.3.4 Released

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

Release 5.3.4 was released shortly after 5.3.3 due to a specific bug in our reporting tool tpm diag. All of the major changes except this one fix are in the 5.3.3 release.

Our 5.3.3/4 release fixes a number of bugs and has been released to improve stability in certain parts of the products.

Highlights common to both products:

  • Fixed an issue with LOAD DATA INFILE
  • Replicator now outputs the filename of the file when using thl to show events
  • tpm diag has been improved the way we extract MySQL and support Net:SSH options

Highlights in the clustering product:

  • Tungsten Manager stability has been improved by identifying some memory leaks.
  • Tungsten Connector has fixed a number of bugs relating to bridge mode, …
[Read more]
Multi-Cloud SaaS Applications: Speed + Availability = Success!

In this blog post, we talk about how to run applications across multiple clouds (i.e. AWS, Google Cloud, Microsoft Azure) using Continuent Clustering. You want your business-critical applications to withstand node, datacenter, availability-zone or regional failures. For SaaS apps, you also want to bring data close to your application users for faster response times and a better user experience. With cross-cloud capability, Continuent also helps avoid lock-in to any particular cloud provider.

The key to success for the database layer is to be available and respond rapidly.

From both a business and operational perspective, spreading the application across cloud environments from different vendors provides significant protection against vendor-specific outages and vendor lock-in. Running on multiple platforms provides greater …

[Read more]
Mastering Continuent Clustering Series: Converting a standalone cluster to a Composite Primary/DR topology using INI configuration

In this blog post, we demonstrate how to convert a single standalone cluster into a Composite Primary/DR topology running in two data centers.

Our example starting cluster has 5 nodes (1 master and 4 slaves) and uses service name alpha. Our target cluster will have 6 nodes (3 per cluster) in 2 member clusters alpha_east and alpha_west in composite service alpha.

This means that we will reuse the existing service name alpha as the name of the new composite service, and create two new service names, one for each cluster (alpha_east and alpha_west).

Below is an INI file extract example for our starting standalone cluster with 5 nodes:

[defaults]
...

[alpha]
connectors=db1,db2,db3,db4,db5
master=db1
members=db1,db2,db3,db4,db5
topology=clustered

To convert the above configuration to a Composite Primary/DR:

  1. First you must stop all services on all existing nodes:
    shell> stopall …
[Read more]
Showing entries 1 to 10 of 132
10 Older Entries »