Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MySQL ClusterDB Ansible Script Addition #44

Open
wants to merge 3 commits into
base: dev
Choose a base branch
from
Open

Conversation

myasas
Copy link

@myasas myasas commented Oct 3, 2019

@nilesh93 , @kosalag, @sanjiva
The POC (poc-mysql_cluster_db.pdf) was concluded with x2 options and I selected option 2 as a GO, considering factors such as, timelines, ease of implementation and maintainability, etc.,

Note: Please note that poc-mysql_cluster_db.pdf in myasas/Deployment includes the POC conducted on configuring x3 node mysql clusted db with HA proxy.

  1. option 1: MySQL InnoDB Cluster
  • Uses Group Replication.
  • It uses the innoDB engine (same as its used in single node instances, which developers use)
  • The option which has the least amount of dependencies on third parties
  • Don't have to rely on external tools, scripts or other components
  • It leverages proven MySQL features including InnoDB, GTIDs, binary logs, multi-threaded slave execution, multi-source replication and Performance Schema.
  1. option 2: Galera Cluster for MySQL
  • Uses Master-Master replication with HA proxy.
  • It uses the innoDB engine (same as its used in single node instances, which developers use)
  • It has the least amount of configurations compared to option one, though it has dependencies on Galera.
  • It has Automatic Node Provisioning feature where its not needed to manually back up the database and copy it to the new node.

Thank you !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant