Hi folks! Recently I faced a pretty sad fact that in Nailgun there’s no common approach to manage transactions. There are commits and flushes in random places of the code and it used to work somehow just because it was all synchronous.
However, after just a few of the subcomponents have been moved to different processes, it all started producing races and deadlocks which are really hard to resolve because there is absolutely no way to predict how a specific transaction is managed but by analyzing the source code. That is rather an ineffective and error-prone approach that has to be fixed before it became uncontrollable. Let’s arrange a discussions to design a document which will describe where and how transactions are managed and refactor Nailgun according to it in 7.0. Otherwise results may be sad. - romcheg
signature.asc
Description: Message signed with OpenPGP using GPGMail
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
