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

Add "verify store" feature #14

Open
pkgw opened this issue Jun 1, 2016 · 2 comments
Open

Add "verify store" feature #14

pkgw opened this issue Jun 1, 2016 · 2 comments

Comments

@pkgw
Copy link
Contributor

pkgw commented Jun 1, 2016

I expect that we're going to want to be able to have the Librarian look through a store and validate its contents: that all of the FileInstances that it knows about are actually there, and (perhaps) that there aren't any files there that are not known FileInstances.

You could also imagine a feature to verify the MD5 sums of file instances, but that will be insanely CPU-heavy to calculate — should only be done for single instances at a time. If we were feeling fancy, we could validate the MD5 subs of flat files as we streamed that out to clients via the /stream/ HTTP handlers, although this won't work with directories (i.e. UV data) without some serious deep magic.

@pkgw
Copy link
Contributor Author

pkgw commented Dec 20, 2016

Also, you could imagine teaching the Librarian to poke around attempting to verify files when the system load is low. Most Librarian usage is very bursty, so it's spending a lot of time sitting around doing nothing. Thus far, however, this has not felt like an urgent feature, though.

@pkgw
Copy link
Contributor Author

pkgw commented Jun 17, 2017

From my efforts to quasi-sync data from qmaster to NRAO, it looks as if we have some examples of the Librarian and the disk getting out of sync. For instance, file zen.2457471.19477.yx.uvc.autos.png is supposed to have an instance on pot1, but it doesn't.

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

No branches or pull requests

1 participant