hpc / hpc/mpifileutils

[Request] dsync --write-verify option?

Open
#581 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
200
Forks
85
Avg merge
3d 21h
Merged PRs (30d)
2

Description

Hi,

We are looking at ways to increase the performance of dsync -c (content) compare. As you would imagine, this can be very time-consuming but at the same time users want this "to be sure" that final sync has an exact copy of their data.

We can do a lot of syncs before final-sync and cut-over to a new file system. However, the dsync -c right now is all or nothing and that takes a long time then for a final-sync for cut-over and that final-sync is when users are "down" so they don't make any changes.

If dsync had an option somewhere between -c (content) and -lite (like dcmp), then it could be ideal when for when doing a series of dsync before final-sync.

This the -lite-content option compares size, mtime and atime (assuming --open-noatime is used as well) such that if all 3 match then content is not compared. But if one is different (even if just atime) the full content is compared.

Thank you for these great utilities!

  • Mark

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the dsync implementations for -c, -lite, and the related dcmp comparison behavior. Define the new option's semantics around size, mtime, and atime, including --open-noatime, and confirm that content is compared only when those attributes differ; done means the behavior is covered by appropriate tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
cli, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.