GHI-229 - Sidekiq service memory usage limits #243
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.
Description of your patch
Declared MemorySwapMax and MemoryHigh limit for the sidekiq service. Added environment variable "EY_SIDEKIQ_WORKER_THRESHOLD_MEMORY_MB" for MemoryHigh limit of the sidekiq service. It is by default 80% of the MemoryMax. Related issue #229
Recommended Release Notes
Environment variable for threshold memory limit of sidekiq service.
Estimated Risk
Low ( After these changes are applied all sidekiq workers will have these limits applied)
Components involved
All clients who use sidekiq in their application
Dependencies
ey-sidekiq
Description of testing done
Create a v7 rails environment with sidekiq
Add environment variables to enable sidekiq in the environment
Run command "systemctl status [sidekiq worker name]" on the instance that sidekiq is running.
Look at the memory row in the output, Max, SwapMax and High limits should be declared.