Open
Conversation
…in data file names and the closing of an existing open file so that the timestamp in the filename and the timestamp in the creation_timestamp HDF5 file Attribute are created more closely in time, and therefore are more likely to agree. This is in HDF5DataStore::open_file_if_needed().
…eation_timestamp_consistency
…eation_timestamp_consistency
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
From the commit message: Reordered the creation of a unique, timestamp-based substring to put in data file names and the closing of an existing open file so that the timestamp in the filename and the timestamp in the creation_timestamp HDF5 file Attribute are created more closely in time, and therefore are more likely to agree. This is in HDF5DataStore::open_file_if_needed().
Description
While running integtests on np04-srv-029, I noticed that I would occasionally see complaints about a mismatch between the timestamp that was part of the raw data filename and the creation-timestamp that is stored in an HDF5 Attribute inside the file. Most of the time, these two timestamps agree quite well. The situation that seemed to trigger the problem was writing the output files to a (probably slow) NFS-mounted disk instead of a (much faster) locally-mounted disk.
When I looked into the problem, I saw that the timestamp that goes into the filename for raw data file N+1 was being created before file N was closed. And, a delay in the closing of file N could cause the timestamp for file N+1 to become a few seconds stale.
The fix was to reorder the code, and that is what is in this PR.
The suggested steps for reproducing the problem are the following, and they will work most reliably if they are run on np04-srv-029.
Type of change
Testing checklist
dunedaq_integtest_bundle.sh)Further checks