## Begin of the insertionDecision

OpenProject will migrate to GoodJob (https://github.com/bensheldon/good\_job)

##End of the insertion Requirements

An ideal replacement would also fulfil the following requirements.

**Multi queue workers with priorities**

Scenario:

* 3 workers
* 1 worker that has a lot of RAM and storage
* 2 workers only get little RAM
* the 2 workers shall be used for small tasks such as sending emails
* the 1 worker shall be used for expensive tasks such as work package exports or backups
* it should be able to handle the cheap jobs as a fallback if there are no expensive jobs available
* the small workers should not attempt these expensive jobs
* info: delayed\_job does not support this

**Bonus: avoid orphaned jobs**

With delayed\_job it can happen that a worker is killed, either during a deployment or due to exceeding the allowed memory usage. In that case the job becomes orphaned and will not be picked up again even after a restart.

An ideal replacement would be able to handle this scenario some way.

Begin of the insertion>End of the insertion ## Begin of the insertionPreviously:End of the insertion Candidates Begin of the insertion
>
>End of the insertion Begin of the deletion

End of the deletion <img class="op-uc-image op-uc-image_inline" style="width:888px;" src="https://community.openproject.org/api/v3/attachments/59146/content"> Begin of the insertion
>
>End of the insertion Begin of the deletion

End of the deletion 1. Popularity.
Begin of the insertion>End of the insertion 2. Rails integration.
Begin of the insertion>End of the insertion 3. Complexity.
Begin of the insertion>End of the insertion 4. Maintainability.
Begin of the insertion>End of the insertion 5. Save resources/Make more scalable.
Begin of the insertion>End of the insertion 6. Have a fancy dashboard :) Begin of the insertion
>
>End of the insertion Begin of the deletion

End of the deletion * DelayedJob Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 1. Not actively developed for years. Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 2. +/- Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 3. Begin of the insertion
>
> End of the insertion Begin of the deletion

End of the deletion 4. We have a couple of modification that have to be maintained. Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 1. Cron jobs scheduling Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 2. Job statuses. Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 5. Process-based. So, need more RAM to scale. Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 6. Not present
Begin of the insertion>End of the insertion * Sidekiq Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 1. Popular and actively developed. Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 2. Some part of sidekiq API is not supported by ActiveJob. Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 3. Complexity will increase significantly. Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 1. Redis as a new dependency to take care of. Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 2. Backup functionality will become more complex. Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 1. saas-openproject Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 2. openproject Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 4. Maintainability will decrease due to complexity increasing :) Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 5. \+ because of multi threading Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 6. Present
Begin of the insertion>End of the insertion * GoodJob Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 1. Quite popular and actively developed. Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 2. Positioned as fully compatible with ActiveJob. Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 3. Complexity will stay on the same level at least. Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 1. Backup functionality stays the same, because jobs are stored inside PostgreSQL Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 4. Maintainability will increase. Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 1. Cron functionality should become more simple, because library is responsible for scheduling and controlling recurrent jobs. Our job is to provide a schedule. So, some of our code will be removed. Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 2. Job status stays the same for now. Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 5. \+ because of multi threading Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion 6. Present Begin of the insertion
>
>End of the insertion Begin of the deletion

End of the deletion ### Prototype scripts for backing up part of the keys from Redis: Begin of the insertion
>
>End of the insertion Begin of the deletion

End of the deletion * Backup Begin of the insertion
>
>End of the insertion Begin of the deletion

End of the deletion ```ruby
Begin of the insertion>End of the insertion require 'benchmark'
Begin of the insertion>End of the insertion redis = RedisClient.new(host: 'redis')
Begin of the insertion>End of the insertion backup_script = <<~LUA Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion local result = {} Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion result['apartment'] = ARGV[1] Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion result['queues'] = {} Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion local queues = redis.call('KEYS', 'queue:*') Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion for index, queue in ipairs(queues) do Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion result['queues'][queue] = {} Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion local jobs_encoded = redis.call('LRANGE', queue, 0, -1) Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion for index, job_encoded in ipairs(jobs_encoded) do Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion local job_decoded = cjson.decode(job_encoded) Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion if job_decoded['args'][1]['schema_name'] == ARGV[1] then Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion table.insert(result['queues'][queue], job_decoded) Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion end Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion end Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion end Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion return cmsgpack.pack(result)
Begin of the insertion>End of the insertion LUA
Begin of the insertion>End of the insertion puts Benchmark.measure { Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion $backup_string = redis.call("EVAL", backup_script, 0, 'public')
Begin of the insertion>End of the insertion }
Begin of the insertion>End of the insertion ``` Begin of the insertion
>
>End of the insertion Begin of the deletion

End of the deletion * Restore Begin of the insertion
>
>End of the insertion Begin of the deletion

End of the deletion ```ruby
Begin of the insertion>End of the insertion require 'benchmark'
Begin of the insertion>End of the insertion redis = RedisClient.new(host: 'redis', timeout: 10)
Begin of the insertion>End of the insertion restore_script = <<~LUA Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion local backup_string = ARGV[1] Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion local backup_decoded = cmsgpack.unpack(backup_string) Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion local apartment = backup_decoded['apartment'] Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion local queues = redis.call('KEYS', 'queue:*') Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion for index, queue in ipairs(queues) do Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion local jobs_encoded = redis.call('lrange', queue, 0, -1) Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion for index, job_encoded in ipairs(jobs_encoded) do Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion local job_decoded = cjson.decode(job_encoded) Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion if job_decoded['args'][1]['schema_name'] == apartment then Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion redis.call('lrem', queue, 1, job_encoded) Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion end Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion end Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion end Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion for queue, jobs in pairs(backup_decoded['queues']) do Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion for index, job in ipairs(jobs) do Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion redis.call('LPUSH', queue, cjson.encode(job)) Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion end Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion end Begin of the insertion
> End of the insertion Begin of the deletion
End of the deletion return true
Begin of the insertion>End of the insertion LUA
Begin of the insertion>End of the insertion puts Benchmark.measure { redis.call("EVAL", restore_script, 0, $backup_string) }
Begin of the insertion>End of the insertion ```