"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "src/imm/README" between
opensaf-5.21.06.tar.gz and opensaf-5.21.09.tar.gz

About: OpenSAF is a project focused on Service Availability (SA) that develops middleware based on open and industry standard interfaces for applications requiring uninterrupted 24x7 service.

README  (opensaf-5.21.06):README  (opensaf-5.21.09)
skipping to change at line 3031 skipping to change at line 3031
Bit 2 controls OpenSAF4.1 protocols allowed or not (normally on/1). Bit 2 controls OpenSAF4.1 protocols allowed or not (normally on/1).
Bit 3 controls OpenSAF4.3 protocols allowed or not (normally on/1). Bit 3 controls OpenSAF4.3 protocols allowed or not (normally on/1).
Bit 4 controls 2PBE oneSafe2PBE, see 2PBE feature in OpenSAF4.4 above (normally off/0). Bit 4 controls 2PBE oneSafe2PBE, see 2PBE feature in OpenSAF4.4 above (normally off/0).
Bit 5 controls OpenSAF4.5 protocols allowed or not (normally on/1). Bit 5 controls OpenSAF4.5 protocols allowed or not (normally on/1).
Bit 6 controls OpenSAF4.6 protocols allowed or not (normally on/1). Bit 6 controls OpenSAF4.6 protocols allowed or not (normally on/1).
Bit 7 controls OpenSAF4.7 protocols allowed or not (normally on/1). Bit 7 controls OpenSAF4.7 protocols allowed or not (normally on/1).
Bit 8 controls OpenSAF5.0 protocols allowed or not (normally on/1). Bit 8 controls OpenSAF5.0 protocols allowed or not (normally on/1).
Bit 9 controls OpenSAF5.1 protocols allowed or not (normally on/1). Bit 9 controls OpenSAF5.1 protocols allowed or not (normally on/1).
Bit 10 controls OpenSAF5.17.11 protocols allowed or not (normally on/1). Bit 10 controls OpenSAF5.17.11 protocols allowed or not (normally on/1).
Bit 11 controls OpenSAF5.19.07 protocols allowed or not (normally on/1). Bit 11 controls OpenSAF5.19.07 protocols allowed or not (normally on/1).
===================================================================
https://sourceforge.net/p/opensaf/tickets/3268/
In a large cluster (e.g, 24 nodes), the components have very often been
timeout in the single step upgrade. To prevent timeout in this case,
Operator need to increase the MDS wait time for all clients in cluster.
Technically the IMMA_SYNC_TIMEOUT environment variable can be exported with
appropriate value in each components on every nodes. However, the cluster
has several nodes, each of which has hundreds of components.
This enhancement introduce a configurable attribute `saImmSyncrTimeout`
to `SaImmMngt` class. This attribute represents the current MDS wait
time of IMM clients. It has 0 (disable this feature) by default and
a valid value is within the range [NCS_SAF_MIN_ACCEPT_TIME(10) - INT64_MAX].
The unit of value is 10 milliseconds.
IMMND will distribute new timeout to all IMM clients when there is a change.
When deleting value of attribute `saImmSyncrTimeout`, it will go back
to default value (0) then force all IMM clients restore to old value.
---------------------------------------- ----------------------------------------
DEPENDENCIES DEPENDENCIES
============ ============
immsv depends of the following other services: immsv depends of the following other services:
- NID - NID
- MBCSV - MBCSV
- MDS - MDS
- BASE - BASE
- AMF - AMF
 End of changes. 1 change blocks. 
0 lines changed or deleted 19 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)