A <sticky/> file is used in cases there the same file is used for many different tasks, but it's not part of the application. The purpose of being <sticky/> is so the file won't be deleted even no current task on client uses the file.

<sticky/> files is only deleted if asked to do so by project, or by detaching from project. Just resetting the project, or manually deleting files from the project-directory won't work, any <sticky/> file that's missing on client-start will be re-downloaded.

WCG have choosen to mark the large file-download for CEP2 as <sticky/>, even if it's part of the beta, and for this reason the file will be kept on client.


As for the 10 GB-limit, each CEP2-task will routinely use 0.5 GB, but disk-usage can increase to atleast 0.75 GB during a task. If you've got a computer with many cpu-cores, and you're running mostly CEP2, there's a chance you'll hit this limit. This is especially true if one or more of the tasks suddenly starts running in high priority, since in this instances this will effectively double the disk-requirements.

The easiest method this is to increase the disk-limit, except if you're out of disk-space.