diff options
Diffstat (limited to 'docs/drools')
| -rw-r--r-- | docs/drools/feature_nolocking.rst | 38 | ||||
| -rw-r--r-- | docs/drools/pdpdEngine.rst | 1 |
2 files changed, 39 insertions, 0 deletions
diff --git a/docs/drools/feature_nolocking.rst b/docs/drools/feature_nolocking.rst new file mode 100644 index 00000000..5399f8b0 --- /dev/null +++ b/docs/drools/feature_nolocking.rst @@ -0,0 +1,38 @@ + +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 + +******************* +Feature: no locking +******************* + +.. contents:: + :depth: 3 + +The no-locking feature allows applications to use a Lock Manager that always succeeds. It does not deny +acquiring resource locks. + +To utilize the no-locking feature, first stop policy engine, disable other locking features, and then enable it +using the "*features*" command. + +In an official OOM installation, place a script with a .pre.sh suffix: + + .. code-block:: bash + :caption: features.pre.sh + #!/bin/sh + + sh -c "features disable distributed-locking" + sh -c "features enable no-locking" + + +under the directory: + + .. code-block:: bash + oom/kubernetes/policy/components/policy-drools-pdp/resources/configmaps + + +and rebuild the policy charts. + +At container initialization, the distributed-locking will be disabled, and the no-locking feature will be enabled. + +End of Document diff --git a/docs/drools/pdpdEngine.rst b/docs/drools/pdpdEngine.rst index 360d85eb..d19eac15 100644 --- a/docs/drools/pdpdEngine.rst +++ b/docs/drools/pdpdEngine.rst @@ -783,6 +783,7 @@ unnecessary or have not been thoroughly tested: feature_sesspersist.rst feature_statemgmt.rst feature_testtransaction.rst + feature_nolocking.rst Data Migration ============== |