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

replication lag can only be displayed to the second #707

Closed
csuzhangxc opened this issue Jun 3, 2020 · 1 comment
Closed

replication lag can only be displayed to the second #707

csuzhangxc opened this issue Jun 3, 2020 · 1 comment
Labels
severity/moderate type/bug This issue is a bug report
Milestone

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.

    set enable-heartbeat: true for task.yaml.

  2. What did you expect to see?

    the replication lag can be a valid less than 1s.

  3. What did you see instead?

    thre replication lag always >= 1s.

  4. Versions of the cluster

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

      v1.0.5
      
@csuzhangxc csuzhangxc added the type/bug This issue is a bug report label Jun 3, 2020
@csuzhangxc csuzhangxc added this to the v1.0.6 milestone Jun 3, 2020
@csuzhangxc
Copy link
Member Author

we use UTC_TIMESTAMP() to generate the current timestamp before, but it will get a fractional seconds precision with 0.

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

No branches or pull requests

2 participants