I have done something about this. I have written some code for tahoe to automatically schedule repair process. the basic idea like this: run a monitor service when tahoe client runs, detect file's health'state when downloading a file, if the file is unhealthy(the valid shares < a threshold number), then record this file, and at a scheduled time(maybe at midnight), run a repair service to make this file healthy... My problem is how to make a test to this? I think this way can save much resources consumed by a repair process. I know there are simulators in the source code folder of tahoe, but I donnot know how to use it to test this repair process. I want to know whether this way to repair files can provide a good way to save repair overhead compared with original way and keep a high availability at the same time.
2013-08-15 Regards, han zheng 发件人："tahoe-lafs" <[email protected]> 发送时间：2013-07-04 00:49 主题：Re: [tahoe-lafs] #643: Automatically schedule repair process (and backups?) 收件人： 抄送："tahoe-lafs-trac-stream"<[email protected]> #643: Automatically schedule repair process (and backups?) -------------------------+------------------------------------------------- Reporter: mmore | Owner: somebody Type: | Status: new enhancement | Milestone: eventually Priority: major | Version: 1.3.0 Component: | Keywords: repair availability preservation operational | usability scheduling tahoe-backup Resolution: | Launchpad Bug: | -------------------------+------------------------------------------------- Old description: > 1.have Tahoe an automatic repair, i.e. , the introducer monitor the > replicas numbers, for example if we have configuration of 10 /3 , so > introducer trigger repair process when the replicas became only 4 to keep > the file available? > 2. what are the threshold that triggers the repair process? New description: 1.have Tahoe an automatic repair, i.e. , the introducer monitor the replicas numbers, for example if we have configuration of 10 /3 , so introducer trigger repair process when the replicas became only 4 to keep the file available? 2. what are the threshold that triggers the repair process? -- Comment (by zhan0903): Is there some implementation about automatical repair? I found it is not convenient to repair only one file or directory every time you run the repair tool sometimes, you even donnot know which file should be repaired, so I think it will be good to make this tool run as a service and check files automatically based on some principles or algorithm actually, I would like to do something about that -- Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/643#comment:17> tahoe-lafs <https://tahoe-lafs.org> secure decentralized storage
_______________________________________________ tahoe-dev mailing list [email protected] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
