You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 8, 2021. It is now read-only.
Is your feature request related to a problem? Please describe:
A large restore today can appear to get "stuck" in some phases, especially "post-processing", where it's possible to see dozens of messages like this over the course of an hour or more:
We are planning to take two steps to optimize the progress log:
Short term optimization. for local backend, add progress for import phase something like [import=66GB/100GB(66%)].
Long term optimization. We will optimize lightning concurrent model to make restore and importer run in pipeline better to avoid the long tail import phase. After this optimization, the current progress will accurately repression the total progress.
Feature Request
Is your feature request related to a problem? Please describe:
A large restore today can appear to get "stuck" in some phases, especially "post-processing", where it's possible to see dozens of messages like this over the course of an hour or more:
Describe the feature you'd like:
We should find better ways to communicate incremental progress information for every phrase of restore.
The text was updated successfully, but these errors were encountered: