From f385ed423e11ad40822f688bc592eaa78efa5b34 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Mon, 9 Jan 2017 18:59:00 +0000 Subject: eventmachine: wait for deferred actions to finish Since EventMachine 1.0.0 in 2012, the EM.defers_finish? API exists to check for the existence of deferred actions. Support it if it exists in the running version of EM and update the note in our SIGNALS document. Thanks to on the mailing list for bringing this up: https://bogomips.org/rainbows-public/CAKwvcL-VH3we4qA1pkNAstTmWvqNA=Rir2N_YiWztV_qbaLQvA@mail.gmail.com/ --- SIGNALS | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'SIGNALS') diff --git a/SIGNALS b/SIGNALS index e53c3e4..fa95a1c 100644 --- a/SIGNALS +++ b/SIGNALS @@ -24,9 +24,9 @@ between \Rainbows!, unicorn and nginx. * INT/TERM - quick shutdown, kills all workers immediately * QUIT - graceful shutdown, waits for workers to finish their - current request before finishing. This currently does not - wait for requests deferred to a separate thread when using - EventMachine (when app.deferred?(env) => true) + current request before finishing. Since Rainbows 5.1.0 (Jan 2017), + this waits requests deferred to a separate thread with + EventMachine (app.deferred?(env) => true). * USR1 - reopen all logs owned by the master and all workers See Unicorn::Util.reopen_logs for what is considered a log. -- cgit v1.2.3-24-ge0c7