lock files shared between library and scripts #336
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are a number of files shared between the library and the run scripts, including
flush.scr
,halt.scr
,nodes.scr
,index.scr
and the summary and rank2file maps among others. While in most cases, the library is not trying to access those files the same time as the scripts, this PR adds read/write locks around shared files to help avoid NFS caching problems.If the library updates the flush file from a compute node and then stops, and then the job script reads the flush file from another node, it may see a stale copy due to NFS caching. The hope is that adding read/write locks will help mitigate those caching problems on some NFS implementations.