zombocom/puma_worker_killer

Issues

• memory calculations are "not useful"

  #106 opened 5 months ago by canoeberry
  2

• Please add support for rack >= 3

  #108 opened 5 months ago by lucaskanashiro
  1

• Restarts at a lower limit after enabling jemalloc

  #105 opened a year ago by JasonBarnabe
  1

• puma 5, rails s error

  #100 opened 3 years ago by huzhijia
  1

• Not seeing 'PumaWorkerKiller: Consuming XXX mb' stdout logging after SIGUSR1 signal to master pid

  #99 opened 3 years ago by dfuentes77
  4

• No restart of pumas with your instructions.

  #98 opened 3 years ago by rhtaylor
  1

• The memory reported doesn't match with the memory in Heroku metric

  #95 opened 4 years ago by imrubyist
  2

• Determine better ram default

  #68 opened 4 years ago by freeformz
  5

• Allow pre_term with enable_rolling_restart

  #83 opened 4 years ago by caljess599
  1

• Using RuboCop?

  #89 opened 4 years ago by utkarsh2102
  4

• Web worker not getting killed on Heroku

  #88 opened 4 years ago by kapso
  3

• workers being constantly booted

  #8 opened 5 years ago by markquezada
  18

• Error tracking

  #42 opened 5 years ago by pawel2105
  2

• NoMethodError: undefined method `reaper_status_logs=' for PumaWorkerKiller:Module

  #44 opened 5 years ago by vcardillo
  4

• Rolling restart uses pids that were killed instead of new pids

  #46 opened 5 years ago by nritholtz
  8

• Callback for tracking calculated memory usage per reap attempt

  #50 opened 5 years ago by tobypinder
  3

• Is there a way to specify a specific dyno that gets killed?

  #52 opened 5 years ago by mberman84
  1

• Can I run both enable_rolling_restart and start

  #53 opened 5 years ago by nitzanav
  2

• Unable to get it working with 3.12 / Rails 5.2

  #61 opened 5 years ago by oyeanuj
  4

• Cannot kill workers

  #64 opened 5 years ago by volkanunsal
  4

• Need more clarity on some of the configurations

  #67 opened 5 years ago by moustafasallam
  1

• AutoReap thread exits

  #17 opened 5 years ago by Ricardonacif
  1

• Seems not working on Puma 2.11.3

  #15 opened 5 years ago by larryzhao
  13

• Continued cycling/killing of puma workers (wrong ones?)

  #14 opened 5 years ago by travisp
  19

• Possible issue with leaving open database connections

  #13 opened 5 years ago by chadbailey59
  1

• Dont kill PumaWorkerKiller when calling largest_worker.term a second time

  #9 opened 5 years ago by Leooo
  5

• Significantly incorrect memory usage reported

  #6 opened 5 years ago by travisp
  24

• Seems to be not working when Puma is detached from the console

  #5 opened 5 years ago by mmonsta
  5

• Be more explicit about where to put PumaWorkerKiller.start

  #4 opened 5 years ago by ponny
  22

• Don't recommend puma_auto_tune?

  #3 opened 5 years ago by travisp
  2

• warning: conflicting chdir during another chdir block

  #79 opened 5 years ago by wellington1993
  3

• No PumaWorkerKiller logs when upgrading to Puma 4.1.0

  #76 opened 5 years ago by ernestojpg
  1

• [ruby] <defunct>

  #75 opened 5 years ago by wellington1993
  3

• is it proper to call ActiveRecord::Base.establish_connection when on_worker_boot

  #73 opened 6 years ago by wenbo
  2

• New puma v4.0.0 available

  #71 opened 6 years ago by ylecuyer
  0

• Puma Worker Killer の導入

  #59 opened 7 years ago by norifumi
  1

• Blank mb used displayed in logs

  #45 opened 8 years ago by vcardillo
  4

• Worker killer not starting on Heroku

  #43 opened 8 years ago by patrickberkeley
  4

• Just enable phased restarts

  #23 opened 9 years ago by lostboy
  8

• Implications for long-running requests

  #18 opened 9 years ago by julik
  4

• Where shall I start PumaWorkerKiller if I do not preload_app?

  #36 opened 9 years ago by larryzhao
  1

• "Detected 1 Thread(s) started in app boot" on puma 3.4.0

  #35 opened 9 years ago by oboxodo
  5

• JRuby fork not implemented issue

  #28 opened 9 years ago by treble37
  2

• worker.inspect generates extremely verbose logs

  #32 opened 9 years ago by swrobel
  3

• Rolling restarts seem extremely inconsistent

  #29 opened 9 years ago by swrobel
  6

• Logs shows consuming memory with master and workers

  #24 opened 9 years ago by anjain
  1

• Not able to restart Puma Server after using Puma Worker Killer

  #21 opened 9 years ago by achiinto
  5

• Add puma worker killer config into puma config file, rather than into initializers

  #19 opened 9 years ago by raymondmars
  0

• Killing workers with plenty of memory left

  #11 opened 10 years ago by timscott
  3

• Restarting main process?

  #10 opened 10 years ago by Leooo
  5