Skip to content
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

[FEATURE REQUEST] Periodic progress report #1450

Open
utdrmac opened this issue Mar 20, 2024 · 0 comments
Open

[FEATURE REQUEST] Periodic progress report #1450

utdrmac opened this issue Mar 20, 2024 · 0 comments

Comments

@utdrmac
Copy link

utdrmac commented Mar 20, 2024

Describe the Feature Request
A large table dumping on thread 3, while threads 1,2,4 have finished, makes it appear as mydumper is frozen

** Message: 20:24:23.267: InnoDB tables completed
** Message: 20:24:23.268: Waiting threads to complete
** Message: 20:24:23.320: Thread 4: dumping view for `envera`.`community_vehicles_view`
** Message: 20:24:23.484: Thread 4: dumping view for `envera`.`report_accounts`
** Message: 20:24:23.650: Thread 4: dumping view for `envera`.`report_users`
** Message: 20:24:23.807: Thread 4: dumping view for `envera`.`vw_duplicated_tags`
** Message: 20:24:23.965: Thread 4: dumping triggers for `envera`
** Message: 20:24:24.131: Thread 4: shutting down

In the above, it states "InnoDB tables completed", but that's not 100% true. Threads 1, 2, and 3 are still dumping large tables. But you can't really see that unless you scroll back/troll through logs.

Expected output
Perhaps after each thread has finished, the status of remaining threads is re-outputted so users can see more clearly that other things are still happening.

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

No branches or pull requests

2 participants