[bugfix] Introduce optional file locking for appending to perflogs #3523
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.
This PR introduces two new configuration variables (
locking_enable
andlocking_file_mode
) for thefilelog
handler. Setting this will cause thefilelog
handler to use file locking when appending to the perflog files.This PR also introduces the following improvements:
osext.flock()
to handle the creation of the lock file for the different Python versions; this function is now used also for the DB.true
andfalse
in the configuration reference to be consistent with the use ofNone
instead of the JSON'snull
.Closes #3521.