# Sidekiq job concurrency issue

**URL:** <https://meta.discourse.org/t/sidekiq-job-concurrency-issue/274618>\
**Category:** Self-hosting\
**Tags:** unsupported-install\
**Created:** [August 10, 2023, 10:48am UTC](https://meta.discourse.org/t/sidekiq-job-concurrency-issue/274618 "2023-08-10T10:48:29Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Prasanth\_Balan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/prasanth_balan/32/281256_2.png) [@Prasanth\_Balan](https://meta.discourse.org/u/Prasanth_Balan)\
**Post date:** [August 11, 2023, 8:53am UTC](https://meta.discourse.org/t/sidekiq-job-concurrency-issue/274618/5 "2023-08-11T08:53:48Z")

</div>

> [@merefield](#):
>
> I think you are going to have to add some logging to your job to find out what is going on.

We have already added logging on my custom code. No issue on our code.

> [@merefield](#):
>
> This is your own custom code, right?

Yes

> [@merefield](#):
>
> So are some people on Kubernetes but that’s not supported here.

Yes, We’re using Kubernetes cluster.

Just one question!

The sidekiq should run only one process? or running more than one sidekiq process is fine?

---

_[View the full topic](https://meta.discourse.org/t/sidekiq-job-concurrency-issue/274618)._
