-
Notifications
You must be signed in to change notification settings - Fork 4
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
Periodic deletion of Bulkrax /imports directory #2091
Comments
Questions:
|
/tmp is local. |
Yes, that is fine, but will that impact @jcrompton42 's file copy process to move files from EFS to /imports for Bulkrax? See #1985 |
It would just need to be updated, I think/hope. |
What @bwatson78 said, when the /imports location changes, can someone make me a ticket to update that? |
@jcrompton42 Yup, I will. |
Notes:
|
@rotated8 Knowing all of the info above, should I move forward with bringing both to |
@bwatson78 tested work in Curate v2.7.0 by running an export from test and a manually uploaded zip file import into arch. Import worked fine. Here's the path that was generated: |
@bwatson78 related to the above comment, when I exported from test I noticed the CSV had a couple of those extraneous multi-valued field columns again for abstract and publisher. |
@bwatson78 @jcrompton42 do we need another ticket related to updating the EFS to Curate file copy job? (#1985) |
I updated the file copy job so we should be good on that. |
Notes from Slack discussion 10/4/23: this is implemented in prod, but each release has its own tmp/imports folder so as we do new releases we leave some stuff hanging out in imports. This means that each time we deploy to prod, there's a separate version with its own /tmp directory. Keeping this open until we determine next steps, which will be a separate ticket. |
In order to prevent Curate from running out of disk space (1/18/23 occurrence), we need to expand our deletion/cleanup jobs to periodically to clean the /imports directory where we upload files to be used for Bulkrax ingests.
To investigate:
We currently have an AWX job that clears out the /tmp directory:
Recommended frequency: same as the above job
The text was updated successfully, but these errors were encountered: