-
Notifications
You must be signed in to change notification settings - Fork 287
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
DM: more detailed query-status #7343
Labels
Comments
/area dm |
/assign |
Duration (start-time) should be kept across failover, for DM in engine scenario only the metaDB is survived across failover, so we might only add this field to the response of engine job's status. |
This was referenced Oct 24, 2022
This was referenced Nov 1, 2022
ti-chi-bot
pushed a commit
that referenced
this issue
Nov 3, 2022
14 tasks
ti-chi-bot
pushed a commit
that referenced
this issue
Nov 7, 2022
ti-chi-bot
pushed a commit
that referenced
this issue
Nov 9, 2022
ti-chi-bot
pushed a commit
that referenced
this issue
Nov 10, 2022
ti-chi-bot
pushed a commit
that referenced
this issue
Nov 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
no
Describe the feature you'd like
add some status:
for sync: rows/s(now is tps), in fact, tps is the rps(rows per sec), a naming problemfor load: calculate by rows(bytes is accurate)Describe alternatives you've considered
No response
Teachability, Documentation, Adoption, Migration Strategy
display in TiDB cloud
The text was updated successfully, but these errors were encountered: