Skip to content
This repository has been archived by the owner on Feb 10, 2023. It is now read-only.

go-mydumper some problems #31

Open
Dragonzlx opened this issue Sep 15, 2020 · 1 comment
Open

go-mydumper some problems #31

Dragonzlx opened this issue Sep 15, 2020 · 1 comment

Comments

@Dragonzlx
Copy link

Hi, i am using go-mydumper in mysql 8.0.19 group replication, it failed to restore a table with 70M, i check the mysql error log, it seems too much memory when go-mydumper to restore, so it lead to mysql out of memory, and lead to node kick out from the cluster, there is some suggestion on below:

  1. myloader consumes too much memory to restore from a backup
  2. it should be better to add parallel options to backup
@BohuTANG
Copy link
Contributor

  1. Need to determine who use the the memory first, go-mydumper is streaming fetch, it's memory efficent.
  2. go-mydumper is parallel based on database

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

No branches or pull requests

2 participants