Skip to content
This repository was archived by the owner on Oct 3, 2025. It is now read-only.

Conversation

@PeterC10
Copy link

  • There has been instances where an Odoo worker has exceeded the soft memory limit after a low level error (e.g. PSQL constraint) the new worker created carried over the same virtual memory
  • The above meant that the worker was killed instantly and this would repeat until the workers were manually killed and Odoo restarted
  • By raising an exception in this case, the Odoo worker will explicitly exit, with the new worker being created without carrying over any reserved memory

@PeterC10 PeterC10 force-pushed the 11.0_DM-614_force_worker_exit branch from cfa67cb to a43a1c8 Compare April 24, 2024 12:49
…quests

* There has been instances where an Odoo worker has
  exceeded the soft memory limit after a low level error
  (e.g. PSQL constraint) the new worker created carried
  over the same virtual memory
* The above meant that the worker was killed instantly
  and this would repeat until the workers were manually
  killed and Odoo restarted
* By raising an exception in this case, the Odoo worker
  will explicitly exit, with the new worker being created
  without carrying over any reserved memory
@PeterC10 PeterC10 force-pushed the 11.0_DM-614_force_worker_exit branch from a43a1c8 to 7f39a65 Compare April 24, 2024 12:49
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants