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

Automatically clean out data/txn files after failures #3523

Open
vvolkl opened this issue Mar 1, 2024 · 1 comment
Open

Automatically clean out data/txn files after failures #3523

vvolkl opened this issue Mar 1, 2024 · 1 comment
Assignees
Milestone

Comments

@vvolkl
Copy link
Contributor

vvolkl commented Mar 1, 2024

Originally https://its.cern.ch/jira/browse/CVM-1462

For a long time the StratumOnes twiki has recommended that stratum 1s clean out old files from the /srv/cvmfs//data/txn directories, but I just learned that release manager machines can suffer the same problems of old files accumulating there after failed publish operations. I think cvmfs_swissknife or cvmfs_server could do a better job of cleaning those out after any type of failure, on both stratum 1s and release managers. There used to be a concern of one operation interfering with another, but now we have locks and if the cleanup is done before the lock is released there should be no danger of that.

@vvolkl vvolkl added this to the 2.12 milestone Mar 1, 2024
@vvolkl vvolkl self-assigned this Mar 1, 2024
@DrDaveD
Copy link
Contributor

DrDaveD commented Mar 1, 2024

Are you sure that the issue was on a release manager? The report that prompted this issue was in this forum thread. Maybe it is only gateways. Release managers themselves don't have the txn directories as far as I can see.

For reference, here's the instructions on the StratumOnes twiki and here's the instructions in the OSG stratum1 instructions. It should probably at least be in the cvmfs readthedocs stratum 1 maintence section.

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

2 participants