Re: [389-devel] Please review ticket 47936: Create a global lock to serialize write operations over several backends

[Ludwig Krispenz <lkrispen@xxxxxxxxxx>]

Hi,

does it make sense to allow subsets of the backends to be locked by the global lock. In our experience with deadlaocks different combinations of backends were involved - so to enable it one would have to know in advance which backends to list. I think if we introduce this global lock, make it global, it would also make the config check if it should be used faster.

If you want to keep the configuration of individual backends I would like to have one "ALL" option

Ludwig

On 02/26/2015 09:03 PM, thierry bordaz wrote:

Hello,

This fix allows to protect several backends with a global lock during update operations.
It is configurable and by default the global lock is not enabled.
Under rare condition some plugin may lead to deadlocks. Global lock would be enabled to prevent those deadlocks
during critical phases or to limit production impact during investigations.

 I will do some performance measurement with this fix.

https://fedorahosted.org/389/ticket/47936

https://fedorahosted.org/389/attachment/ticket/47936/0001-Ticket-47936-Create-a-global-lock-to-serialize-write.patch

thanks
thierry

--
389-devel mailing list
389-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-devel

--
389-devel mailing list
389-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-devel