RPC Inner (rpci)

Description

Service role that registers active instances of roles made redundant in Active-Passive mode. Each node in the system has an rpci client for such requests. rpci server roles are configured per site. The rpci service provides microservice addresses within the site.

Made redundant in Active-Active mode, but the first available instance is predominantly used.

Table 1. System characteristics

Code

rpci

Operation mode

Service, storage

Redundancy mode

Active-Active

Site types

All

Layer

Configuration

Placement

Internal

State preservation and recovery on restart

Yes

Application

era_rpci

Own storage

RAM table

Limitations

  • Present in the initial configuration.

  • Must be present on all sites.

Parameters

Table 2. Parameters
Name Type Default Description

name

str

required

Name. May consist of Latin letters and digits and must start with a letter.

roletype

str

required

Role type. Possible values: "rpci".

ext

json

empty

Additional role options. Contains a JSON object or list.

enabled

bool

empty

Role activity flag. When set to false, the role does not participate in validation and is not started.

limit_of_cores

int

empty

Limit on the number of CPU logical cores used. Default: 0 - unlimited.

logging_default_level

int

empty

Default logging level set specifically for the role instance (microservice type). More

allow_divergence

bool

false

Flag allowing parameter differences in roles of the same group. Default: false - not allowed.

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.

Node example
{
  "name": "rpci1",
  "roletype": "rpci"
}

See also