Storage (st)
Description
Universal site storage. Used by various roles as an internal service.
Made redundant in Active-Passive mode. Scaled by splitting into groups by key hash sums.
Code |
|
Operation mode |
|
Redundancy mode |
|
Site types |
|
Layer |
|
Placement |
|
State preservation and recovery on restart |
|
Application |
|
Own storage |
|
Limitations
-
Present in the initial configuration.
-
Must be present on every site.
-
If the role is unavailable, most services do not function, including system startup.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
|
|
required |
Name. May consist of Latin letters and digits and must start with a letter. |
|
|
required |
Role type. Possible values: |
|
|
empty |
Additional role options. Contains a JSON object or list. |
|
|
empty |
Role activity flag. When set to false, the role does not participate in validation and is not started. |
|
|
empty |
Limit on the number of CPU logical cores used. Default: 0 - unlimited. |
|
|
empty |
Default logging level set specifically for the role instance (microservice type). More |
|
|
|
Flag allowing parameter differences in roles of the same group. Default: false - not allowed. |
|
|
required |
Group number. |
|
|
required |
Order of the role instance within the group. |
|
|
|
Object storage operation mode.
|
|
|
global |
Takeover mode switch.
|
Configuration example
Configuration management is performed in an application available to master domain administrators. The application hides the full configuration content, but it is still available through the API.
The configuration contains a section describing all instances of all roles. Parameters are defined for each specific role instance.
{
"st1": {
"name": "store1",
"roletype": "st",
"group": "11080",
"order": "1"
}
}