2 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
3 .. http://creativecommons.org/licenses/by/4.0
12 The no-locking feature allows applications to use a Lock Manager that always succeeds. It does not deny
13 acquiring resource locks.
15 To utilize the no-locking feature, first stop policy engine, disable other locking features, and then enable it
16 using the "*features*" command.
18 In an official OOM installation, place a script with a .pre.sh suffix:
21 :caption: features.pre.sh
24 sh -c "features disable distributed-locking"
25 sh -c "features enable no-locking"
31 oom/kubernetes/policy/components/policy-drools-pdp/resources/configmaps
34 and rebuild the policy charts.
36 At container initialization, the distributed-locking will be disabled, and the no-locking feature will be enabled.