Fix Sidekiq stop_sequence signal (TTIN→TSTP) + add long-running-jobs guide#15
Draft
lvangool wants to merge 1 commit into
Draft
Conversation
The procfile_metadata example used TTIN, which in Sidekiq 5+ only dumps
thread backtraces and does not start quiet mode, so workers kept fetching
new jobs throughout the shutdown wait window. Switch the example to TSTP
(the correct quiet-mode signal since Sidekiq 5.0) and add a Callout
explaining the TSTP/TTIN/USR1 semantics and version compatibility.
Also adds a dedicated how-to page so the pattern is discoverable by the
terms customers search ("long-running sidekiq across deploys") rather than
only under the signal-centric "Process Signal Options" heading.
Linear: SUP-975 (absorbs SUP-979)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
procfile_metadatastop_sequenceexample inmanifest/_processes.mdxfromttintotstp._processes.mdxexplaining the signal semantics (TSTP= quiet mode since Sidekiq 5.0;TTIN= backtrace dump only;USR1= deprecated in 7.0+).build-and-config/long-running-sidekiq-across-deploys.mdxwith a signal-semantics table, a workedstop_sequenceexample, and cross-links.Why
On HS #33436 a customer running Sidekiq 7.3.6 followed our documented
ttin, 120, term, 5, killexample and saw workers keep fetching new jobs throughout the 120-second wait, defeating the graceful drain. In Sidekiq 5+TTINonly dumps thread backtraces — it does not start quiet mode. The correct quiet-mode signal isTSTP. This was a correctness bug in the docs (originally filed as SUP-979) compounded by a discoverability gap: the existing content lives under the signal-centric "Process Signal Options" heading and doesn't surface for product-term searches like "long-running sidekiq across deploys" (SUP-975).Linear
Test plan
yarn validate:mdxpasses_processes.mdx↔ new page)🤖 Generated with Claude Code