Arthur

+1 I've been using max_fails=0 to prevent all our applications going down when one is misbehaving. Yes, we have a bit of a weird set up on AWS ECS where...

@splitice It was just a note/observatiuon that `proxy_next_upstream none;` does not prevent upstreams from being marked as down when they error/timeout. I missed that the first time I looked into...

@ArturT We use Sidekiq::Throttled to enforce concurrency. Not sure if that is sufficient for you use case, as it will not enforce the sequence of jobs, but will ensure only...

We are using super_fetch icm sidekiq_throttled and it seems to work as expected. Perhaps the initializer order matters? This how I init relevant parts of the server: ``` initializer 'sidekiq-server'...

> However, it'll override Sidekiq's custom fetch from Sidekiq::Pro::SuperFetch to Sidekiq::Throttled::Fetch. We've since learned this too, but at first glance it looks like it should be possible to 'wrap' the...

@ixti I see you've setup a new repo for sidekick-throttled? Shall I make a PR there? It might also be a good idea to put a little notice on this...

> On testing, I think we can mark tests as "require sidekiq-pro" and have extra appraisal for those. I'll see if I can get that to work 👍

Just ran into this myself, fairly certain always setting tag_handling: 'xml' fixes it. I'll do more testing tomorrow and make a PR if it turns out good

Coincidentally, we also ran into ordering issues with Throttled this week. As it works by popping a job from the queue and requeuing it if it should be throttled. This...

I've made a PR that fixes this, forgot to link the issue though 😅 #307