toggle quoted messageShow quoted text
Congratulations for this v26 release!
Do you have any documentation for the benefits and trade offs introduced by this new arbitrator, compared to the standard 3-nodes setup? What happens to the "quorum" principle in such arbitrator setup?
Are there any consequences or benefits in terms of managing possible sync failures and manual GTID re-sync?
And a last question : do you plan upgrading to MariaDB 10.1.x in future releases?
Le 25 févr. 2016 à 17:53, Mike Youngstrom <youngm(a)gmail.com> a écrit :
In our case we'll use the arbitrator because we only have 2 AZs in some datacenters. The Arbitrator allows us to place the 3rd member of the cluster in another datacenter minimal performance impact. Nice feature!
On Thu, Feb 25, 2016 at 9:49 AM, Duncan Winn <dwinn(a)pivotal.io> wrote:
+1.. The arbitrator is a fantastic feature. Great job MySQL team.
On Thu, 25 Feb 2016 at 00:39, James Bayer <jbayer(a)pivotal.io> wrote:--
congrats mysql team! the arbitrator is a nice touch to save resources yet still result in high availability even when losing an entire AZ.
On Wed, Feb 24, 2016 at 10:43 AM, Marco Nicosia <mnicosia(a)pivotal.io> wrote:
Hello Cloud Foundry folks,
For those of you who are tired of deploying web apps without easy integration with data services, cf-mysql is a great place to start. With this release, I'm happy to tell you that it takes even less commitment than ever to give cf-mysql a spin!
The theme for this release is the First Rule in Government Spending. Wanna take a ride?
A single MySQL node is a Single Point of Failure. With the introduction of the Arbitrator, we allow you to buy two at twice the price. Previously, we made you buy three for the same sense of security. Upgrading to cf-mysql v26 will save you money, with no sacrifice in performance!
If you like what we're doing with cf-mysql, click the thumbs up: 👍
If we're messing up your game, click the thumbs down: 👎
And if this just isn't your thing, at least give me a fist bump! 👊
- We've updated to MariaDB 10.0.23, enabled some important behind-the-scenes features, and fixed several important bugs.
- For those of you who require audit access to all data, we've given you the option to enable a Read Only admin user.
- We've introduced a new HA deployment option, 2+1: two MySQL nodes and an Arbitrator.
- And we've made significant updates to the generate-deployment-manifest script and stubs.
You'll have to update your stubs to use the new release, but we hope with the new Examples and Arbitrator feature, it'll be worth your time to upgrade. Make sure to read the release notes for important information about the upgrade process.
As always, for full disclosure, and links beyond that, please check out the Release Notes.
Introducing the Arbitrator
With cf-mysql v26, we've replaced one of the MySQL nodes with a lightweight Arbitrator node. Previously, the minimal HA configuration required three full-size MySQL nodes.
For cf-mysql administrators who are careful with their infrastructure resources, the Arbitrator feature is a new deployment topology that uses a smaller VM footprint while maintaining high availability guarantees. Unlike the old three node topology, the Arbitrator decreases spend with no impact on performance.
Thanks, and make sure to give me your feedback to influence what we do for future releases!
Pivotal Software, Inc.
Cloud Foundry PCF Services