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

Support machines that have no cache space (data can only be written to file system) #54

Closed
adammoody opened this issue Jul 20, 2017 · 2 comments · Fixed by #166
Closed
Assignees
Milestone

Comments

@adammoody
Copy link
Contributor

For systems that have no SSDs available for cache or sufficient free memory for ramdisk, let's write checkpoints directly to the file system. Let's assume we can still write filemap info to ramdisk, though (it's very small).

Route_file will need to do mkdir() calls here, probably for each component below the prefix directory.

We'll need to track file names and write SCR metadata that we'd normally get after a flush.

We need fetch to be aware of this, too.

The scavenge script will probably have to be modified, too.

@adammoody adammoody added this to the v1.2 milestone Jul 20, 2017
@adammoody adammoody self-assigned this Jul 20, 2017
@becker33
Copy link
Collaborator

Should this really be marked 1.2? I thought this was on a later time-scale.

@adammoody
Copy link
Contributor Author

It's not a hard requirement for v1.2. I listed it as a stretch goal hoping I'd find the time tol fit this in. It's looking more like v1.3 right now.

@becker33 becker33 removed this from the v1.2 milestone Aug 11, 2017
@adammoody adammoody added this to the v1.3 milestone Aug 11, 2017
@adammoody adammoody removed their assignment Jan 21, 2020
@rhaas80 rhaas80 self-assigned this Jan 29, 2020
@adammoody adammoody mentioned this issue May 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants