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

clone on a big dir is slow and progress display incorrect. #4806

Open
zhoucheng361 opened this issue Apr 30, 2024 · 0 comments
Open

clone on a big dir is slow and progress display incorrect. #4806

zhoucheng361 opened this issue Apr 30, 2024 · 0 comments
Labels

Comments

@zhoucheng361
Copy link
Contributor

zhoucheng361 commented Apr 30, 2024

What happened:

  1. the meta op is too slow.
  2. ETA in progress is a minus number.
  3. at the beginning of clone, the progress is 0 for a long time.
image image

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?

Environment:

  • JuiceFS version (use juicefs --version) or Hadoop Java SDK version:
  • Cloud provider or hardware configuration running JuiceFS:
  • OS (e.g cat /etc/os-release):
  • Kernel (e.g. uname -a):
  • Object storage (cloud provider and region, or self maintained):
  • Metadata engine info (version, cloud provider managed or self maintained):
  • Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
  • Others:
@zhoucheng361 zhoucheng361 added the kind/bug Something isn't working label Apr 30, 2024
@zhoucheng361 zhoucheng361 changed the title clone on a big dir is very slow and progress display incorrect. clone on a big dir is slow and progress display incorrect. Apr 30, 2024
@zhoucheng361 zhoucheng361 added kind/enhancement and removed kind/bug Something isn't working labels Apr 30, 2024
@SandyXSD SandyXSD added the priority/normal The default priority label May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants