st_volume_set_forced_red_level
If a redundancy level is forced, every operation is redirected to the redundancy segment that represents that level.
In case of write operations, no redundancy data is written (since you write directly on a redundancy segment that
does not have other redundancy segments). This is a debug function, so use it with caution!
If the forced redundancy level is set within an operation property (stopprop), the redundancy level will then
overwrite the one that has been set using this function (for that particular operation).
Mandatory parameters
| Parameter name | Data type | Description |
|---|---|---|
| vid | integer | Volume ID |
| force_red_level | integer | Forced_red Level of redundancy that should be used for reading/writing. Level 1 selects the master segment. Example: it enables the 'normal' behaviour, including red. write operations and automatic recovery (copy-on-demand) for read operations. A higher level selects the corresponding redundancy segment. |
Optional parameters
| Parameter name | Data type | Description |
|---|---|---|
| vname | string | Name of an existing volume |
Substitute parameters
The following table describes what parameters can be substituted for another parameter.
| Parameter name | Substitute parameter |
|---|---|
| vid | vname |
| vname | vid |
Allowed users
There are no defined allowed users.
Allowed groups
The following groups are allowed to run this job:
- root
Examples
The following examples show how to run this job in a Python program using XML-RPC or on the command line using confd_client.
Python using XML-RPC