sidekiq_process_killer 0.3.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.gitignore +12 -0
- data/.rspec +2 -0
- data/.travis.yml +8 -0
- data/CODE_OF_CONDUCT.md +74 -0
- data/Gemfile +6 -0
- data/LICENSE.txt +21 -0
- data/README.md +79 -0
- data/Rakefile +6 -0
- data/bin/console +14 -0
- data/bin/setup +6 -0
- data/lib/sidekiq_process_killer/middleware.rb +87 -0
- data/lib/sidekiq_process_killer/version.rb +3 -0
- data/lib/sidekiq_process_killer.rb +20 -0
- data/sidekiq_process_killer.gemspec +28 -0
- metadata +130 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA1:
|
3
|
+
metadata.gz: 238e5c56b973d15c48532c8ae97ed69e618ef2df
|
4
|
+
data.tar.gz: 36bbaea2b7b882acc74eb0cda54ddea5206c5bdf
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: f07e2f56f74e42bcced965174a4142643de77b3a90c4ab453b9bc1930e4ef921fe422ea7c2b7d8ed93648515acae994ab3a04f09ae2ea8e233b4df06724dd8e4
|
7
|
+
data.tar.gz: 39ed73ecfcf7d7b9a3fda70dfcc428db2e8eabb758fd33c27b582df587479f360e6b88e82aae1fd82ba62834d175bdde00131c3228a435a1c773a4649f369c67
|
data/.gitignore
ADDED
data/.rspec
ADDED
data/.travis.yml
ADDED
data/CODE_OF_CONDUCT.md
ADDED
@@ -0,0 +1,74 @@
|
|
1
|
+
# Contributor Covenant Code of Conduct
|
2
|
+
|
3
|
+
## Our Pledge
|
4
|
+
|
5
|
+
In the interest of fostering an open and welcoming environment, we as
|
6
|
+
contributors and maintainers pledge to making participation in our project and
|
7
|
+
our community a harassment-free experience for everyone, regardless of age, body
|
8
|
+
size, disability, ethnicity, gender identity and expression, level of experience,
|
9
|
+
nationality, personal appearance, race, religion, or sexual identity and
|
10
|
+
orientation.
|
11
|
+
|
12
|
+
## Our Standards
|
13
|
+
|
14
|
+
Examples of behavior that contributes to creating a positive environment
|
15
|
+
include:
|
16
|
+
|
17
|
+
* Using welcoming and inclusive language
|
18
|
+
* Being respectful of differing viewpoints and experiences
|
19
|
+
* Gracefully accepting constructive criticism
|
20
|
+
* Focusing on what is best for the community
|
21
|
+
* Showing empathy towards other community members
|
22
|
+
|
23
|
+
Examples of unacceptable behavior by participants include:
|
24
|
+
|
25
|
+
* The use of sexualized language or imagery and unwelcome sexual attention or
|
26
|
+
advances
|
27
|
+
* Trolling, insulting/derogatory comments, and personal or political attacks
|
28
|
+
* Public or private harassment
|
29
|
+
* Publishing others' private information, such as a physical or electronic
|
30
|
+
address, without explicit permission
|
31
|
+
* Other conduct which could reasonably be considered inappropriate in a
|
32
|
+
professional setting
|
33
|
+
|
34
|
+
## Our Responsibilities
|
35
|
+
|
36
|
+
Project maintainers are responsible for clarifying the standards of acceptable
|
37
|
+
behavior and are expected to take appropriate and fair corrective action in
|
38
|
+
response to any instances of unacceptable behavior.
|
39
|
+
|
40
|
+
Project maintainers have the right and responsibility to remove, edit, or
|
41
|
+
reject comments, commits, code, wiki edits, issues, and other contributions
|
42
|
+
that are not aligned to this Code of Conduct, or to ban temporarily or
|
43
|
+
permanently any contributor for other behaviors that they deem inappropriate,
|
44
|
+
threatening, offensive, or harmful.
|
45
|
+
|
46
|
+
## Scope
|
47
|
+
|
48
|
+
This Code of Conduct applies both within project spaces and in public spaces
|
49
|
+
when an individual is representing the project or its community. Examples of
|
50
|
+
representing a project or community include using an official project e-mail
|
51
|
+
address, posting via an official social media account, or acting as an appointed
|
52
|
+
representative at an online or offline event. Representation of a project may be
|
53
|
+
further defined and clarified by project maintainers.
|
54
|
+
|
55
|
+
## Enforcement
|
56
|
+
|
57
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
58
|
+
reported by contacting the project team at dev@shayon.me. All
|
59
|
+
complaints will be reviewed and investigated and will result in a response that
|
60
|
+
is deemed necessary and appropriate to the circumstances. The project team is
|
61
|
+
obligated to maintain confidentiality with regard to the reporter of an incident.
|
62
|
+
Further details of specific enforcement policies may be posted separately.
|
63
|
+
|
64
|
+
Project maintainers who do not follow or enforce the Code of Conduct in good
|
65
|
+
faith may face temporary or permanent repercussions as determined by other
|
66
|
+
members of the project's leadership.
|
67
|
+
|
68
|
+
## Attribution
|
69
|
+
|
70
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
71
|
+
available at [http://contributor-covenant.org/version/1/4][version]
|
72
|
+
|
73
|
+
[homepage]: http://contributor-covenant.org
|
74
|
+
[version]: http://contributor-covenant.org/version/1/4/
|
data/Gemfile
ADDED
data/LICENSE.txt
ADDED
@@ -0,0 +1,21 @@
|
|
1
|
+
The MIT License (MIT)
|
2
|
+
|
3
|
+
Copyright (c) 2017 Shayon Mukherjee
|
4
|
+
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
7
|
+
in the Software without restriction, including without limitation the rights
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
10
|
+
furnished to do so, subject to the following conditions:
|
11
|
+
|
12
|
+
The above copyright notice and this permission notice shall be included in
|
13
|
+
all copies or substantial portions of the Software.
|
14
|
+
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
21
|
+
THE SOFTWARE.
|
data/README.md
ADDED
@@ -0,0 +1,79 @@
|
|
1
|
+
# SidekiqProcessKiller
|
2
|
+
|
3
|
+
[![Build Status](https://travis-ci.org/shayonj/sidekiq_process_killer.svg?branch=master)](https://travis-ci.org/shayonj/sidekiq_process_killer)
|
4
|
+
|
5
|
+
When you have memory leaks or "bloats" in your ruby application, identifying and fixing them can at times be a nightmare. Instead, an _"acceptable"_ mitigation is to re-spin the workers. Its a common technique that can be found in [Puma Worker Killer](https://github.com/schneems/puma_worker_killer) or [Unicorn Worker Killer](https://github.com/kzk/unicorn-worker-killer). Though, its neater and good practice to find and fix your leaks.
|
6
|
+
|
7
|
+
SidekiqProcessKiller plugs into Sidekiq's middleware and kills a process if its processing beyond the supplied [RSS](https://en.wikipedia.org/wiki/Resident_set_size) threshold. Since this plugs into the middleware, the check is performed after each job.
|
8
|
+
|
9
|
+
## Installation
|
10
|
+
|
11
|
+
**While in testing period, this is not published to a public server, yet. Until then:**
|
12
|
+
|
13
|
+
Add the following to your Gemfile
|
14
|
+
|
15
|
+
```ruby
|
16
|
+
gem "sidekiq_process_killer", git: "git://github.com/shayonj/sidekiq_process_killer.git"
|
17
|
+
```
|
18
|
+
|
19
|
+
## Usage
|
20
|
+
|
21
|
+
### Configuration
|
22
|
+
|
23
|
+
The default configurations are:
|
24
|
+
|
25
|
+
```ruby
|
26
|
+
memory_threshold: 250.0 # mb
|
27
|
+
shutdown_wait_timeout: 25 # seconds
|
28
|
+
shutdown_signal: "SIGKILL"
|
29
|
+
silent_mode: false
|
30
|
+
statsd_klass: nil
|
31
|
+
```
|
32
|
+
|
33
|
+
- `silent_mode`: When set to `true`, it will mean that no signals for terminate or otherwise will be sent. This is helpful if you are planning to launch this, but want to first do a dry run.
|
34
|
+
- `memory_threshold`: This is the threshold, which, when, breached, the respective Sidekiq worker will be instructed for termination (via `TERM` signal, which sidekiq gracefully exits).
|
35
|
+
- `shutdown_signal`: Signal for force shutdown/kill/quit.
|
36
|
+
- `shutdown_wait_timeout`: If, for some reason, the process takes more than the timeout defined in `shutdown_wait_timeout`, to die, the process will be forced terminated using the signal set in `shutdown_signal`.
|
37
|
+
- `statsd_klass`: This is your custom statsd class object which responds to an `increment` function. If present, then it will send custom metrics about the worker process that is being terminated and its respective RSS.
|
38
|
+
- The `increment` is called with a single argument of type `Hash` which contains, `metric_name`, `worker_name` and `current_memory_usage`. The implementation of this may not be very flexible, its expected that your custom class reads the passed in information and appropriately send to your statsd agent. PRs/patches welcome to extend this functionality :).
|
39
|
+
|
40
|
+
### Updating default configuration:
|
41
|
+
|
42
|
+
```ruby
|
43
|
+
class CustomMetric
|
44
|
+
...
|
45
|
+
|
46
|
+
def increment(params)
|
47
|
+
StatsD.count(
|
48
|
+
params[:metric_name],
|
49
|
+
tags: {
|
50
|
+
worker_name: params[:worker_name]
|
51
|
+
}
|
52
|
+
)
|
53
|
+
end
|
54
|
+
|
55
|
+
...
|
56
|
+
end
|
57
|
+
|
58
|
+
SidekiqProcessKiller.config do |con|
|
59
|
+
con.memory_threshold = 1024.0
|
60
|
+
con.shutdown_wait_timeout = 60
|
61
|
+
con.shutdown_signal = "SIGUSR2"
|
62
|
+
con.silent_mode = false
|
63
|
+
con.statsd_klass = CustomMetric.new # your custom statsd class object
|
64
|
+
end
|
65
|
+
```
|
66
|
+
|
67
|
+
### Turn on SidekiqProcessKiller
|
68
|
+
|
69
|
+
Just plugin the Middleware
|
70
|
+
|
71
|
+
```ruby
|
72
|
+
Sidekiq.configure_server do |config|
|
73
|
+
config.server_middleware do |chain|
|
74
|
+
chain.add SidekiqProcessKiller::Middleware
|
75
|
+
end
|
76
|
+
end
|
77
|
+
```
|
78
|
+
|
79
|
+
The class tries to log as much as possible, as best as possible.
|
data/Rakefile
ADDED
data/bin/console
ADDED
@@ -0,0 +1,14 @@
|
|
1
|
+
#!/usr/bin/env ruby
|
2
|
+
|
3
|
+
require "bundler/setup"
|
4
|
+
require "sidekiq_process_killer"
|
5
|
+
|
6
|
+
# You can add fixtures and/or initialization code here to make experimenting
|
7
|
+
# with your gem easier. You can also use a different console, if you like.
|
8
|
+
|
9
|
+
# (If you use this, don't forget to add pry to your Gemfile!)
|
10
|
+
# require "pry"
|
11
|
+
# Pry.start
|
12
|
+
|
13
|
+
require "irb"
|
14
|
+
IRB.start(__FILE__)
|
data/bin/setup
ADDED
@@ -0,0 +1,87 @@
|
|
1
|
+
module SidekiqProcessKiller
|
2
|
+
class Middleware
|
3
|
+
LOG_PREFIX = self.name
|
4
|
+
METRIC_PREFIX = "sidekiq_process_killer".freeze
|
5
|
+
|
6
|
+
attr_accessor :pid, :worker, :jid, :queue, :memory
|
7
|
+
|
8
|
+
def call(worker, job, queue)
|
9
|
+
@pid = ::Process.pid
|
10
|
+
@worker = worker.class
|
11
|
+
@queue = queue
|
12
|
+
@memory = process_memory.mb
|
13
|
+
@jid = job['jid']
|
14
|
+
|
15
|
+
yield
|
16
|
+
|
17
|
+
memory_threshold = SidekiqProcessKiller.memory_threshold
|
18
|
+
return if memory_threshold > memory
|
19
|
+
|
20
|
+
log_warn("Breached RSS threshold at #{memory_threshold}. Sending TERM Signal.")
|
21
|
+
|
22
|
+
send_signal("SIGTERM", pid)
|
23
|
+
sleep(SidekiqProcessKiller.shutdown_wait_timeout)
|
24
|
+
|
25
|
+
shutdown_signal = SidekiqProcessKiller.shutdown_signal
|
26
|
+
|
27
|
+
begin
|
28
|
+
::Process.getpgid(pid)
|
29
|
+
log_warn("Forcefully killing process with #{shutdown_signal}.")
|
30
|
+
|
31
|
+
increment_statsd({
|
32
|
+
metric_name: "process.killed.forcefully",
|
33
|
+
worker_name: worker.class,
|
34
|
+
current_memory_usage: memory
|
35
|
+
})
|
36
|
+
|
37
|
+
send_signal(shutdown_signal, pid)
|
38
|
+
rescue Errno::ESRCH
|
39
|
+
log_warn("Process killed successfully.")
|
40
|
+
|
41
|
+
increment_statsd({
|
42
|
+
metric_name: "process.killed.successfully",
|
43
|
+
worker_name: worker.class,
|
44
|
+
current_memory_usage: memory
|
45
|
+
})
|
46
|
+
end
|
47
|
+
end
|
48
|
+
|
49
|
+
private def process_memory
|
50
|
+
@memory ||= GetProcessMem.new
|
51
|
+
end
|
52
|
+
|
53
|
+
private def humanized_attributes
|
54
|
+
instance_variables.map do |var|
|
55
|
+
key = var.to_s.gsub("@", "").capitalize
|
56
|
+
value = instance_variable_get(var)
|
57
|
+
"#{key}: #{value}"
|
58
|
+
end.join(", ")
|
59
|
+
end
|
60
|
+
|
61
|
+
private def silent_mode_msg
|
62
|
+
SidekiqProcessKiller.silent_mode ? " [SILENT]" : ""
|
63
|
+
end
|
64
|
+
|
65
|
+
private def log_warn(msg)
|
66
|
+
Sidekiq.logger.warn("[#{LOG_PREFIX}]#{silent_mode_msg} #{msg} #{humanized_attributes}")
|
67
|
+
end
|
68
|
+
|
69
|
+
private def log_info(msg)
|
70
|
+
Sidekiq.logger.info("[#{LOG_PREFIX}]#{silent_mode_msg} #{msg} #{humanized_attributes}")
|
71
|
+
end
|
72
|
+
|
73
|
+
private def send_signal(name, pid)
|
74
|
+
return if SidekiqProcessKiller.silent_mode
|
75
|
+
|
76
|
+
::Process.kill(name, pid)
|
77
|
+
end
|
78
|
+
|
79
|
+
private def increment_statsd(params)
|
80
|
+
statsd_klass = SidekiqProcessKiller.statsd_klass
|
81
|
+
return unless statsd_klass.respond_to?(:increment)
|
82
|
+
|
83
|
+
params[:metric_name] = "#{METRIC_PREFIX}.#{params[:metric_name]}"
|
84
|
+
statsd_klass.increment(params)
|
85
|
+
end
|
86
|
+
end
|
87
|
+
end
|
@@ -0,0 +1,20 @@
|
|
1
|
+
module SidekiqProcessKiller
|
2
|
+
extend self
|
3
|
+
|
4
|
+
attr_accessor :memory_threshold, :shutdown_wait_timeout, :shutdown_signal, :silent_mode, :statsd_klass
|
5
|
+
|
6
|
+
self.memory_threshold = 250.0 # mb
|
7
|
+
self.shutdown_wait_timeout = 25 # seconds
|
8
|
+
self.shutdown_signal = "SIGKILL"
|
9
|
+
self.silent_mode = false
|
10
|
+
self.statsd_klass = nil
|
11
|
+
|
12
|
+
def config
|
13
|
+
yield self
|
14
|
+
end
|
15
|
+
end
|
16
|
+
|
17
|
+
require "get_process_mem"
|
18
|
+
require "sidekiq"
|
19
|
+
require "sidekiq_process_killer/version"
|
20
|
+
require "sidekiq_process_killer/middleware"
|
@@ -0,0 +1,28 @@
|
|
1
|
+
# coding: utf-8
|
2
|
+
lib = File.expand_path("../lib", __FILE__)
|
3
|
+
$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
|
4
|
+
require "sidekiq_process_killer/version"
|
5
|
+
|
6
|
+
Gem::Specification.new do |spec|
|
7
|
+
spec.name = "sidekiq_process_killer"
|
8
|
+
spec.version = SidekiqProcessKiller::VERSION
|
9
|
+
spec.authors = ["Shayon Mukherjee"]
|
10
|
+
spec.email = ["dev@shayon.me"]
|
11
|
+
|
12
|
+
spec.summary = "Simple process killer for sidekiq to avoid memory leaks and/or bloats"
|
13
|
+
spec.description = "SidekiqProcessKiller plugs into Sidekiq's middleware and kills a process if its processing beyond the supplied RSS threshold. Since, this plugs into the middleware the check is performed after each job."
|
14
|
+
spec.homepage = "https://github.com/shayonj/sidekiq_process_killer"
|
15
|
+
spec.license = "MIT"
|
16
|
+
|
17
|
+
spec.files = `git ls-files -z`.split("\x0").reject do |f|
|
18
|
+
f.match(%r{^(test|spec|features)/})
|
19
|
+
end
|
20
|
+
spec.require_paths = ["lib"]
|
21
|
+
|
22
|
+
spec.add_development_dependency "bundler", "~> 1.15"
|
23
|
+
spec.add_development_dependency "rake", "~> 10.0"
|
24
|
+
spec.add_development_dependency "rspec", "~> 3.0"
|
25
|
+
|
26
|
+
spec.add_dependency "get_process_mem"
|
27
|
+
spec.add_dependency "sidekiq"
|
28
|
+
end
|
metadata
ADDED
@@ -0,0 +1,130 @@
|
|
1
|
+
--- !ruby/object:Gem::Specification
|
2
|
+
name: sidekiq_process_killer
|
3
|
+
version: !ruby/object:Gem::Version
|
4
|
+
version: 0.3.0
|
5
|
+
platform: ruby
|
6
|
+
authors:
|
7
|
+
- Shayon Mukherjee
|
8
|
+
autorequire:
|
9
|
+
bindir: bin
|
10
|
+
cert_chain: []
|
11
|
+
date: 2017-10-30 00:00:00.000000000 Z
|
12
|
+
dependencies:
|
13
|
+
- !ruby/object:Gem::Dependency
|
14
|
+
name: bundler
|
15
|
+
requirement: !ruby/object:Gem::Requirement
|
16
|
+
requirements:
|
17
|
+
- - "~>"
|
18
|
+
- !ruby/object:Gem::Version
|
19
|
+
version: '1.15'
|
20
|
+
type: :development
|
21
|
+
prerelease: false
|
22
|
+
version_requirements: !ruby/object:Gem::Requirement
|
23
|
+
requirements:
|
24
|
+
- - "~>"
|
25
|
+
- !ruby/object:Gem::Version
|
26
|
+
version: '1.15'
|
27
|
+
- !ruby/object:Gem::Dependency
|
28
|
+
name: rake
|
29
|
+
requirement: !ruby/object:Gem::Requirement
|
30
|
+
requirements:
|
31
|
+
- - "~>"
|
32
|
+
- !ruby/object:Gem::Version
|
33
|
+
version: '10.0'
|
34
|
+
type: :development
|
35
|
+
prerelease: false
|
36
|
+
version_requirements: !ruby/object:Gem::Requirement
|
37
|
+
requirements:
|
38
|
+
- - "~>"
|
39
|
+
- !ruby/object:Gem::Version
|
40
|
+
version: '10.0'
|
41
|
+
- !ruby/object:Gem::Dependency
|
42
|
+
name: rspec
|
43
|
+
requirement: !ruby/object:Gem::Requirement
|
44
|
+
requirements:
|
45
|
+
- - "~>"
|
46
|
+
- !ruby/object:Gem::Version
|
47
|
+
version: '3.0'
|
48
|
+
type: :development
|
49
|
+
prerelease: false
|
50
|
+
version_requirements: !ruby/object:Gem::Requirement
|
51
|
+
requirements:
|
52
|
+
- - "~>"
|
53
|
+
- !ruby/object:Gem::Version
|
54
|
+
version: '3.0'
|
55
|
+
- !ruby/object:Gem::Dependency
|
56
|
+
name: get_process_mem
|
57
|
+
requirement: !ruby/object:Gem::Requirement
|
58
|
+
requirements:
|
59
|
+
- - ">="
|
60
|
+
- !ruby/object:Gem::Version
|
61
|
+
version: '0'
|
62
|
+
type: :runtime
|
63
|
+
prerelease: false
|
64
|
+
version_requirements: !ruby/object:Gem::Requirement
|
65
|
+
requirements:
|
66
|
+
- - ">="
|
67
|
+
- !ruby/object:Gem::Version
|
68
|
+
version: '0'
|
69
|
+
- !ruby/object:Gem::Dependency
|
70
|
+
name: sidekiq
|
71
|
+
requirement: !ruby/object:Gem::Requirement
|
72
|
+
requirements:
|
73
|
+
- - ">="
|
74
|
+
- !ruby/object:Gem::Version
|
75
|
+
version: '0'
|
76
|
+
type: :runtime
|
77
|
+
prerelease: false
|
78
|
+
version_requirements: !ruby/object:Gem::Requirement
|
79
|
+
requirements:
|
80
|
+
- - ">="
|
81
|
+
- !ruby/object:Gem::Version
|
82
|
+
version: '0'
|
83
|
+
description: SidekiqProcessKiller plugs into Sidekiq's middleware and kills a process
|
84
|
+
if its processing beyond the supplied RSS threshold. Since, this plugs into the
|
85
|
+
middleware the check is performed after each job.
|
86
|
+
email:
|
87
|
+
- dev@shayon.me
|
88
|
+
executables: []
|
89
|
+
extensions: []
|
90
|
+
extra_rdoc_files: []
|
91
|
+
files:
|
92
|
+
- ".gitignore"
|
93
|
+
- ".rspec"
|
94
|
+
- ".travis.yml"
|
95
|
+
- CODE_OF_CONDUCT.md
|
96
|
+
- Gemfile
|
97
|
+
- LICENSE.txt
|
98
|
+
- README.md
|
99
|
+
- Rakefile
|
100
|
+
- bin/console
|
101
|
+
- bin/setup
|
102
|
+
- lib/sidekiq_process_killer.rb
|
103
|
+
- lib/sidekiq_process_killer/middleware.rb
|
104
|
+
- lib/sidekiq_process_killer/version.rb
|
105
|
+
- sidekiq_process_killer.gemspec
|
106
|
+
homepage: https://github.com/shayonj/sidekiq_process_killer
|
107
|
+
licenses:
|
108
|
+
- MIT
|
109
|
+
metadata: {}
|
110
|
+
post_install_message:
|
111
|
+
rdoc_options: []
|
112
|
+
require_paths:
|
113
|
+
- lib
|
114
|
+
required_ruby_version: !ruby/object:Gem::Requirement
|
115
|
+
requirements:
|
116
|
+
- - ">="
|
117
|
+
- !ruby/object:Gem::Version
|
118
|
+
version: '0'
|
119
|
+
required_rubygems_version: !ruby/object:Gem::Requirement
|
120
|
+
requirements:
|
121
|
+
- - ">="
|
122
|
+
- !ruby/object:Gem::Version
|
123
|
+
version: '0'
|
124
|
+
requirements: []
|
125
|
+
rubyforge_project:
|
126
|
+
rubygems_version: 2.6.14
|
127
|
+
signing_key:
|
128
|
+
specification_version: 4
|
129
|
+
summary: Simple process killer for sidekiq to avoid memory leaks and/or bloats
|
130
|
+
test_files: []
|