You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we updated from Oban 2.12.1 to 2.14.2 and ObanPro 0.11.0 to 0.13.2 we are faced an issue with DynamicQueues, and the global_limit opt, from queues that already exists on Database.
We found a difference in the global_limit option structure. For example, the data from oban_queues.opts column:
Before: {"paused": null, "rate_limit": null, "local_limit": 1, "global_limit": 1}
After: {"paused": null, "rate_limit": null, "local_limit": 1, "global_limit": {"allowed": 1, "tracked": {}, "partition": null}, "retry_backoff": 1000, "retry_attempts": 5}
When we tried to run the application we got the error traces below:
The simplest way to change the schema is to declare those queues in the DynamicQueues list again. If that's not an option, then the following SQL will fix it:
update oban_queues
set opts = jsonb_set(opts, '{global_limit}', jsonb_build_object('allowed', opts->'global_limit', 'partition', null))
where opts->'global_limit'<>'null'::jsonb;
Environment
Oban Version
2.14.2
Oban Pro Version
0.13.2
PostgreSQL Version
psql (PostgreSQL) 14.5
Elixir & Erlang/OTP Versions (
elixir --version
)Current Behavior
When we updated from
Oban 2.12.1
to2.14.2
andObanPro 0.11.0
to0.13.2
we are faced an issue with DynamicQueues, and theglobal_limit
opt, from queues that already exists on Database.We found a difference in the global_limit option structure. For example, the data from
oban_queues.opts
column:Before:
{"paused": null, "rate_limit": null, "local_limit": 1, "global_limit": 1}
After:
{"paused": null, "rate_limit": null, "local_limit": 1, "global_limit": {"allowed": 1, "tracked": {}, "partition": null}, "retry_backoff": 1000, "retry_attempts": 5}
When we tried to run the application we got the error traces below:
Do you have any suggestions or already exists a migration to update old queue records?
Thank you!
Expected Behavior
Maybe a migration to update existing queue records
The text was updated successfully, but these errors were encountered: