#450 closed enhancement (duplicate)

checker / repair agent

Reported by: warner Owned by:
Priority: major Milestone: undecided
Component: code-storage Version: 1.0.0
Keywords: verify repair Cc:
Launchpad Bug:


Our old roadmap.txt had "Checker/Repairer? steps 1.5/2/3" as "maintain file manifest, centralized chekcer/repair-agent, nodes also check their own files".

The idea was that, as a first step, nodes should simply keep track of their "manifest": a list of all the files that they wanted to keep alive. Files that cease to be on this list should be deleted (see #449).

Once we have this list, we can use it to decide what files we want to check/verify/repair. Passing the list to a centralized agent would offload the work from the clients (also allowing them to go offline for extended periods of time). This interacts strongly with #119 (lease expiration / deletion / filechecking / quotas).

We could have a central agent check up on files, or have the client node do it, or both.

Change History (4)

comment:1 Changed at 2008-09-03T01:35:22Z by warner

  • Milestone changed from undecided to 1.3.0

comment:2 Changed at 2009-02-07T19:48:09Z by zooko

  • Milestone 1.3.0 deleted

We have a checker/verifier/repairer in trunk, but not an agent. We don't need an agent for 1.3.0.

comment:3 Changed at 2010-02-11T03:37:41Z by davidsarah

  • Keywords verify repair added
  • Milestone set to undecided

comment:4 Changed at 2010-12-12T23:16:03Z by davidsarah

  • Resolution set to duplicate
  • Status changed from new to closed

Duplicate of #483.

Note: See TracTickets for help on using tickets.