Mike Perham

I would suggest you lower that timeout from 120 seconds back down to the default of 30 seconds and see if that fixes the issue.

How are you starting Sidekiq in k8s? Show me the actual exec line.

Ok, that command is good. Some people start Sidekiq via bash, which can trap signals, breaking the shutdown process and orphaning jobs. I would try to determine when the behavior...

That's definitely not expected behavior but bugs can be located anywhere or be caused by several subsystems interacting badly. The fact that a Sidekiq version downgrade is not solving the...

`ThreadError: can't alloc thread` is a very bad sign and indicates you've got a resource issue somewhere but I have no idea how to debug that issue. What are you...

@fatkodima That's concerning but I don't have any idea what might be wrong. I'd suggest you open your own issue, link to this one, and provide any more debugging /...

I suspect the problem lies in [sidekiq/web/action.rb:51](https://github.com/sidekiq/sidekiq/blob/164b690a1c08a5ff72c1fbbf78f8b6d42734feef/lib/sidekiq/web/action.rb#L51-L56).

The pseudocode isn’t really debuggable. Can you give me a gist which reproduces the issue?

It's possible I need to update the docs. I'll investigate Monday.

Inconsistent namespacing is a currently known issue, see #6337. The plan is the prefix all metrics with `sidekiq` for Sidekiq Pro 8.0. Likewise metrics coming from puma should start with...