Defines the time that a contending Content Server will wait before it will treat an archive lock file whose timestamp has not changed as having expired. The Content Server will also touch any locks it is maintaining twice during this interval.
An archive lock is created by placing a lock file into an appropriate directory. In order for the lock to persist, the timestamp on the file must change periodically; otherwise any contending Content Server will treat the lock as an expired lock.
The smaller the value of this setting, the quicker that locks can alternate between Content Servers. The larger the value, the more likely that high activity (which could keep a touch request delayed for many seconds) on the network drive will cause a Content Server to falsely report a lock as having expired. If a lock is falsely expired, it can cause duplicated effort (although it should not have any long term impact on the state of the Content Server).
The default is 12000 milliseconds (12 seconds).
As a configuration setting: