Changes between Version 13 and Version 14 of FileDeleter


Ignore:
Timestamp:
Feb 23, 2012, 7:33:55 PM (13 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • FileDeleter

    v13 v14  
     1[[PageOutline]]
    12= Server-side file deletion =
    2 Files are deleted from the data server's upload and download directories by the '''file_deleter''' daemon.
     3
     4Files are deleted from the data server's upload and download directories by two
     5programs:
     6 * The '''file_deleter''' daemon, which deletes input and output files
     7   as jobs are completed.
     8 * The '''antique file deleter''', which deletes files that have
     9   "fallen through the cracks".
     10
     11== The File Deleter
     12
    313Typically you don't need to customize this.
    414The default file deletion policy is:
    … …  
    818 * A result's output files are deleted after the workunit is assimilated.
    919   The canonical result is handled differently,
    10    since its output files may be needed to validate results that are reported after assimilation;
    11    hence its files are deleted only when all results are over, and all successful results have been validated.
    12  * Periodically remove 'antiques': output files that are older than the oldest WU in the database.
    13    These files are created when BOINC clients return after the corresponding WU has been deleted from the database.
     20   since its output files may be needed to validate results
     21   that are reported after assimilation;
     22   hence its files are deleted only when all results are over,
     23   and all successful results have been validated.
    1424
    1525Command-line options:
    … …  
    1929 --one_pass:: exit after one pass through DB
    2030 --dont_retry_errors:: Don't retry file deletions that failed previously.
    21  --dont_delete_antiques:: Don't delete antiques
    22  --delete_antiques_interval S:: change the interval between delete antique passes (S in seconds, defaults to 24h)
    23  --delete_antiques_limit N:: change the maximum number of files deleted in one delete antique pass (defaults to 50000)
    2431 --preserve_wu_files::  Update the DB, but don't delete input files
    2532 --preserve_result_files:: Update the DB, but don't delete output files
    … …  
    3441 --app S:: only process workunits of app with name S
    3542
    36 If the web-server account on your system is not 'apache',
    37 add a {{{<httpd_user>}}} element to your [ProjectOptions#dirs config.xml] file.
    38 Otherwise antique deletion won't work.
    39 
    4043In some cases you may not want files to be deleted. There are three ways to accomplish this:
    4144
    … …  
    4548 * Include nodelete in the workunit name.
    4649
    47 The antique files are deleted by using a Unix 'find' command to locate files that are older than the oldest workunit.
    48 The find command will work on NFS mounted file systems, and will ignore .nfs stale file markers.
     50== The Antique File Deleter ==
     51
     52Runs as a periodic task.
     53Removes 'antiques': output files that are older
     54than the oldest WU in the database.
     55These files are created when BOINC clients
     56return after the corresponding WU has been deleted from the database.
     57
     58The antique files are deleted by using a Unix 'find' command to locate files
     59that are older than the oldest workunit.
     60The find command will work on NFS mounted file systems,
     61and will ignore .nfs stale file markers.
    4962The output of find is limited by a 'head' to 50000 files by default.
     63
     64If the web-server account on your system is not 'apache',
     65add a {{{<httpd_user>}}} element to your [ProjectOptions#dirs config.xml] file.
     66Otherwise antique deletion won't work.
     67