Skip to content

Commit

Permalink
Document issue with Resque workers hanging
Browse files Browse the repository at this point in the history
**What does this PR do?**:

This PR adds the "Resque workers hang on exit" issue discussed in
#3015 to the
"Known issues and suggested configurations" section of our docs.

**Motivation**:

This issue seems to come up a few times, e.g. in:
* #466
* #2379
* #3015

...so I've decided to document the issue and the best-known workaround
so that other customers than unfortunately run into it may find our
suggested solution.

**Additional Notes**:

N/A

**How to test the change?**:

Docs-only change.
  • Loading branch information
ivoanjo committed Aug 8, 2023
1 parent b3f3a0a commit 8cd1f94
Showing 1 changed file with 12 additions and 1 deletion.
13 changes: 12 additions & 1 deletion docs/GettingStarted.md
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,7 @@ To contribute, check out the [contribution guidelines][contribution docs] and [d
- [Known issues and suggested configurations](#known-issues-and-suggested-configurations)
- [Payload too large](#payload-too-large)
- [Stack level too deep](#stack-level-too-deep)
- [Resque workers hang on exit](#resque-workers-hang-on-exit)

## Compatibility

Expand Down Expand Up @@ -2975,6 +2976,16 @@ As the implementation of `alias_method` exists within those libraries, Datadog g

For libraries without a known workaround, consider removing the library using `alias` or `Module#alias_method` or separating libraries into different environments for testing.

For any further questions or to report an occurence of this issue, please [reach out to Datadog support](https://docs.datadoghq.com/help)
For any further questions or to report an occurrence of this issue, please [reach out to Datadog support](https://docs.datadoghq.com/help)

### Resque workers hang on exit

Resque's default of forking a process per job can, in rare situations, result in resque processes hanging on exit when instrumented with ddtrace.

As a workaround, we recommend setting the `FORK_PER_JOB` environment variable to `false` to disable this behavior.

See [this issue](https://github.com/DataDog/dd-trace-rb/issues/3015) for a discussion of the problem.

<!---->

[header tags]: https://docs.datadoghq.com/tracing/configure_data_security/#applying-header-tags-to-root-spans

0 comments on commit 8cd1f94

Please sign in to comment.