Archives
Contributors
[28984] Scaling and healing issues with Odoo.SH, any experiences /
further documentation available
Dear community of Odooers,
Odoo.SH plattform, based on a not precisely known method pauses cron
jobs.
Our analysis shows that the pause of a period T happens, if a job A
produces a certain amount of errors Y within a certain period Z of
time.
Furthermore if the load exceeds some magic threshold entire systems
seem to be shut down by the higher level VM environment causing the
Odoo Server to restart.
Especially for larger installations in productive usage this is
inacceptable. So we are wondering if this or similar behaviour is
specified and documented somewhere or others did make the same or
similar experiences with Odoo.SH.
This knowledge would be very valuable in either decide when to pull the
plug on SH or at least how to monitor and prevent those situations from
happening.
Best Frederik
P.S.: It is clear that for a cloud environment to operate properly such
measures shall be taken but at least they must clearly be documented
P.P.S: What i found was this
https://www.odoo.com/documentation/master/administration/odoo_sh/advanced/frequent_technical_questions.html
basically saying that and why they are doing it but not on the basis of
which measures
and that
https://www.odoo.com/de_DE/forum/hilfe-1/odoo-sh-performance-sizing-142865
--
Dr.-Ing. Frederik Kramer
Geschäftsführer
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
Phone: +49 4105 56156-12
Fax: +49 4105 56156-10
Mobil: +49 179 3901819
Email: frederik.kramer@initos.com
Web: www.initos.com
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155
by Frederik Kramer - 03:36 - 1 Sep 2021