kotovalexarian-likes-github/mperham--sidekiq
1
0
Fork 0
mirror of https://github.com/mperham/sidekiq.git synced 2022-11-09 13:52:34 -05:00
Code Releases Activity

Remove note about ephemeral_hostname

Browse source 
It was a hack and I don't want to document or support it long-term.  Instead call out timed_fetch as the right solution for most people.
This commit is contained in:
Mike Perham 2016-04-26 10:23:45 -07:00
parent 78fc103d56
commit 99667863e8
2 changed files with 6 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

1
Ent-Changes.md
View file

@ -7,6 +7,7 @@ HEAD
------------- -------------
- Add API to check if a unique lock is present. See [#2932] for details. - Add API to check if a unique lock is present. See [#2932] for details.
- Tune concurrent limiters to minimize thread thrashing under heavy contention. [#2944]
1.2.1 1.2.1
------------- -------------

12
Pro-3.0-Upgrade.md
View file

@ -17,17 +17,15 @@ Sidekiq Pro 3.0 is designed to work with Sidekiq 4.0.
* Reliable fetch has been re-implemented due to the fetch changes in * Reliable fetch has been re-implemented due to the fetch changes in
Sidekiq 4.0. Sidekiq 4.0.
* Support for platforms without persistent hostnames. Since reliable fetch * Support for platforms without persistent hostnames. Since the reliable\_fetch
normally requires a persistent hostname, you may disable hostname usage on algorithm requires a persistent hostname, an alternative reliability
platforms like Heroku and Docker: algorithm is now available for platforms like Heroku and Docker:
```ruby ```ruby
Sidekiq.configure_server do |config| Sidekiq.configure_server do |config|
config.options[:ephemeral_hostname] = true config.timed_fetch!
config.reliable_fetch!
end end
``` ```
This option is enabled automatically if Heroku's DYNO environment variable is present. The wiki contains [much more detail about each reliability option](https://github.com/mperham/sidekiq/wiki/Pro-Reliability-Server).
Without a persistent hostname, each Sidekiq process **must** have its own unique index.
* The old 'sidekiq/notifications' features have been removed. * The old 'sidekiq/notifications' features have been removed.