It is known that the lock on the database properties (option "Allow document locking") on the server, which is in ACL is marked as an Administrative (Master Lock Server), create a system repository for locks. In real distributed system without a permanent connection between the servers, having trouble: the mechanism locks works very slowly, sometimes incorrectly, when the timeout throws out an error code 4000...

 

One of the working solutions - to block or modify documents on their parent server. The find was to disable the replication of ACL (including an option "Enforce a consistent Acess Control List across all replicas"), and to set the ACL of each database on each server of the Current (Master Lock) server, it leads to the fact that on each server creates its own repository for locks - it works quickly and beautifully.

The problem is that now can not sync ACL, - have to do it manually...

 

I propose move the server setup blocking option from the ACL to the database properties, because on the one hand, it has no relation to the ACL, and the other would remove the restriction, which further enhance adjustability Lotus database for the distributed environment.