From 7864dbdd4b53d427e08d717bc609bf5751119137 Mon Sep 17 00:00:00 2001 From: "Dustin J. Mitchell" Date: Mon, 4 Apr 2022 14:43:41 +0000 Subject: [PATCH] Remove outdated warning about forking This paragraph is no longer true after 5.3.0 and in fact contradicts the rest of the section. --- README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/README.md b/README.md index 7b46be19..76339b06 100644 --- a/README.md +++ b/README.md @@ -81,8 +81,6 @@ Version v5.x of `dogstatsd-ruby` is using a sender thread for flushing. This pro If you are using [Sidekiq](https://github.com/mperham/sidekiq), please make sure to close the client instances that are instantiated. [See this example on using DogStatsD-ruby v5.x with Sidekiq](https://github.com/DataDog/dogstatsd-ruby/blob/master/examples/sidekiq_example.rb). -If you are using [Puma](https://github.com/puma/puma) or [Unicorn](https://yhbt.net/unicorn.git), please make sure to create the instance of DogStatsD in the workers, not in the main process before it forks to create its workers. See [this comment for more details](https://github.com/DataDog/dogstatsd-ruby/issues/179#issuecomment-845570345). - Applications that run into issues but can't apply these recommendations should use the `single_thread` mode which disables the use of the sender thread. Here is how to instantiate a client in this mode: