rollback disk operation when database commit failed

Open
#8 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
50/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
backend, databases

Research direction

Start in src/cas/fs.rs around line 458 and trace the object-storage path through the metadata database commit. Confirm the failure path removes the disk object when the commit fails, and verify the object is not left behind after an unsuccessful store.

Written by the indexing model from the issue text.

Description

when storing object, there is possibility that the metadata DB commit failed after we successfully wrote the block to the disk.
We need to delete the object in the disk to keep the disk clean.

https://github.com/threefoldtech/s3-cas/blob/7f20502aeaefcf1405f9abf352eb7776737f72b6/src/cas/fs.rs#L458

Dominant language
Rust
Stars
0
Forks
1
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from threefoldtech/qss_storage

All issues in threefoldtech/qss_storage

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.