High number of Sessions to the database with the value SET parameter (#292022) · Issues · GitLab.org / GitLab · GitLab (original) (raw)
High number of Sessions to the database with the value SET parameter
After investigating spikes over 70% of CPU usage on the database :
we find out these statements being executed thousands of times :
QueryId | Query |
---|---|
-1600097631520268746 | SET application_name='sidekiq 5.2.9 queues:pipeline_...ate_highest_role [0 of 5 busy]' |
-5301438116714883807 | SET application_name='sidekiq 5.2.9 queues:pipeline_..._reset_approvals [0 of 5 busy]' |
-1837678789145345515 | SET application_name='sidekiq 5.2.9 queues:pipeline_..._reset_approvals [1 of 5 busy]' |
-5574449258521171212 | SET application_name='sidekiq 5.2.9 queues:pipeline_...ate_highest_role [1 of 5 busy]' |
-1837678789145345515 | SET application_name='sidekiq 5.2.9 queues:pipeline_..._reset_approvals [1 of 5 busy]' |
464378149681088322 | SET application_name='sidekiq 5.2.9 queues:authorize...export_deletion [6 of 15 busy]' |
4685939062284273306 | SET application_name='sidekiq 5.2.9 queues:pipeline_...ate_highest_role [2 of 5 busy]' |
1228111764957874426 | SET application_name='sidekiq 5.2.9 queues:authorize...export_deletion [4 of 15 busy]' |
1274360748137397104 | SET application_name='sidekiq 5.2.9 queues:pipeline_..._reset_approvals [2 of 5 busy]' |
4683099022293987741 | SET application_name='sidekiq 5.2.9 queues:authorize...export_deletion [5 of 15 busy]' |
It seems that sidekiq is generating/using these SET statements. It seems we are reiterating over them: [2 of 5 busy]
or [5 of 15 busy]
... what means the busy in this context? Could we reduce/eliminate them?
Edited Dec 15, 2020 by Jose Finotto