From 147a26d9583c09c27dbe0b0ee06efe6e6cc8620d Mon Sep 17 00:00:00 2001 From: Victor Seva Date: Mon, 23 Nov 2015 12:04:40 +0100 Subject: [PATCH] Revert "rtpengine: Update doku for node enable/disable" This reverts commit fefe1e63a175ce475a44ae11bb89929e5c5f67d3. --- modules/rtpengine/doc/rtpengine_admin.xml | 32 ----------------------- 1 file changed, 32 deletions(-) diff --git a/modules/rtpengine/doc/rtpengine_admin.xml b/modules/rtpengine/doc/rtpengine_admin.xml index 2454db2aa05..bcb1c030ea4 100644 --- a/modules/rtpengine/doc/rtpengine_admin.xml +++ b/modules/rtpengine/doc/rtpengine_admin.xml @@ -73,38 +73,6 @@ If the set was selected using setid_avp, the avp needs to be set only once before rtpengine_offer() or rtpengine_manage() call. - - From the current implementation point of view, the sets of rtpproxy nodes - are shared memory(shm), so all processes can see a common list of nodes. - There is no locking when setting the nodes enabled/disabled (to keep the - memory access as fast as possible). Thus, problems related to node state - might appear for concurent processes that might set the nodes - enabled/disabled(e.g. by fifo command). This robustness problems are overcomed as follows. - - - - If the current process sees the selected node as disabled, the node is - force tested before the current process actually - takes the disabled decision. If the test succeeds, the process will set - the node as enabled (but other concurrent process might still see it as disabled). -. - - - - If the current process sees the selected node as enabled, it does no additional checks - and sends the command which will fail in case the machine is actually broken. - The process will set the node as disabled (but other concurrent process might still see it as enabled). - - - - The 'kamctl fifo' commands (including rtpengin ones) are executed by an exclusive - process which operate on the same shared memory node list. - - - - All the nodes are pinged in the beginning by all the processes, - even if the node list is shared memory. -