This document provides an overview and comparison of MySQL InnoDB Cluster and MySQL InnoDB ReplicaSet. It discusses the components, goals, and features of each solution. MySQL InnoDB Cluster uses Group Replication to provide high availability, automatic failover, and data consistency. MySQL InnoDB ReplicaSet uses asynchronous replication and provides availability and read scaling through manual primary/secondary configuration and failover. Both solutions integrate MySQL Shell, Router, and automatic member provisioning for easy management.
24시간 365일 서비스를 위한 MySQL DB 이중화.
MySQL 이중화 방안들에 대해 알아보고 운영하면서 겪은 고민들을 이야기해 봅니다.
목차
1. DB 이중화 필요성
2. 이중화 방안
- HW 이중화
- MySQL Replication 이중화
3. 이중화 운영 장애
4. DNS와 VIP
5. MySQL 이중화 솔루션 비교
대상
- MySQL을 서비스하고 있는 인프라 담당자
- MySQL 이중화에 관심 있는 개발자
MySQL InnoDB Cluster - A complete High Availability solution for MySQLOlivier DASINI
MySQL InnoDB Cluster provides a complete high availability solution for MySQL. It uses MySQL Group Replication, which allows for multiple read-write replicas of a database to exist with synchronous replication. MySQL InnoDB Cluster also includes MySQL Shell for setup, management and orchestration of the cluster, and MySQL Router for intelligent connection routing. It allows databases to scale out writes across replicas in a fault-tolerant and self-healing manner.
MySQL InnoDB Cluster: High Availability Made Easy!Vittorio Cioe
InnoDB Cluster represents the present and the future of High-Availability technologies for MySQL! It has been developed to remove from the discussion all the "BUT" which used to arised when we were speaking about high-availability with MySQL. Now, with quasi-automated deployment, fully automated failover and conflict resolution, designing, implementing and maintaing your highly-available MySQL infrastructure is a really no-stress operation!
MySQL Parallel Replication: All the 5.7 and 8.0 Details (LOGICAL_CLOCK)Jean-François Gagné
To get better replication speed and less lag, MySQL implements parallel replication in the same schema, also known as LOGICAL_CLOCK. But fully benefiting from this feature is not as simple as just enabling it.
In this talk, I explain in detail how this feature works. I also cover how to optimize parallel replication and the improvements made in MySQL 8.0 and back-ported in 5.7 (Write Sets), greatly improving the potential for parallel execution on replicas (but needing RBR).
Come to this talk to get all the details about MySQL 5.7 and 8.0 Parallel Replication.
The document discusses MySQL Group Replication, which is a plugin that provides multi-master replication capability for MySQL. It allows data to be replicated between multiple MySQL servers so that they can stay in sync. The replication works by having each server send transaction writesets to other servers through a group communication system, and then each server certifies and applies the changes locally in an asynchronous manner.
Slides for the webinar held on January 21st 2014
Repair & Recovery for your MySQL, MariaDB & MongoDB / TokuMX Clusters
Galera Cluster, NDB Cluster, VIP with HAProxy and Keepalived, MongoDB Sharded Cluster, etc. all have their own availability models. We are aware of these availability models and will demonstrate in this webinar how to take corrective action in case of failures via our cluster management tool, ClusterControl.
In this webinar, Severalnines CTO Johan Andersson will show you how to leverage ClusterControl to detect failures in your database cluster and automatically repair them to maximize the availability of your database services. And Codership CEO Seppo Jaakola will be joining Johan to provide a deep-dive into Galera recovery internals.
Agenda:
Redundancy models for Galera, NDB and MongoDB/TokuMX
Failover & Recovery (Automatic vs Manual)
Zooming into Galera recovery procedures
Split brains in multi-datacenter setups
ProxySQL High Avalability and Configuration Management OverviewRené Cannaò
The document provides an overview of high availability and configuration management options for ProxySQL. It discusses deploying ProxySQL locally on application servers, in a dedicated layer, or using both approaches. When deploying in a dedicated layer, options for high availability include keepalived, load balancers, Consul, and Kubernetes. Configuration can be managed through tools like Ansible, Puppet, or by loading SQL files. ProxySQL Cluster enables syncing configuration across nodes.
This is the presentation delivered by Karthik.P.R at MySQL User Camp Bangalore on 09th June 2017. ProxySQL is a high performance MySQL Load Balancer Designed to scale database servers.
MySQL InnoDB Cluster provides a complete, high-availability solution for MySQL. Learn how with a few easy-to-use Shell commands, how to set up a MySQL database architecture.
MariaDB MaxScale is a database proxy that provides scalability, high availability, and data streaming capabilities for MariaDB and MySQL databases. It acts as a load balancer and router to distribute queries across database servers. MaxScale supports services like read/write splitting, query caching, and security features like selective data masking. It can monitor replication lag and route queries accordingly. MaxScale uses a plugin architecture and its core remains stateless to provide flexibility and high performance.
MySQL 8.0 is the latest Generally Available version of MySQL. This session will help you upgrade from older versions, understand what utilities are available to make the process smoother and also understand what you need to bear in mind with the new version and considerations for possible behavior changes and solutions.
Replication Troubleshooting in Classic VS GTIDMydbops
This presentation talk will assist you in troubleshooting MySQL replication for the most common issues we might face with a simple comparison of how can we get them solved in the different replication methods (Classic VS GTID).
MySQL InnoDB Cluster HA Overview & DemoKeith Hollman
Take a look at the High Availability option that you can use with your out-of-the-box MySQL: MySQL InnoDB Cluster. With MySQL Server 8.0, MySQL Shell & MySQL Router you can convert from single-primary to multi-primary and back again, in a single command. Want to know how?
This document provides an overview of new features and enhancements in MySQL 8.0 over the last 18 months, from versions 8.0.23 to 8.0.30. It discusses improvements to replication, Group Replication, InnoDB, and primary keys. Some key changes include a new InnoDB redo log architecture, support for disabling the redo log at runtime, parallel index builds, and the ability to add an invisible auto-increment primary key column to tables without a primary key. The document is presented by Frédéric Descamps at the MySQL User Group NL.
Since the introduction of replication in MySQL, users have been trying to automate the promotion of a replica to a primary as well as automating the failover of TCP connections from one database server to another in the event of a database failure: planned or unplanned. For over a decade, users and organizations have designed various types of solutions to achieve this. Though, many of these solutions were done manually or were using third party software, mostly open source, to automate and integrate various architectures.
For more than 5 years now, MySQL offers complete and very easy-to-use solutions to set up database architectures that provide High-Availability and recently added Disaster Recovery capabilities. Completely built in-house and supported by Oracle, many enterprises large and small have adopted these solutions into business-critical applications.
Business requirements dictate what type of database architecture is required for your system. Disaster tolerance is key and can be measured at different levels: data loss, data availability, and uptime. In this session, the various MySQL Database Architecture solutions will be covered to help you choose the right solution based on your business requirements
MySQL InnoDB Cluster - Advanced Configuration & OperationsFrederic Descamps
The document discusses various methods for provisioning and monitoring new members joining a MySQL InnoDB cluster. It describes the incremental recovery and clone-based provisioning processes. It provides guidance on forcing the use of clone over incremental recovery for both provisioning and recovery scenarios. The document also discusses using MySQL Shell commands and Performance Schema tables to monitor the provisioning and recovery processes, as well as the overall health and performance of the cluster.
In this tutorial, we cover the different deployment possibilities of the MySQL architecture depending on the business requirements for the data. We also deploy some architecture and see how to evolve to the next one.
The tutorial covers the new MySQL Solutions like InnoDB ReplicaSet, InnoDB Cluster, and InnoDB ClusterSet.
The document discusses two MySQL high availability solutions: MySQL InnoDB Cluster and MySQL NDB Cluster. MySQL InnoDB Cluster provides easy high availability built into MySQL with write consistency, read scalability, and application failover using MySQL Router. MySQL NDB Cluster is an in-memory database that provides automatic sharding, native access via several APIs, read/write consistency, and read/write scalability using the NDB storage engine. The document compares the two solutions and discusses their architectures and key features.
MySQL InnoDB Cluster / ReplicaSet - TutorialMiguel Araújo
Tutorial given at pre-FOSDEM MySQL Days 2020 on MySQL InnoDB Cluster and ReplicaSet, a fully integrated product built on MySQL technology, by MySQL.
MySQL InnoDB Cluster and ReplicaSet provide failover/high availability and scaling features baked in; providing an integrated end-to-end solution that is easy to use.
MySQL InnoDB Cluster / ReplicaSet - TutorialKenny Gryp
Tutorial on MySQL InnoDB Cluster and ReplicaSet, a fully integrated product built on MySQL technology, by MySQL.
MySQL InnoDB Cluster and ReplicaSet provide failover/high availability and scaling features baked in; providing an integrated end-to-end solution that is easy to use.
The document discusses MySQL high availability options including:
1) Asynchronous and semi-synchronous replication for high availability deployments.
2) MySQL InnoDB Cluster which uses Group Replication, MySQL Router, and MySQL Shell to provide an integrated high availability solution.
3) Examples of deploying MySQL InnoDB Cluster in single and multi-data center configurations for high availability and disaster recovery.
The document introduces the MySQL Operator for Kubernetes, which automates the deployment and management of MySQL databases on Kubernetes. It leverages MySQL InnoDB Cluster to deploy high availability MySQL clusters on Kubernetes with no data loss. The operator provides self-healing, backup/restore, and allows scaling MySQL servers and routers with minimal downtime. A public beta of the open source community edition will be released in the coming weeks.
The document outlines Oracle's MySQL product roadmap, including recent and upcoming releases of MySQL Database, MySQL Cluster, MySQL Enterprise Monitor, and MySQL Workbench. It highlights key features and performance improvements in areas such as scalability, security, and high availability. It also discusses Oracle's ongoing investment in and certifications for MySQL to make it a better open source database for web and enterprise applications.
MySQL Database Architectures - High Availability and Disaster Recovery SolutionMiguel Araújo
MySQL InnoDB ClusterSet brings multi-datacenter capabilities to our solutions and makes it very easy to set up a disaster recovery architecture. Think multiple MySQL InnoDB Clusters into one single database architecture, fully managed from MySQL Shell and with full MySQL Router integration to make it easy to access the entire architecture.
This presentation covers the various solutions of MySQL for High Availability, Replication, and Disaster Recovery, with a special focus on InnoDB ClusterSet:
- The various features of InnoDB Clusterset
- How to setup MySQL InnoDB ClusterSet
- Ways to migrate from an existing MySQL InnoDB Cluster into MySQL InnoDB ClusterSet
- How to deal with various failures
- The various features of router integration make the connection to the database architecture easy.
MySQL High Availability Solutions - Avoid loss of service by reducing the r...Olivier DASINI
MySQL High Availability Solutions
Avoid loss of service by reducing the risk of failures
MySQL InnoDB Cluster
Collection of products that work together to provide a complete High Availability solution for MySQL
MySQL InnoDB ReplicaSet
Administer a set of MySQL instances running asynchronous replication
MySQL NDB Cluster
A high-availability, high-redundancy version of MySQL adapted for the distributed computing environment
Keith Larson, the MySQL Community Manager, gave an introduction to MySQL. He outlined MySQL's history from being started in the 1980s to its acquisition by Oracle. Larson then covered key MySQL concepts like storage engines, replication, partitioning, and clustering to provide high availability. He emphasized that MySQL remains free and open source for the community to use.
MySQL Day Paris 2016 - MySQL HA: InnoDB Cluster and NDB ClusterOlivier DASINI
The document discusses two high availability solutions for MySQL: InnoDB Cluster and NDB Cluster. InnoDB Cluster provides high availability using MySQL Group Replication and allows for read scaling. It has weak consistency, no sharding, and medium operational complexity. NDB Cluster uses the NDB storage engine, provides automatic sharding and strong consistency. It has high operational complexity but also provides native NoSQL APIs and load balancing. The document explores these solutions in further detail.
Deep Dive into MySQL InnoDB Cluster Read Scale-out Capabilities.pdfMiguel Araújo
MySQL's first Innovation Release is out, 8.1.0, and with it, we're introducing MySQL InnoDB Cluster Read Replicas.
The main purpose of secondaries on MySQL InnoDB Cluster is to be ready to take over when a primary member has failed (High Availability). This is done using MySQL Group Replication. Another commonly used purpose for the secondaries is to use them to offload read workloads away from the primary. With MySQL InnoDB Cluster Read Replicas, it's now possible to add asynchronous replicas to the database topology, to be used to offload read traffic away from primary or secondaries, to have dedicated read replicas, special purpose read replicas (e.g. for reporting), or to scale beyond what the secondaries can handle by adding multiple read replicas.
This talk covers the read replicas functionality, showcase its usage in different database architectures, and include a demonstration on its setup and management.
MySQL InnoDB Cluster - Meetup Oracle MySQL / AFUP ParisOlivier DASINI
MySQL InnoDB cluster is a collection of products that work together to provide a complete High Availability solution for MySQL. A group of MySQL servers can be configured to create a cluster using MySQL Shell.
In the presentation, we will learn on how to set up InnoDB cluster using the official MySQL Docker containers and run them with docker-compose. This presentation covers a demo, including how to connect to the cluster through MySQL Router using a simple application.
Mysql User Camp : 20th June - Mysql New FeaturesTarique Saleem
This document discusses new features in MySQL 5.7 and NoSQL support in MySQL. Some key points:
- MySQL 5.7 includes improvements to InnoDB for better transactional performance and scalability, as well as enhancements to replication, security, and other areas.
- NoSQL support allows direct access to MySQL data via Memcached APIs for simpler and faster key-value access while maintaining ACID guarantees.
- Benchmarks show NoSQL inserts into MySQL can be up to 9x faster than SQL inserts, and MySQL 5.7 can achieve over 1 million queries per second.
Mysql User Camp : 20-June-14 : Mysql New features and NoSQL SupportMysql User Camp
This slide was presented at Mysql User Camp Event on 20-June-14 at Oracle bangalore. This presentation gives a good insight about New Features in Mysql 5.7 DMR 4 and Nosql Support in Mysql.
Moodle Moot Spain: Moodle Available and Scalable with MySQL HA - InnoDB Clust...Keith Hollman
This document provides an overview of MySQL high availability and replication solutions. It discusses InnoDB Cluster, which allows MySQL to provide high availability and scaling features through MySQL Group Replication, MySQL Shell, and MySQL Router. It also covers MySQL InnoDB ReplicaSet, which provides an easy way to set up MySQL replication with MySQL Router. Additionally, it provides background information on MySQL replication, how it works, and its key components.
MySQL Day Paris 2018 - MySQL InnoDB Cluster; A complete High Availability sol...Olivier DASINI
Here are the steps to deploy a local 3-node MySQL InnoDB Cluster sandbox:
1. Start 3 local MySQL instances on ports 3310, 3320, 3330
2. Connect to the first instance using MySQL Shell
3. Run the following commands in MySQL Shell to bootstrap and join the nodes:
```js
// Bootstrap first node
dba.bootstrapCluster({
"host": "127.0.0.1",
"port": 3310
});
// Join second node
dba.addInstance({
"host": "127.0.0.1",
"port": 3320
});
// Join third node
dba.add
This document summarizes a talk about the MySQL Operator for InnoDB Cluster on Kubernetes. It discusses the trend of running databases on Kubernetes using operators, the need for operators to handle stateful applications like databases, and an overview of the Oracle MySQL Operator including its architecture, features, maturity level, and a demonstration of setting it up.
Similar to MySQL Database Architectures - InnoDB ReplicaSet & Cluster (20)
Upgrading MySQL databases do not come without risk. There is no guarantee that no problems will happen if you move to a new major MySQL version.
Should we just upgrade and rollback immediately if problems occur? But what if these problems only happen a few days after migrating to this new version?
You might have a database environment that is risk-adverse, where you really have to be sure that this new MySQL version will handle the workload properly.
Examples:
- Both MySQL 5.6 and 5.7 have a lot of changes in the MySQL Optimizer. It is expected that this improves performance of my queries, but is it really the case? What if there is a performance regression? How will this affect my database performance?
- Also, there are a lot of incompatible changes which are documented in the release notes, how do I know if I'm affected by this in my workload? It's a lot to read..
- Can I go immediately from MySQL 5.5 to 5.7 and skip MySQL 5.6 even though the MySQL documentation states that this is not supported?
- Many companies have staging environments, but is there a QA team and do they really test all functionality, under a similar workload?
This presentation will show you a process, using open source tools, of these types of migrations with a focus on assessing risk and fixing any problems you might run into prior to the migration.
This process can then be used for various changes:
- MySQL upgrades for major version upgrades
- Switching storage engines
- Changing hardware architecture
Additionally, we will describe ways to do the actual migration and rollback with the least amount of downtime.
Percona XtraDB Cluster vs Galera Cluster vs MySQL Group ReplicationKenny Gryp
This document provides an overview of different database replication technologies including Galera Cluster, Percona XtraDB Cluster, and MySQL Group Replication. It discusses similarities between the technologies such as multi-master replication topologies and consistency models. Key differences are also outlined relating to node provisioning, failure handling, and operational limitations of each solution. Known issues uncovered through quality assurance testing are also briefly mentioned.
Group Replication went Generally Available end of 2016, it introduces a 'synchronous' active:active multi-master eplication, in addition to asynchronous and semi-synchronous replication, the latter 2 being available in in MySQL for longtime.
As with any new feature, and especially with introducing active:active multi-master replication, it takes a while before companies are adopting the software in production database environment.
For example, even though MySQL 5.7 has been GA for more than a year, adoption is only starting to increase recently.
We can, and should, expect the same from Group Replication. As with every release, bugs will be found, and with new features, best practises still need to formed out of practical experience.
After giving a short introduction on what Group Replication is, I will cover my experience so far in evaluating Group Replication.
Multi Source Replication With MySQL 5.7 @ VerisureKenny Gryp
Verisure migrated their data warehouse from using Tungsten Replicator to native multi-source replication in MySQL 5.7 to simplify operations. They loaded data from production shards into the new data warehouse setup using XtraBackup backups and improved replication capacity with MySQL's parallel replication features. Some issues were encountered with replication lag reporting and crashes during the upgrade but most were resolved. Monitoring and management tools also required updates to support the new multi-source replication configuration.
MySQL Group Replication - HandsOn TutorialKenny Gryp
Group Replication is a plugin for MySQL that provides multi-master replication. It works by having each node send write transactions to other nodes through a group communication system. The writes are certified locally in an asynchronous manner to ensure total order of transactions across all nodes. Group Replication uses optimistic locking where local locks are released right after commit, and conflict detection happens during certification rather than at the start of transactions.
Online MySQL Backups with Percona XtraBackupKenny Gryp
Percona XtraBackup is a free, open source, complete online backup solution for all versions of Percona Server, MySQL® and MariaDB®.
Percona XtraBackup provides:
* Fast and reliable backups
* Uninterrupted transaction processing during backups
* Savings on disk space and network bandwidth with better compression
* Automatic backup verification
* Higher uptime due to faster restore time
This talk will discuss the various different features of Percona XtraBackup, including:
* Full & Incremental Backups
* Compression, Streaming & Encryption of Backups
* Backing Up To The Cloud (Swift).
* Percona XtraDB Cluster / Galera Cluster.
* Percona Server Specific features
Advanced Percona XtraDB Cluster in a nutshell... la suiteKenny Gryp
This document provides a hands-on tutorial for advanced Percona XtraDB Cluster users. It discusses setting up a 3 node PXC cluster environment in VirtualBox and bootstrapping the initial cluster. It then covers topics like avoiding state snapshot transfers when restarting MySQL, recovering from clean and unclean shutdowns, and reproducing and diagnosing different types of conflicts through examples.
Java MySQL Connector & Connection Pool Features & OptimizationKenny Gryp
This talk will give an overview of the different available Java MySQL connectors (Connector/J, MariaDB Java Connector) and connection pools (Commons-DBCP, C3P0, ...).
One of the things with the default configuration of these solutions is that they are very chatty. This can have a noticeable impact on application performance and database load. I've seen many environments where over 50% of the total amount of queries are caused by such behavior. This behavior will be explained through examples seen on production systems as well as recommendations on optimization will be made.
Load balancing and transparent failover solutions will be described for both MySQL's traditional asynchronous replication and Galera based replication (Percona XtraDB Cluster or MariaDB Galera Cluster).
Built-in MySQL Replication is known for its capability to enable to scale reads easily. However, there are some limitations and known issues with this solution because of the asynchronous nature of this replication. This talk will describe another way of doing MySQL replication, by using synchronous replication, available in Percona XtraDB Cluster. The open source solution will be explained and compared to traditional asynchronous MySQL replication, as well as some known use cases will be described. Percona XtraDB Cluster is an, open source, high availability and high scalability solution for MySQL clustering. Features include: Synchronous replication, Multi-master replication support, Parallel replication, Automatic node provisioning.
Software development... for all? (keynote at ICSOFT'2024)miso_uam
Our world runs on software. It governs all major aspects of our life. It is an enabler for research and innovation, and is critical for business competitivity. Traditional software engineering techniques have achieved high effectiveness, but still may fall short on delivering software at the accelerated pace and with the increasing quality that future scenarios will require.
To attack this issue, some software paradigms raise the automation of software development via higher levels of abstraction through domain-specific languages (e.g., in model-driven engineering) and empowering non-professional developers with the possibility to build their own software (e.g., in low-code development approaches). In a software-demanding world, this is an attractive possibility, and perhaps -- paraphrasing Andy Warhol -- "in the future, everyone will be a developer for 15 minutes". However, to make this possible, methods are required to tweak languages to their context of use (crucial given the diversity of backgrounds and purposes), and the assistance to developers throughout the development process (especially critical for non-professionals).
In this keynote talk at ICSOFT'2024 I presented enabling techniques for this vision, supporting the creation of families of domain-specific languages, their adaptation to the usage context; and the augmentation of low-code environments with assistants and recommender systems to guide developers (professional or not) in the development process.
COMPSAC 2024 D&I Panel: Charting a Course for Equity: Strategies for Overcomi...Hironori Washizaki
Hironori Washizaki, "Charting a Course for Equity: Strategies for Overcoming Challenges and Promoting Inclusion in the Metaverse", IEEE COMPSAC 2024 D&I Panel, 2024.
What is OCR Technology and How to Extract Text from Any Image for FreeTwisterTools
Discover the fascinating world of Optical Character Recognition (OCR) technology with our comprehensive presentation. Learn how OCR converts various types of documents, such as scanned paper documents, PDFs, or images captured by a digital camera, into editable and searchable data. Dive into the history, modern applications, and future trends of OCR technology. Get step-by-step instructions on how to extract text from any image online for free using a simple tool, along with best practices for OCR image preparation. Ideal for professionals, students, and tech enthusiasts looking to harness the power of OCR.
Seamless PostgreSQL to Snowflake Data Transfer in 8 Simple StepsEstuary Flow
Unlock the full potential of your data by effortlessly migrating from PostgreSQL to Snowflake, the leading cloud data warehouse. This comprehensive guide presents an easy-to-follow 8-step process using Estuary Flow, an open-source data operations platform designed to simplify data pipelines.
Discover how to seamlessly transfer your PostgreSQL data to Snowflake, leveraging Estuary Flow's intuitive interface and powerful real-time replication capabilities. Harness the power of both platforms to create a robust data ecosystem that drives business intelligence, analytics, and data-driven decision-making.
Key Takeaways:
1. Effortless Migration: Learn how to migrate your PostgreSQL data to Snowflake in 8 simple steps, even with limited technical expertise.
2. Real-Time Insights: Achieve near-instantaneous data syncing for up-to-the-minute analytics and reporting.
3. Cost-Effective Solution: Lower your total cost of ownership (TCO) with Estuary Flow's efficient and scalable architecture.
4. Seamless Integration: Combine the strengths of PostgreSQL's transactional power with Snowflake's cloud-native scalability and data warehousing features.
Don't miss out on this opportunity to unlock the full potential of your data. Read & Download this comprehensive guide now and embark on a seamless data journey from PostgreSQL to Snowflake with Estuary Flow!
Try it Free: https://dashboard.estuary.dev/register
introduction of Ansys software and basic and advance knowledge of modelling s...sachin chaurasia
Ansys Mechanical enables you to solve complex structural engineering problems and make better, faster design decisions. With the finite element analysis (FEA) solvers available in the suite, you can customize and automate solutions for your structural mechanics problems and parameterize them to analyze multiple design scenarios. Ansys Mechanical is a dynamic tool that has a complete range of analysis tools.
Cultural Shifts: Embracing DevOps for Organizational TransformationMindfire Solution
Mindfire Solutions specializes in DevOps services, facilitating digital transformation through streamlined software development and operational efficiency. Their expertise enhances collaboration, accelerates delivery cycles, and ensures scalability using cloud-native technologies. Mindfire Solutions empowers businesses to innovate rapidly and maintain competitive advantage in dynamic market landscapes.
Lots of bloggers are using Google AdSense now. It’s getting really popular. With AdSense, bloggers can make money by showing ads on their websites. Read this important article written by the experienced designers of the best website designing company in Delhi –
An MVP (Minimum Viable Product) mobile application is a streamlined version of a mobile app that includes only the core features necessary to address the primary needs of its users. The purpose of an MVP is to validate the app concept with minimal resources, gather user feedback, and identify any areas for improvement before investing in a full-scale development. This approach allows businesses to quickly launch their app, test its market viability, and make data-driven decisions for future enhancements, ensuring a higher likelihood of success and user satisfaction.
Are you wondering how to migrate to the Cloud? At the ITB session, we addressed the challenge of managing multiple ColdFusion licenses and AWS EC2 instances. Discover how you can consolidate with just one EC2 instance capable of running over 50 apps using CommandBox ColdFusion. This solution supports both ColdFusion flavors and includes cb-websites, a GoLang binary for managing CommandBox websites.
Sami provided a beginner-friendly introduction to Amazon Web Services (AWS), covering essential terms, products, and services for cloud deployment. Participants explored AWS' latest Gen AI offerings, making it accessible for those starting their cloud journey or integrating AI into coding practices.
Attendance Tracking From Paper To DigitalTask Tracker
If you are having trouble deciding which time tracker tool is best for you, try "Task Tracker" app. It has numerous features, including the ability to check daily attendance sheet, and other that make team management easier.
Efficient hot work permit software for safe, streamlined work permit management and compliance. Enhance safety today. Contact us on +353 214536034.
https://sheqnetwork.com/work-permit/
3.
Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for information purpose only, and may not be
incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied up
in making purchasing decisions. The development, release and timing of any features or functionality described for Oracle´s
product remains at the sole discretion of Oracle.
3 / 28
5. Past, Present & Future
In The Past - MANUAL
Setting up Replication topology was done manually, taking many steps
including user management, restoring backups, configuring replication...
MySQL offered the technical pieces, leaving it up to the user to setup an (always customized) architecture
This requires technical components ... bringing lot's of work for DBA's and experts, who spent their time automating
4 / 28
6. Past, Present & Future
In The Past - MANUAL
Setting up Replication topology was done manually, taking many steps
including user management, restoring backups, configuring replication...
MySQL offered the technical pieces, leaving it up to the user to setup an (always customized) architecture
This requires technical components ... bringing lot's of work for DBA's and experts, who spent their time automating
2016-2019 - MySQL InnoDB Cluster
Group Replication: Automatic membership changes, network partition handling, consistency...
Shell to provide a powerful interface that helps in automating an integrating all components
InnoDB CLONE to automatically provision members, fully integrated in InnoDB
4 / 28
7. Past, Present & Future
In The Past - MANUAL
Setting up Replication topology was done manually, taking many steps
including user management, restoring backups, configuring replication...
MySQL offered the technical pieces, leaving it up to the user to setup an (always customized) architecture
This requires technical components ... bringing lot's of work for DBA's and experts, who spent their time automating
2016-2019 - MySQL InnoDB Cluster
Group Replication: Automatic membership changes, network partition handling, consistency...
Shell to provide a powerful interface that helps in automating an integrating all components
InnoDB CLONE to automatically provision members, fully integrated in InnoDB
2020 - MySQL InnoDB Replicaset
'classic', 'asynchronous' Replication based Solution, fully integrated
4 / 28
8. MySQL InnoDB Cluster
"A single product — MySQL — with high availability and scaling features baked in;
providing an integrated end-to-end solution that is easy to use."
5 / 28
9. MySQL InnoDB Cluster
"A single product — MySQL — with high availability and scaling features baked in;
providing an integrated end-to-end solution that is easy to use."
5 / 28
10. Components:
MySQL Server
MySQL Group Replication
MySQL Shell
MySQL Router
MySQL InnoDB Cluster
"A single product — MySQL — with high availability and scaling features baked in;
providing an integrated end-to-end solution that is easy to use."
5 / 28
11. One Product: MySQL
All components developed together
Integration of all components
Full stack testing
MySQL InnoDB Cluster - Goals
6 / 28
12. One Product: MySQL
All components developed together
Integration of all components
Full stack testing
Easy to Use
One client: MySQL Shell
Integrated orchestration
Homogenous servers
MySQL InnoDB Cluster - Goals
6 / 28
14. High Available Distributed MySQL DB
Fault tolerance
Automatic failover
Active/Active update anywhere (limits apply)
Automatic membership management
Adding/removing members
Network partitions, failures
Conflict detection and resolution
Prevents data loss
MySQL Group Replication
7 / 28
15. MySQL Group Replication
Implementation of Replicated Database State Machine
Total Order - Writes
XCOM - Paxos implementation
Configurable Consistency Guarantees
eventual consistency
8.0+: per session & global read/write consistency
Using MySQL replication framework by design
binary logs
relay logs
GTIDs: Global Transaction IDs
Generally Available since MySQL 5.7
Supported on all platforms: linux, windows, solaris, macosx, freebsd
8 / 28
16. Recovery Time Objective (RTO)
How fast should the service recover from a failure
Recovery Point Objective (RPO)
How much data loss can the service lose from a failure
Business Requirements
9 / 28
17. Recovery Time Objective (RTO)
How fast should the service recover from a failure
Recovery Point Objective (RPO)
How much data loss can the service lose from a failure
Types of Failures
High Availability: Single Server Failure, Network Partition
Disaster Recovery: Full Region/Network Failure
Human Error: Little Bobby Tables
How Much
None
few seconds
minutes
hours
day
...
Business Requirements
9 / 28
18. Consistency: No Data Loss (RPO=0)
in event of failure of (primary) member
Split brain prevention (Quorum)
MySQL Group Replication - Use Cases
10 / 28
19. Consistency: No Data Loss (RPO=0)
in event of failure of (primary) member
Split brain prevention (Quorum)
Highly Available: Automatic Failover
Primary members are automatically elected
Automatic Network Partition handling
MySQL Group Replication - Use Cases
10 / 28
20. Consistency: No Data Loss (RPO=0)
in event of failure of (primary) member
Split brain prevention (Quorum)
Highly Available: Automatic Failover
Primary members are automatically elected
Automatic Network Partition handling
Read Scaleout
Add/Remove members as needed
Replication Lag handling with Flow Control
Configurable Consistency Levels
Eventual
Full Consistency -- no stale reads
MySQL Group Replication - Use Cases
10 / 28
21. Consistency: No Data Loss (RPO=0)
in event of failure of (primary) member
Split brain prevention (Quorum)
Highly Available: Automatic Failover
Primary members are automatically elected
Automatic Network Partition handling
Read Scaleout
Add/Remove members as needed
Replication Lag handling with Flow Control
Configurable Consistency Levels
Eventual
Full Consistency -- no stale reads
Active/Active environments
Write to many members at the same time
ordered writes within the group (XCOM)
guaranteed consistency
Good write performance
due to Optimistic Locking
(workload dependent)
MySQL Group Replication - Use Cases
10 / 28
23. Transparent Access to Database Arch.
"provide transparent routing between your application and
back-end MySQL Servers"
Transparent client connection routing
Load balancing
Application connection failover
Little to no configuration needed
Stateless design offers easy HA client routing
Router as part of the application stack
Integration into InnoDB Cluster & InnoDB ReplicaSet
Understands Group Replication & Replication
topology
Currently TCP Port each for PRIMARY and NON-PRIMARY
traffic
MySQL Router
11 / 28
25. Database Administration Interface
"MySQL Shell provides the developer and DBA with a single
intuitive, flexible, and powerful interface for all MySQL
related tasks!"
Multi-Language: JavaScript, Python, and SQL
Naturally scriptable
Supports Document and Relational models
Exposes full Development and Admin API
Classic MySQL protocol and X protocol
MySQL Shell
12 / 28
27. MySQL InnoDB Cluster
mysql-js> c admin@mysql1
mysql-js> cluster = dba.createCluster('cluster')
MySQL Shell - Easy to Use
13 / 28
28. MySQL InnoDB Cluster
mysql-js> c admin@mysql1
mysql-js> cluster = dba.createCluster('cluster')
Configure server to add later:
mysql-js> dba.con gureInstance('admin@mysql2')
MySQL Shell - Easy to Use
13 / 28
29. MySQL InnoDB Cluster
mysql-js> c admin@mysql1
mysql-js> cluster = dba.createCluster('cluster')
Configure server to add later:
mysql-js> dba.con gureInstance('admin@mysql2')
Add server to the Cluster:
mysql-js> cluster.addInstance('admin@mysql2')
MySQL Shell - Easy to Use
13 / 28
30. MySQL InnoDB Cluster
mysql-js> c admin@mysql1
mysql-js> cluster = dba.createCluster('cluster')
Configure server to add later:
mysql-js> dba.con gureInstance('admin@mysql2')
Add server to the Cluster:
mysql-js> cluster.addInstance('admin@mysql2')
Bootstrap MySQL Router
$ sudo mysqlrouter --user=mysqlrouter --bootstrap
$ sudo systemctl start mysqlrouter
MySQL Shell - Easy to Use
13 / 28
31. mysql-js> cluster.status()
{
"clusterName": "cluster",
"defaultReplicaSet": {
"name": "default",
"primary": "mysql1:3306",
"ssl": "REQUIRED",
"status": "OK",
"statusText": "Cluster is ONLINE and can
tolerate up to ONE failure.",
"topology": {
"mysql1:3306": {
"address": "mysql1:3306",
"mode": "R/W",
"readReplicas": {},
"role": "HA",
"status": "ONLINE"
},
"mysql2:3306": {
"address": "mysql2:3306",
"mode": "R/O",
"readReplicas": {},
"role": "HA",
"status": "ONLINE"
},
"mysql3:3306": {
"address": "mysql3:3306",
"mode": "R/O",
"readReplicas": {},
"role": "HA",
"status": "ONLINE"
}
}
}
MySQL Shell - Easy to Use
Check the Cluster status:
14 / 28
33. Many of our customers have adopted InnoDB Cluster!
Fully integrated MySQL Router
Automatic Routing
Ease of use with MySQL Shell
Configuring, Adding, Removing members
Group Replication Architecture
Providing Consistency
Automatic Failover
Network Partition Handling
No data loss in case of failure
Automatic Member Provisioning (CLONE)
MySQL InnoDB Cluster - Adoption
16 / 28
34. Introducing MySQL InnoDB ReplicaSet!
8.0.19 Feature!
Fully integrated MySQL Router
Automatic Routing
Ease of use with MySQL Shell
Configuring, Adding, Removing members
Automatic Member Provisioning (CLONE)
Replication Architecture:
(manual) Switchover & Failover
(asynchronous) Read Scaleout
'Simple' Replication architecture:
no network/hardware requirements
Providing Availability on PRIMARY when
issues with secondaries or network
MySQL InnoDB Replicaset
17 / 28
35. Past MySQL InnoDB ReplicaSet
Restore a backup to provision a member Automatically provisioning new members:
InnoDB CLONE
MySQL InnoDB ReplicaSet - Features
18 / 28
36. Past MySQL InnoDB ReplicaSet
Restore a backup to provision a member Automatically provisioning new members:
InnoDB CLONE
Configure Replication Users
Configure Replication
MySQL Shell Automatically configures users &
replication
MySQL InnoDB ReplicaSet - Features
18 / 28
37. Past MySQL InnoDB ReplicaSet
Restore a backup to provision a member Automatically provisioning new members:
InnoDB CLONE
Configure Replication Users
Configure Replication
MySQL Shell Automatically configures users &
replication
Manually configuring, adding removing servers in
Application, MySQL Router (or other proxy)
Integrated MySQL Router load balancing
Only need to bootstrap Router
Router is stateless, adapts to topology changes
MySQL InnoDB ReplicaSet - Features
18 / 28
38. Past MySQL InnoDB ReplicaSet
Restore a backup to provision a member Automatically provisioning new members:
InnoDB CLONE
Configure Replication Users
Configure Replication
MySQL Shell Automatically configures users &
replication
Manually configuring, adding removing servers in
Application, MySQL Router (or other proxy)
Integrated MySQL Router load balancing
Only need to bootstrap Router
Router is stateless, adapts to topology changes
Manually or relying on external tools to make topology
changes
Easy to use manual switchover/failover
MySQL InnoDB ReplicaSet - Features
18 / 28
39. Past MySQL InnoDB ReplicaSet
Restore a backup to provision a member Automatically provisioning new members:
InnoDB CLONE
Configure Replication Users
Configure Replication
MySQL Shell Automatically configures users &
replication
Manually configuring, adding removing servers in
Application, MySQL Router (or other proxy)
Integrated MySQL Router load balancing
Only need to bootstrap Router
Router is stateless, adapts to topology changes
Manually or relying on external tools to make topology
changes
Easy to use manual switchover/failover
Use additional monitoring tool log in on all machines to
check topology status
See status of the topology through MySQL Shell
status()
MySQL InnoDB ReplicaSet - Features
18 / 28
40. Past MySQL InnoDB ReplicaSet
MySQL InnoDB ReplicaSet - Features
19 / 28
41. Past MySQL InnoDB ReplicaSet
complexity: user is responsible for the full configuration
of every component and it's settings
Shell configures Server, Router, Replication in a
standardized best practice setup, prevents mistakes
MySQL InnoDB ReplicaSet - Features
19 / 28
42. Past MySQL InnoDB ReplicaSet
complexity: user is responsible for the full configuration
of every component and it's settings
Shell configures Server, Router, Replication in a
standardized best practice setup, prevents mistakes
every setup is a customized setup Standard Solution -- Supported & QA'ed by Oracle
MySQL InnoDB ReplicaSet - Features
19 / 28
43. Past MySQL InnoDB ReplicaSet
complexity: user is responsible for the full configuration
of every component and it's settings
Shell configures Server, Router, Replication in a
standardized best practice setup, prevents mistakes
every setup is a customized setup Standard Solution -- Supported & QA'ed by Oracle
A lot of manual steps and additional software required,
always customized and often overengineered by MySQL
DBA's
Easy to use, even for MySQL beginner
MySQL InnoDB ReplicaSet - Features
19 / 28
44. MySQL InnoDB ReplicaSet - Requirements & Limitations
Requirements:
MySQL 8 (SET PERSIST!)
GTID
Limitations:
Manual failover
No multi-primary as such topology cannot guarantee data consistency
All secondary members replicate from primary
20 / 28
46. MySQL InnoDB ReplicaSet - MySQL Router Integration
--bootstrap to automatically configure
Metadata schema contains Replication Topology
Health checks are performed to all members
Switchover to new primary (setPrimaryInstance()):
Shell performs topology change, configures super_read_only and updates view_id in metadata
Router automatically sees higher view_id
and will redirect primary traffic to new primary
When the Primary is lost: forcePrimaryInstance()
Shell performs topology change, updates view_id in metadata and invalidates lost primary
Router will notice topology change by higher view_id in metadata (if network allows)
and automatically connect to new Primary
22 / 28
48. MySQL InnoDB Cluster MySQL InnoDB ReplicaSet
mysql-js> c admin@mysql1
mysql-js> cluster = dba.createCluster('cluster')
mysql-js> c admin@mysql1
mysql-js> rs = dba.createReplicaSet('replicaset')
MySQL Shell - Easy to Use
23 / 28
49. MySQL InnoDB Cluster MySQL InnoDB ReplicaSet
mysql-js> c admin@mysql1
mysql-js> cluster = dba.createCluster('cluster')
mysql-js> c admin@mysql1
mysql-js> rs = dba.createReplicaSet('replicaset')
Configure server to add later
mysql-js> dba.con gureInstance('admin@mysql2') mysql-js> dba.con gureReplicaSetInstance('admin@mysql2')
MySQL Shell - Easy to Use
23 / 28
50. MySQL InnoDB Cluster MySQL InnoDB ReplicaSet
mysql-js> c admin@mysql1
mysql-js> cluster = dba.createCluster('cluster')
mysql-js> c admin@mysql1
mysql-js> rs = dba.createReplicaSet('replicaset')
Configure server to add later
mysql-js> dba.con gureInstance('admin@mysql2') mysql-js> dba.con gureReplicaSetInstance('admin@mysql2')
Add server to the Cluster
mysql-js> cluster.addInstance('admin@mysql2') mysql-js> rs.addInstance('admin@mysql2')
MySQL Shell - Easy to Use
23 / 28
51. MySQL InnoDB Cluster MySQL InnoDB ReplicaSet
mysql-js> c admin@mysql1
mysql-js> cluster = dba.createCluster('cluster')
mysql-js> c admin@mysql1
mysql-js> rs = dba.createReplicaSet('replicaset')
Configure server to add later
mysql-js> dba.con gureInstance('admin@mysql2') mysql-js> dba.con gureReplicaSetInstance('admin@mysql2')
Add server to the Cluster
mysql-js> cluster.addInstance('admin@mysql2') mysql-js> rs.addInstance('admin@mysql2')
Bootstrap MySQL Router
$ sudo mysqlrouter --user=mysqlrouter --bootstrap
$ sudo systemctl start mysqlrouter
$ sudo mysqlrouter --user=mysqlrouter --bootstrap
$ sudo systemctl start mysqlrouter
MySQL Shell - Easy to Use
Demo: https://mysqlserverteam.com/introducing-mysql-innodb-replicaset
23 / 28
52. By design chosen to be Manual failover
Having external monitoring processes decide failover can
cause a lot of false positives.
External tool decides, if the tool has issues: even
bigger issues.
Split brain issues
Majority of production deployments are configured
with Manual Failover, which increases Uptime!
When automatic failover is needed:
use MySQL InnoDB Cluster instead of Semi-Sync
MySQL InnoDB ReplicaSet - Manual Failover
24 / 28
53. Example:
1 Primary, 2 Secondaries, 2 Proxy hosts (App servers)
1 Management server: monitoring and making Topology
changes automatically
Problem: Management server & replica server is partitioned
from all other servers
What will happen?
MySQL InnoDB ReplicaSet - Manual Failover
25 / 28
54. Example:
1 Primary, 2 Secondaries, 2 Proxy hosts (App servers)
1 Management server: monitoring and making Topology
changes automatically
Problem: Management server & replica server is partitioned
from all other servers
What will happen?
The management host might promote the secondary
causing split brain
use MySQL InnoDB Cluster over Semi-Sync
With semi-sync, all members have to ack (prevent split
brain), causing downtime with every small glitch
MySQL InnoDB ReplicaSet - Manual Failover
26 / 28
56. MySQL InnoDB Cluster MySQL InnoDB ReplicaSet
Single Primary, multiple Secondaries
Multi Primary mode (write to all)
Single Primary, multiple Secondaries
Which Solution fits me?
27 / 28
57. MySQL InnoDB Cluster MySQL InnoDB ReplicaSet
Single Primary, multiple Secondaries
Multi Primary mode (write to all)
Single Primary, multiple Secondaries
Read Scaleout with configurable consistent reads Read Scaleout with stale reads
Which Solution fits me?
27 / 28
58. MySQL InnoDB Cluster MySQL InnoDB ReplicaSet
Single Primary, multiple Secondaries
Multi Primary mode (write to all)
Single Primary, multiple Secondaries
Read Scaleout with configurable consistent reads Read Scaleout with stale reads
All members partake in consensus
(write performance is as fast as it's slowest node)
Secondary members only get stream of changes (binlog),
does not impact Primary
Which Solution fits me?
27 / 28
59. MySQL InnoDB Cluster MySQL InnoDB ReplicaSet
Single Primary, multiple Secondaries
Multi Primary mode (write to all)
Single Primary, multiple Secondaries
Read Scaleout with configurable consistent reads Read Scaleout with stale reads
All members partake in consensus
(write performance is as fast as it's slowest node)
Secondary members only get stream of changes (binlog),
does not impact Primary
Stable network is required:
Network glitches cause stalls/membership changes
Uneven amount of members (3-5)
No network requirements:
glitches in network do not impact availability
2 or more members
Which Solution fits me?
27 / 28
60. MySQL InnoDB Cluster MySQL InnoDB ReplicaSet
Single Primary, multiple Secondaries
Multi Primary mode (write to all)
Single Primary, multiple Secondaries
Read Scaleout with configurable consistent reads Read Scaleout with stale reads
All members partake in consensus
(write performance is as fast as it's slowest node)
Secondary members only get stream of changes (binlog),
does not impact Primary
Stable network is required:
Network glitches cause stalls/membership changes
Uneven amount of members (3-5)
No network requirements:
glitches in network do not impact availability
2 or more members
No data loss in case of member failure
(Recovery Point Objective = 0 (RPO))
Consistency
During planned switchover: No data loss, split brain is
handled
During manual Unplanned failover: up to user
Which Solution fits me?
27 / 28
61. MySQL InnoDB Cluster MySQL InnoDB ReplicaSet
Single Primary, multiple Secondaries
Multi Primary mode (write to all)
Single Primary, multiple Secondaries
Read Scaleout with configurable consistent reads Read Scaleout with stale reads
All members partake in consensus
(write performance is as fast as it's slowest node)
Secondary members only get stream of changes (binlog),
does not impact Primary
Stable network is required:
Network glitches cause stalls/membership changes
Uneven amount of members (3-5)
No network requirements:
glitches in network do not impact availability
2 or more members
No data loss in case of member failure
(Recovery Point Objective = 0 (RPO))
Consistency
During planned switchover: No data loss, split brain is
handled
During manual Unplanned failover: up to user
Automatic Failover in case of failure
(Easier to achieve a lower Recovery Time Objective
(RTO) with stable network/servers)
Manual switchover/failover only
Which Solution fits me?
27 / 28
62. MySQL InnoDB Cluster MySQL InnoDB ReplicaSet
Database Solutions
http://www.mysql.com
http://dev.mysql.com/doc
http://www.mysqlhighavailability.com
http://www.mysqlserverteam.com
Kenny Gryp
MySQL Product Manager
28 / 28