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

do not "auto resume" for errors in dump unit #837

Closed
csuzhangxc opened this issue Jul 28, 2020 · 0 comments · Fixed by #872
Closed

do not "auto resume" for errors in dump unit #837

csuzhangxc opened this issue Jul 28, 2020 · 0 comments · Fixed by #872
Assignees
Labels
severity/minor type/bug This issue is a bug report

Comments

@csuzhangxc
Copy link
Member

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do? If possible, provide a recipe for reproducing the error.

    Run a task with "Couldn't acquire global lock"

  2. What did you expect to see?

    the task keep paused

  3. What did you see instead?

    still "auto resume".

    for errors in dump unit, most of them should not succeed after resumed, so no extra workload on upstream MySQL/MariaDB is better.

  4. Versions of the cluster

    • DM version (run dmctl -V or dm-worker -V or dm-master -V):

      v1.0.6
      
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity/minor type/bug This issue is a bug report
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants