Change ETLv2 file locking to use flock #167
Merged
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.
Change ETLv2 file locking to use flock
Description
The current ETLv2 file locking uses a pid in the lockfile to determine if a process is currently running and using the lockfile. This causes a problem for processes using moderate amounts of memory because PHP hits the script memory limit when attempting to fork/exec to run the
ps
command. This PR changes the behavior to useflock()
instead.Motivation and Context
PHP script out of memory errors.
Tests performed
Tested running an ETL pipeline
Types of changes
Checklist: