Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto-cleaning of Midway logs #124

Open
pdeperio opened this issue Oct 3, 2017 · 2 comments
Open

Auto-cleaning of Midway logs #124

pdeperio opened this issue Oct 3, 2017 · 2 comments
Assignees

Comments

@pdeperio
Copy link
Contributor

pdeperio commented Oct 3, 2017

We regularly reach file quota on /project, likely due to continuous production of job logs. I suggest to write a simple function in the job script that removes logs older than some threshold.

@lucrlom
Copy link
Contributor

lucrlom commented Oct 19, 2017

Ciao Patrick

There are two options maybe:

  1. don't touch the directories of the present pax version, but delete together with the PurgeProcessed also the old log directories. We should find a way to identify automatically the directory where cax put the log, maybe in the config file.

  2. crate check in the bash script on the number of log files present in the $JOB_WORKING_DIR. If they are more than 10 can be deleted. But anyway when we purge the processed file we will remove also the logs.

I will try to implement the first on before

@pdeperio
Copy link
Contributor Author

Ciao Francesco,

  1. Right now, the path is hardcoded and built here. I guess you can hardcode in PurgeProcessed too, since we don't expect this to change often.

  2. Since we don't frequently run PurgeProcessed, this would be preferable for continuously cleaning. As you mentioned, you can add a check here.

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants