puma 3.7.1 → 4.1.0

Sign up to get free protection for your applications and to get access to all the features.

Potentially problematic release.


This version of puma might be problematic. Click here for more details.

Files changed (74) hide show
  1. checksums.yaml +5 -5
  2. data/History.md +229 -1
  3. data/README.md +179 -212
  4. data/docs/architecture.md +37 -0
  5. data/{DEPLOYMENT.md → docs/deployment.md} +24 -4
  6. data/docs/images/puma-connection-flow-no-reactor.png +0 -0
  7. data/docs/images/puma-connection-flow.png +0 -0
  8. data/docs/images/puma-general-arch.png +0 -0
  9. data/docs/plugins.md +28 -0
  10. data/docs/restart.md +41 -0
  11. data/docs/signals.md +56 -3
  12. data/docs/systemd.md +130 -37
  13. data/ext/puma_http11/PumaHttp11Service.java +2 -0
  14. data/ext/puma_http11/extconf.rb +8 -0
  15. data/ext/puma_http11/http11_parser.c +84 -84
  16. data/ext/puma_http11/http11_parser.rl +9 -9
  17. data/ext/puma_http11/mini_ssl.c +105 -9
  18. data/ext/puma_http11/org/jruby/puma/Http11Parser.java +13 -16
  19. data/ext/puma_http11/org/jruby/puma/IOBuffer.java +72 -0
  20. data/ext/puma_http11/org/jruby/puma/MiniSSL.java +30 -6
  21. data/lib/puma.rb +10 -0
  22. data/lib/puma/accept_nonblock.rb +2 -0
  23. data/lib/puma/app/status.rb +13 -0
  24. data/lib/puma/binder.rb +33 -18
  25. data/lib/puma/cli.rb +48 -33
  26. data/lib/puma/client.rb +94 -22
  27. data/lib/puma/cluster.rb +69 -21
  28. data/lib/puma/commonlogger.rb +2 -0
  29. data/lib/puma/configuration.rb +134 -136
  30. data/lib/puma/const.rb +16 -2
  31. data/lib/puma/control_cli.rb +31 -18
  32. data/lib/puma/convenient.rb +5 -3
  33. data/lib/puma/daemon_ext.rb +2 -0
  34. data/lib/puma/delegation.rb +2 -0
  35. data/lib/puma/detect.rb +2 -0
  36. data/lib/puma/dsl.rb +349 -113
  37. data/lib/puma/events.rb +8 -4
  38. data/lib/puma/io_buffer.rb +3 -6
  39. data/lib/puma/jruby_restart.rb +2 -1
  40. data/lib/puma/launcher.rb +60 -36
  41. data/lib/puma/minissl.rb +85 -28
  42. data/lib/puma/null_io.rb +2 -0
  43. data/lib/puma/plugin.rb +2 -0
  44. data/lib/puma/plugin/tmp_restart.rb +3 -2
  45. data/lib/puma/rack/builder.rb +4 -1
  46. data/lib/puma/rack/urlmap.rb +2 -0
  47. data/lib/puma/rack_default.rb +2 -0
  48. data/lib/puma/reactor.rb +218 -30
  49. data/lib/puma/runner.rb +18 -4
  50. data/lib/puma/server.rb +149 -56
  51. data/lib/puma/single.rb +16 -5
  52. data/lib/puma/state_file.rb +2 -0
  53. data/lib/puma/tcp_logger.rb +2 -0
  54. data/lib/puma/thread_pool.rb +59 -6
  55. data/lib/puma/util.rb +2 -6
  56. data/lib/rack/handler/puma.rb +58 -19
  57. data/tools/jungle/README.md +12 -2
  58. data/tools/jungle/init.d/README.md +2 -0
  59. data/tools/jungle/init.d/puma +8 -8
  60. data/tools/jungle/init.d/run-puma +1 -1
  61. data/tools/jungle/rc.d/README.md +74 -0
  62. data/tools/jungle/rc.d/puma +61 -0
  63. data/tools/jungle/rc.d/puma.conf +10 -0
  64. data/tools/trickletest.rb +1 -1
  65. metadata +25 -85
  66. data/.github/issue_template.md +0 -20
  67. data/Gemfile +0 -12
  68. data/Manifest.txt +0 -77
  69. data/Rakefile +0 -158
  70. data/gemfiles/2.1-Gemfile +0 -12
  71. data/lib/puma/compat.rb +0 -14
  72. data/lib/puma/java_io_buffer.rb +0 -45
  73. data/lib/puma/rack/backports/uri/common_193.rb +0 -33
  74. data/puma.gemspec +0 -52
data/lib/puma/null_io.rb CHANGED
@@ -1,3 +1,5 @@
1
+ # frozen_string_literal: true
2
+
1
3
  module Puma
2
4
  # Provides an IO-like object that always appears to contain no data.
3
5
  # Used as the value for rack.input when the request has no body.
data/lib/puma/plugin.rb CHANGED
@@ -1,3 +1,5 @@
1
+ # frozen_string_literal: true
2
+
1
3
  module Puma
2
4
  class UnknownPlugin < RuntimeError; end
3
5
 
@@ -1,3 +1,5 @@
1
+ # frozen_string_literal: true
2
+
1
3
  require 'puma/plugin'
2
4
 
3
5
  Puma::Plugin.create do
@@ -8,7 +10,7 @@ Puma::Plugin.create do
8
10
 
9
11
  # If we can't write to the path, then just don't bother with this plugin
10
12
  begin
11
- File.write path, ""
13
+ File.write(path, "") unless File.exist?(path)
12
14
  orig = File.stat(path).mtime
13
15
  rescue SystemCallError
14
16
  return
@@ -32,4 +34,3 @@ Puma::Plugin.create do
32
34
  end
33
35
  end
34
36
  end
35
-
@@ -1,3 +1,5 @@
1
+ # frozen_string_literal: true
2
+
1
3
  module Puma
2
4
  end
3
5
 
@@ -110,7 +112,8 @@ module Puma::Rack
110
112
 
111
113
  has_options = false
112
114
  server.valid_options.each do |name, description|
113
- next if name.to_s.match(/^(Host|Port)[^a-zA-Z]/) # ignore handler's host and port options, we do our own.
115
+ next if name.to_s =~ /^(Host|Port)[^a-zA-Z]/ # ignore handler's host and port options, we do our own.
116
+
114
117
  info << " -O %-21s %s" % [name, description]
115
118
  has_options = true
116
119
  end
@@ -1,3 +1,5 @@
1
+ # frozen_string_literal: true
2
+
1
3
  module Puma::Rack
2
4
  # Rack::URLMap takes a hash mapping urls or paths to apps, and
3
5
  # dispatches accordingly. Support for HTTP/1.1 host names exists if
@@ -1,3 +1,5 @@
1
+ # frozen_string_literal: true
2
+
1
3
  require 'rack/handler/puma'
2
4
 
3
5
  module Rack::Handler
data/lib/puma/reactor.rb CHANGED
@@ -1,57 +1,201 @@
1
+ # frozen_string_literal: true
2
+
1
3
  require 'puma/util'
2
4
  require 'puma/minissl'
3
5
 
6
+ require 'nio'
7
+
4
8
  module Puma
9
+ # Internal Docs, Not a public interface.
10
+ #
11
+ # The Reactor object is responsible for ensuring that a request has been
12
+ # completely received before it starts to be processed. This may be known as read buffering.
13
+ # If read buffering is not done, and no other read buffering is performed (such as by an application server
14
+ # such as nginx) then the application would be subject to a slow client attack.
15
+ #
16
+ # Each Puma "worker" process has its own Reactor. For example if you start puma with `$ puma -w 5` then
17
+ # it will have 5 workers and each worker will have it's own reactor.
18
+ #
19
+ # For a graphical representation of how the reactor works see [architecture.md](https://github.com/puma/puma/blob/master/docs/architecture.md#connection-pipeline).
20
+ #
21
+ # ## Reactor Flow
22
+ #
23
+ # A connection comes into a `Puma::Server` instance, it is then passed to a `Puma::Reactor` instance,
24
+ # which stores it in an array and waits for any of the connections to be ready for reading.
25
+ #
26
+ # The waiting/wake up is performed with nio4r, which will use the appropriate backend (libev, Java NIO or
27
+ # just plain IO#select). The call to `NIO::Selector#select` will "wake up" and
28
+ # return the references to any objects that caused it to "wake". The reactor
29
+ # then loops through each of these request objects, and sees if they're complete. If they
30
+ # have a full header and body then the reactor passes the request to a thread pool.
31
+ # Once in a thread pool, a "worker thread" can run the the application's Ruby code against the request.
32
+ #
33
+ # If the request is not complete, then it stays in the array, and the next time any
34
+ # data is written to that socket reference, then the loop is woken up and it is checked for completeness again.
35
+ #
36
+ # A detailed example is given in the docs for `run_internal` which is where the bulk
37
+ # of this logic lives.
5
38
  class Reactor
6
39
  DefaultSleepFor = 5
7
40
 
41
+ # Creates an instance of Puma::Reactor
42
+ #
43
+ # The `server` argument is an instance of `Puma::Server`
44
+ # that is used to write a response for "low level errors"
45
+ # when there is an exception inside of the reactor.
46
+ #
47
+ # The `app_pool` is an instance of `Puma::ThreadPool`.
48
+ # Once a request is fully formed (header and body are received)
49
+ # it will be passed to the `app_pool`.
8
50
  def initialize(server, app_pool)
9
51
  @server = server
10
52
  @events = server.events
11
53
  @app_pool = app_pool
12
54
 
55
+ @selector = NIO::Selector.new
56
+
13
57
  @mutex = Mutex.new
58
+
59
+ # Read / Write pipes to wake up internal while loop
14
60
  @ready, @trigger = Puma::Util.pipe
15
61
  @input = []
16
62
  @sleep_for = DefaultSleepFor
17
63
  @timeouts = []
18
64
 
19
- @sockets = [@ready]
65
+ mon = @selector.register(@ready, :r)
66
+ mon.value = @ready
67
+
68
+ @monitors = [mon]
20
69
  end
21
70
 
22
71
  private
23
72
 
73
+ # Until a request is added via the `add` method this method will internally
74
+ # loop, waiting on the `sockets` array objects. The only object in this
75
+ # array at first is the `@ready` IO object, which is the read end of a pipe
76
+ # connected to `@trigger` object. When `@trigger` is written to, then the loop
77
+ # will break on `NIO::Selector#select` and return an array.
78
+ #
79
+ # ## When a request is added:
80
+ #
81
+ # When the `add` method is called, an instance of `Puma::Client` is added to the `@input` array.
82
+ # Next the `@ready` pipe is "woken" by writing a string of `"*"` to `@trigger`.
83
+ #
84
+ # When that happens, the internal loop stops blocking at `NIO::Selector#select` and returns a reference
85
+ # to whatever "woke" it up. On the very first loop, the only thing in `sockets` is `@ready`.
86
+ # When `@trigger` is written-to, the loop "wakes" and the `ready`
87
+ # variable returns an array of arrays that looks like `[[#<IO:fd 10>], [], []]` where the
88
+ # first IO object is the `@ready` object. This first array `[#<IO:fd 10>]`
89
+ # is saved as a `reads` variable.
90
+ #
91
+ # The `reads` variable is iterated through. In the case that the object
92
+ # is the same as the `@ready` input pipe, then we know that there was a `trigger` event.
93
+ #
94
+ # If there was a trigger event, then one byte of `@ready` is read into memory. In the case of the first request,
95
+ # the reactor sees that it's a `"*"` value and the reactor adds the contents of `@input` into the `sockets` array.
96
+ # The while then loop continues to iterate again, but now the `sockets` array contains a `Puma::Client` instance in addition
97
+ # to the `@ready` IO object. For example: `[#<IO:fd 10>, #<Puma::Client:0x3fdc1103bee8 @ready=false>]`.
98
+ #
99
+ # Since the `Puma::Client` in this example has data that has not been read yet,
100
+ # the `NIO::Selector#select` is immediately able to "wake" and read from the `Puma::Client`. At this point the
101
+ # `ready` output looks like this: `[[#<Puma::Client:0x3fdc1103bee8 @ready=false>], [], []]`.
102
+ #
103
+ # Each element in the first entry is iterated over. The `Puma::Client` object is not
104
+ # the `@ready` pipe, so the reactor checks to see if it has the full header and body with
105
+ # the `Puma::Client#try_to_finish` method. If the full request has been sent,
106
+ # then the request is passed off to the `@app_pool` thread pool so that a "worker thread"
107
+ # can pick up the request and begin to execute application logic. This is done
108
+ # via `@app_pool << c`. The `Puma::Client` is then removed from the `sockets` array.
109
+ #
110
+ # If the request body is not present then nothing will happen, and the loop will iterate
111
+ # again. When the client sends more data to the socket the `Puma::Client` object will
112
+ # wake up the `NIO::Selector#select` and it can again be checked to see if it's ready to be
113
+ # passed to the thread pool.
114
+ #
115
+ # ## Time Out Case
116
+ #
117
+ # In addition to being woken via a write to one of the sockets the `NIO::Selector#select` will
118
+ # periodically "time out" of the sleep. One of the functions of this is to check for
119
+ # any requests that have "timed out". At the end of the loop it's checked to see if
120
+ # the first element in the `@timeout` array has exceed its allowed time. If so,
121
+ # the client object is removed from the timeout array, a 408 response is written.
122
+ # Then its connection is closed, and the object is removed from the `sockets` array
123
+ # that watches for new data.
124
+ #
125
+ # This behavior loops until all the objects that have timed out have been removed.
126
+ #
127
+ # Once all the timeouts have been processed, the next duration of the `NIO::Selector#select` sleep
128
+ # will be set to be equal to the amount of time it will take for the next timeout to occur.
129
+ # This calculation happens in `calculate_sleep`.
24
130
  def run_internal
25
- sockets = @sockets
131
+ monitors = @monitors
132
+ selector = @selector
26
133
 
27
134
  while true
28
135
  begin
29
- ready = IO.select sockets, nil, nil, @sleep_for
136
+ ready = selector.select @sleep_for
30
137
  rescue IOError => e
31
- if sockets.any? { |socket| socket.closed? }
138
+ Thread.current.purge_interrupt_queue if Thread.current.respond_to? :purge_interrupt_queue
139
+ if monitors.any? { |mon| mon.value.closed? }
32
140
  STDERR.puts "Error in select: #{e.message} (#{e.class})"
33
141
  STDERR.puts e.backtrace
34
- sockets = sockets.reject { |socket| socket.closed? }
142
+
143
+ monitors.reject! do |mon|
144
+ if mon.value.closed?
145
+ selector.deregister mon.value
146
+ true
147
+ end
148
+ end
149
+
35
150
  retry
36
151
  else
37
152
  raise
38
153
  end
39
154
  end
40
155
 
41
- if ready and reads = ready[0]
42
- reads.each do |c|
43
- if c == @ready
156
+ if ready
157
+ ready.each do |mon|
158
+ if mon.value == @ready
44
159
  @mutex.synchronize do
45
160
  case @ready.read(1)
46
161
  when "*"
47
- sockets += @input
162
+ @input.each do |c|
163
+ mon = nil
164
+ begin
165
+ begin
166
+ mon = selector.register(c, :r)
167
+ rescue ArgumentError
168
+ # There is a bug where we seem to be registering an already registered
169
+ # client. This code deals with this situation but I wish we didn't have to.
170
+ monitors.delete_if { |submon| submon.value.to_io == c.to_io }
171
+ selector.deregister(c)
172
+ mon = selector.register(c, :r)
173
+ end
174
+ rescue IOError
175
+ # Means that the io is closed, so we should ignore this request
176
+ # entirely
177
+ else
178
+ mon.value = c
179
+ @timeouts << mon if c.timeout_at
180
+ monitors << mon
181
+ end
182
+ end
48
183
  @input.clear
184
+
185
+ @timeouts.sort! { |a,b| a.value.timeout_at <=> b.value.timeout_at }
186
+ calculate_sleep
49
187
  when "c"
50
- sockets.delete_if do |s|
51
- if s == @ready
188
+ monitors.reject! do |submon|
189
+ if submon.value == @ready
52
190
  false
53
191
  else
54
- s.close
192
+ submon.value.close
193
+ begin
194
+ selector.deregister submon.value
195
+ rescue IOError
196
+ # nio4r on jruby seems to throw an IOError here if the IO is closed, so
197
+ # we need to swallow it.
198
+ end
55
199
  true
56
200
  end
57
201
  end
@@ -60,19 +204,21 @@ module Puma
60
204
  end
61
205
  end
62
206
  else
207
+ c = mon.value
208
+
63
209
  # We have to be sure to remove it from the timeout
64
210
  # list or we'll accidentally close the socket when
65
211
  # it's in use!
66
212
  if c.timeout_at
67
213
  @mutex.synchronize do
68
- @timeouts.delete c
214
+ @timeouts.delete mon
69
215
  end
70
216
  end
71
217
 
72
218
  begin
73
219
  if c.try_to_finish
74
220
  @app_pool << c
75
- sockets.delete c
221
+ clear_monitor mon
76
222
  end
77
223
 
78
224
  # Don't report these to the lowlevel_error handler, otherwise
@@ -82,18 +228,23 @@ module Puma
82
228
  c.write_500
83
229
  c.close
84
230
 
85
- sockets.delete c
231
+ clear_monitor mon
86
232
 
87
233
  # SSL handshake failure
88
234
  rescue MiniSSL::SSLError => e
89
235
  @server.lowlevel_error(e, c.env)
90
236
 
91
237
  ssl_socket = c.io
92
- addr = ssl_socket.peeraddr.last
238
+ begin
239
+ addr = ssl_socket.peeraddr.last
240
+ rescue IOError
241
+ addr = "<unknown>"
242
+ end
243
+
93
244
  cert = ssl_socket.peercert
94
245
 
95
246
  c.close
96
- sockets.delete c
247
+ clear_monitor mon
97
248
 
98
249
  @events.ssl_error @server, addr, cert, e
99
250
 
@@ -104,7 +255,7 @@ module Puma
104
255
  c.write_400
105
256
  c.close
106
257
 
107
- sockets.delete c
258
+ clear_monitor mon
108
259
 
109
260
  @events.parse_error @server, c.env, e
110
261
  rescue StandardError => e
@@ -113,7 +264,7 @@ module Puma
113
264
  c.write_500
114
265
  c.close
115
266
 
116
- sockets.delete c
267
+ clear_monitor mon
117
268
  end
118
269
  end
119
270
  end
@@ -123,11 +274,13 @@ module Puma
123
274
  @mutex.synchronize do
124
275
  now = Time.now
125
276
 
126
- while @timeouts.first.timeout_at < now
127
- c = @timeouts.shift
277
+ while @timeouts.first.value.timeout_at < now
278
+ mon = @timeouts.shift
279
+ c = mon.value
128
280
  c.write_408 if c.in_data_phase
129
281
  c.close
130
- sockets.delete c
282
+
283
+ clear_monitor mon
131
284
 
132
285
  break if @timeouts.empty?
133
286
  end
@@ -138,6 +291,11 @@ module Puma
138
291
  end
139
292
  end
140
293
 
294
+ def clear_monitor(mon)
295
+ @selector.deregister mon.value
296
+ @monitors.delete mon
297
+ end
298
+
141
299
  public
142
300
 
143
301
  def run
@@ -162,11 +320,21 @@ module Puma
162
320
  end
163
321
  end
164
322
 
323
+ # The `calculate_sleep` sets the value that the `NIO::Selector#select` will
324
+ # sleep for in the main reactor loop when no sockets are being written to.
325
+ #
326
+ # The values kept in `@timeouts` are sorted so that the first timeout
327
+ # comes first in the array. When there are no timeouts the default timeout is used.
328
+ #
329
+ # Otherwise a sleep value is set that is the same as the amount of time it
330
+ # would take for the first element to time out.
331
+ #
332
+ # If that value is in the past, then a sleep value of zero is used.
165
333
  def calculate_sleep
166
334
  if @timeouts.empty?
167
335
  @sleep_for = DefaultSleepFor
168
336
  else
169
- diff = @timeouts.first.timeout_at.to_f - Time.now.to_f
337
+ diff = @timeouts.first.value.timeout_at.to_f - Time.now.to_f
170
338
 
171
339
  if diff < 0.0
172
340
  @sleep_for = 0
@@ -176,17 +344,35 @@ module Puma
176
344
  end
177
345
  end
178
346
 
347
+ # This method adds a connection to the reactor
348
+ #
349
+ # Typically called by `Puma::Server` the value passed in
350
+ # is usually a `Puma::Client` object that responds like an IO
351
+ # object.
352
+ #
353
+ # The main body of the reactor loop is in `run_internal` and it
354
+ # will sleep on `NIO::Selector#select`. When a new connection is added to the
355
+ # reactor it cannot be added directly to the `sockets` array, because
356
+ # the `NIO::Selector#select` will not be watching for it yet.
357
+ #
358
+ # Instead what needs to happen is that `NIO::Selector#select` needs to be woken up,
359
+ # the contents of `@input` added to the `sockets` array, and then
360
+ # another call to `NIO::Selector#select` needs to happen. Since the `Puma::Client`
361
+ # object can be read immediately, it does not block, but instead returns
362
+ # right away.
363
+ #
364
+ # This behavior is accomplished by writing to `@trigger` which wakes up
365
+ # the `NIO::Selector#select` and then there is logic to detect the value of `*`,
366
+ # pull the contents from `@input` and add them to the sockets array.
367
+ #
368
+ # If the object passed in has a timeout value in `timeout_at` then
369
+ # it is added to a `@timeouts` array. This array is then re-arranged
370
+ # so that the first element to timeout will be at the front of the
371
+ # array. Then a value to sleep for is derived in the call to `calculate_sleep`
179
372
  def add(c)
180
373
  @mutex.synchronize do
181
374
  @input << c
182
375
  @trigger << "*"
183
-
184
- if c.timeout_at
185
- @timeouts << c
186
- @timeouts.sort! { |a,b| a.timeout_at <=> b.timeout_at }
187
-
188
- calculate_sleep
189
- end
190
376
  end
191
377
  end
192
378
 
@@ -195,6 +381,7 @@ module Puma
195
381
  begin
196
382
  @trigger << "c"
197
383
  rescue IOError
384
+ Thread.current.purge_interrupt_queue if Thread.current.respond_to? :purge_interrupt_queue
198
385
  end
199
386
  end
200
387
 
@@ -202,6 +389,7 @@ module Puma
202
389
  begin
203
390
  @trigger << "!"
204
391
  rescue IOError
392
+ Thread.current.purge_interrupt_queue if Thread.current.respond_to? :purge_interrupt_queue
205
393
  end
206
394
 
207
395
  @thread.join