# Locking issues in sidekiq jobs?

**URL:** <https://meta.discourse.org/t/locking-issues-in-sidekiq-jobs/69287>\
**Category:** Product Support\
**Created:** [2017 年9 月 3 日 13:49 UTC](https://meta.discourse.org/t/locking-issues-in-sidekiq-jobs/69287 "2017-09-03T13:49:34Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

作者： ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
发布日期： [2019 年1 月 2 日 17:06 UTC](https://meta.discourse.org/t/locking-issues-in-sidekiq-jobs/69287/3 "2019-01-02T17:06:23Z")

</div>

Were you ever able to pinpoint this issue? We’re seeing the exact same thing on one server. Sidekiq goes to 90% CPU and the only way to get it back to normal is to restart it. It then stays low for a day or so and then it gets stuck at 90% again.

`ps -T -p <pid>` says this is happening in `manager.rb:27` which is here

> <https://github.com/discourse/mini_scheduler/blob/main/lib/mini_scheduler/manager.rb#L27>

There are no scheduled jobs in Sidekiq.

---

_[View the full topic](https://meta.discourse.org/t/locking-issues-in-sidekiq-jobs/69287)._