Skip to content

Commit

Permalink
Remove failover
Browse files Browse the repository at this point in the history
  • Loading branch information
dveeden committed Oct 26, 2024
1 parent ff1dab4 commit 06e800a
Show file tree
Hide file tree
Showing 9 changed files with 0 additions and 754 deletions.
13 changes: 0 additions & 13 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,6 @@ This repo uses [Changelog](CHANGELOG.md).
* [Incremental dumping](#canal)
* [Client](#client)
* [Fake server](#server)
* [Failover](#failover)
* [database/sql like driver](#driver)

## Replication
Expand Down Expand Up @@ -327,18 +326,6 @@ MySQL [(none)]>
>
> To customize server configurations, use ```NewServer()``` and create connection via ```NewCustomizedConn()```.

## Failover

Failover supports to promote a new master and let replicas replicate from it automatically when the old master was down.

Failover supports MySQL >= 5.6.9 with GTID mode, if you use lower version, e.g, MySQL 5.0 - 5.5, please use [MHA](http://code.google.com/p/mysql-master-ha/) or [orchestrator](https://github.com/outbrain/orchestrator).

At the same time, Failover supports MariaDB >= 10.0.9 with GTID mode too.

Why only GTID? Supporting failover with no GTID mode is very hard, because replicas can not find the proper binlog filename and position with the new master.
Although there are many companies use MySQL 5.0 - 5.5, I think upgrade MySQL to 5.6 or higher is easy.

## Driver

Driver is the package that you can use go-mysql with go database/sql like other drivers. A simple example:
Expand Down
11 changes: 0 additions & 11 deletions failover/const.go

This file was deleted.

8 changes: 0 additions & 8 deletions failover/doc.go

This file was deleted.

67 changes: 0 additions & 67 deletions failover/failover.go

This file was deleted.

176 changes: 0 additions & 176 deletions failover/failover_test.go

This file was deleted.

22 changes: 0 additions & 22 deletions failover/handler.go

This file was deleted.

Loading

0 comments on commit 06e800a

Please sign in to comment.