Strong increase of Zammad Jobs

Jomi · December 17, 2024, 12:26pm

Hello dear community,

We are facing some issue with Zammad Jobs since we update 5.4.1 to 6.3.1

Used Zammad version: 6.3.1
Used Zammad installation type: helm-chart (V12.1.1)
Operating system: Docker
Browser + version: Firefox 133.0.3 OR Google 131.0.6778.140

ZAMMAD_PROCESS_DELAYED_JOBS_WORKERS : 6
ZAMMAD_SESSION_JOBS_CONCURRENT : 3

zammad:
zammad:
elasticsearch:
resources:
limits:
cpu: 1
memory: 8Gi
requests:
cpu: 200m
memory: 2Gi

Expected behavior:

While counting with Delayed::Job.count
Jobs don’t reach more than 200 jobs on high activity
And decrease fast cause of the optimization of the configuration

Actual behavior:

Jobs increase up to 2500 Jobs and happens every 11 minutes
It does decrease fast cause of the optimization of the configuration

Supposition :
It looks like there is a recurrent background batch that create massive jobs on zammad-railserver

Thank you for your help, and questions that I’m looking forward to answer

Jomi · December 17, 2024, 4:51pm

Here is the 4 jobs when the delayed job is at his lowest

#<Delayed::Backend::ActiveRecord::Job:0x00007f1405cfc310 id: 402388367, priority: 300, attempts: 0, handler: "—

!ruby/object:ActiveJob::QueueAdapters::DelayedJobAdapter::JobWrapper\njob_data:\n job_class: SearchIndexAssociationsJob\n job_id: 8f002b46-957d-4f6c-bf1d-de7db5f890d9\n provider_job_id:\n queue_name: default\n priority: 300\n arguments:\n - Ticket\n - 207797\n executions: 0\n exception_executions: {}\n locale: en\n timezone: UTC\n enqueued_at: ‘2024-12-16T11:44:46Z’\n", last_error: nil, run_at: Mon, 16 Dec 2024 11:44:46.855000000 UTC +00:00, locked_at: Mon, 16 Dec 2024 11:44:55.249000000 UTC +00:00, failed_at: nil, locked_by: “host:ens-support-zammad-scheduler-85f5d5f88c-g4zr7 pid:16”, queue: “default”, created_at: Mon, 16 Dec 2024 11:44:46.855000000 UTC +00:00, updated_at: Mon, 16 Dec 2024 11:44:46.855000000 UTC +00:00>,

#<Delayed::Backend::ActiveRecord::Job:0x00007f1405cfc3b0 id: 402388368, priority: 300, attempts: 0, handler: "—

!ruby/object:ActiveJob::QueueAdapters::DelayedJobAdapter::JobWrapper\njob_data:\n job_class: SearchIndexJob\n job_id: 7599c147-4dad-4613-9f5f-2fffb548f4ed\n provider_job_id:\n queue_name: default\n priority: 300\n arguments:\n - User\n - 104609\n executions: 0\n exception_executions: {}\n locale: en\n timezone: UTC\n enqueued_at: ‘2024-12-16T11:44:46Z’\n", last_error: nil, run_at: Mon, 16 Dec 2024 11:44:46.866000000 UTC +00:00, locked_at: Mon, 16 Dec 2024 11:44:55.249000000 UTC +00:00, failed_at: nil, locked_by: “host:ens-support-zammad-scheduler-85f5d5f88c-g4zr7 pid:16”, queue: “default”, created_at: Mon, 16 Dec 2024 11:44:46.866000000 UTC +00:00, updated_at: Mon, 16 Dec 2024 11:44:46.866000000 UTC +00:00>, — Press enter to continue ( q to break ) —

#<Delayed::Backend::ActiveRecord::Job:0x00007f1405cfc450 id: 402388371, priority: 300, attempts: 0, handler: "—

!ruby/object:ActiveJob::QueueAdapters::DelayedJobAdapter::JobWrapper\njob_data:\n job_class: SearchIndexAssociationsJob\n job_id: 16f26e7b-4cec-4fde-8a10-62f4467535f9\n provider_job_id:\n queue_name: default\n priority: 300\n arguments:\n - User\n - 104609\n executions: 0\n exception_executions: {}\n locale: en\n timezone: UTC\n enqueued_at: ‘2024-12-16T11:44:54Z’\n", last_error: nil, run_at: Mon, 16 Dec 2024 11:44:54.499000000 UTC +00:00, locked_at: Mon, 16 Dec 2024 11:44:55.249000000 UTC +00:00, failed_at: nil, locked_by: “host:ens-support-zammad-scheduler-85f5d5f88c-g4zr7 pid:16”, queue: “default”, created_at: Mon, 16 Dec 2024 11:44:54.499000000 UTC +00:00, updated_at: Mon, 16 Dec 2024 11:44:54.499000000 UTC +00:00>,

#<Delayed::Backend::ActiveRecord::Job:0x00007f1405cfc4f0 id: 402410132, priority: 200, attempts: 0, handler: "—

!ruby/object:ActiveJob::QueueAdapters::DelayedJobAdapter::JobWrapper\njob_data:\n job_class: TransactionJob\n job_id: 5b6ec70f-b463-4cfc-8ee8-118352eda5db\n provider_job_id:\n queue_name: default\n priority: 200\n arguments:\n - object: Ticket\n object_id: 207814\n user_id: 3\n created_at:\n _aj_serialized: ActiveJob::Serializers::TimeWithZoneSerializer\n value: ‘2024-12-16T12:52:48.705511972Z’\n type: create\n article_id: 460480\n _aj_symbol_keys:\n - object\n - object_id\n - user_id\n - created_at\n - type\n - article_id\n - interface_handle: application_server\n _aj_symbol_keys:\n - interface_handle\n executions: 0\n exception_executions: {}\n locale: en\n timezone: UTC\n enqueued_at: ‘2024-12-16T12:52:48Z’\n", last_error: nil, run_at: Mon, 16 Dec 2024 12:52:48.723000000 UTC +00:00, locked_at: Mon, 16 Dec 2024 12:52:50.282000000 UTC +00:00, failed_at: nil, locked_by: “host:ens-support-zammad-scheduler-85f5d5f88c-g4zr7 pid:22”, queue: “default”, — Press enter to continue ( q to break ) — created_at: Mon, 16 Dec 2024 12:52:48.723000000 UTC +00:00, updated_at: Mon, 16 Dec 2024 12:52:48.723000000 UTC +00:00>

I am surprise to see zammad-scheduler locking ticket as we don’t use any of the functionnality from it.
Also this logs (16/12) have been taken today Tuesday 17 Dec and there is no date issue with some other log

Ex :
#<Delayed::Backend::ActiveRecord::Job:0x00007f1405cfd0d0 id: 402780115, priority: 300, attempts: 0, handler: "—

!ruby/object:ActiveJob::QueueAdapters::DelayedJobAdapter::JobWrapper\njob_data:\n job_class: SearchIndexAssociationsJob\n job_id: c87f05e9-8b06-4e66-9975-582d8cc8001b\n provider_job_id:\n queue_name: default\n priority: 300\n arguments:\n - StatsStore\n - 1152\n executions: 0\n exception_executions: {}\n locale: en\n timezone: UTC\n enqueued_at: ‘2024-12-17T13:48:28Z’\n", last_error: nil, run_at: Tue, 17 Dec 2024 13:48:28.492000000 UTC +00:00, locked_at: nil, failed_at: nil, locked_by: nil, queue: “default”, created_at: Tue, 17 Dec 2024 13:48:28.492000000 UTC +00:00, updated_at: Tue, 17 Dec 2024 13:48:28.492000000 UTC +00:00>

Also this last log is from the logs when there is the increase of Zammad Job ; and from the 20 logs that we catch ( Delayed::Job.last(20) ) they all look like that minus time stamp and id

usevgeny · December 20, 2024, 11:24am

WooooW! 2500 jobs every 11 minutes! thats wiered might be related to zammad-scheduler… id be happy to help you with your investigations. but I’d also kindly ask @MrGeneration his opinion on this subject

MrGeneration · December 20, 2024, 11:30am

Definitely at least one job that runs every 10 minutes (called Scheduler in the UI)

system · December 15, 2025, 11:31am

This topic was automatically closed 360 days after the last reply. New replies are no longer allowed.