2.2.3. Cluster services
All server cluster manager features are broken down into several independent services. Each service has specific characteristics. You can view the list of services, their brief description and characteristics below:
Service | Description | Characteristics |
Object locks | Stores pessimistic (not transaction-based) object locks. | Memory Replication Migration+ Instancing by infobases |
External session management | Controls creation of sessions that require client licenses. | Migration+ Instancing by infobases |
Time | Supports getting real-time timestamps and some auxiliary functions. | Replication Migration+ Instancing by infobases |
Auxiliary cluster functions | Manages cluster lock information collection. | No migration |
Data Accelerator | Allows creating data copies for high-speed preparation of analytical reports. Service works together with data base copies mechanism. | Memory Disk Migration- |
Event logs | Supports access to event logs. | Disk Migration- Instancing by infobases |
Jobs | Starts and monitors lifetime of background and scheduled jobs. | Replication Migration+ |
Integration data | Ensures operation of integration services. | Instancing by infobases No migration |
Cluster configuration | Stores all cluster settings. | No migration Replication |
Full-text search coordination v2 | The service allows you to divide storage and maintenance of the search index between cluster managers. | Migration- Instancing by infobases |
Licensing | Provides software license distribution. If the cluster licensing service that had issued licenses earlier is temporarily unavailable, this service issues duplicate licenses for no longer than 20 seconds. To ensure uninterrupted license acquisition from the licensing service, the rphost and rmngr processes of 1C:Enterprise server must have rights to create, read, and modify data in the 1cv8conn.pfl file. | Migration+ |
Resource consumption counter monitoring | Calculates values of resource consumption indicators. | Disk Memory Migration- |
Numbering | Generates unique object numbers and codes. | Replication Migration+ Instancing by infobases |
Database table/field numbering | Provides unified numbering for database tables and fields. Used during database configuration updates that involve changes in database structure. | Migration+ Instancing by infobases |
Session reuse | Provides an automatic pool of reused sessions for Web services, HTTP services, and OData. | Migration+ |
Full-text search | Performs full-text search and indexing. | Disk Migration- Instancing by infobases |
Full-text search v2 | The service is responsible for full-text search and indexing management: start on demand, start on a schedule, and information about the index status. | Disk Migration- Instancing by infobases |
Getting a list of sessions | Allows you to get a list of current sessions using various platform features, including internal cluster features, 1C:Enterprise language objects, and administration tools. | Migration+ |
Custom settings | Provides access to files storing custom settings. | Migration- Instancing by infobases |
OpenID provider | Stores OpenID authentication contexts. | Migration- Instancing by infobases |
ODBC external data source management | Provides interaction with external databases over ODBC interface. | Memory Migration+ Instancing by infobases |
External data source management using XMLA | Provides interaction with OLAP sources over XMLA interface. | Migration- Instancing by infobases |
Session data | Provides storage and caching of session information, for example, information in managed application forms. Provides client license acquisition. | Disk Replication Migration+ Instancing by infobases |
Speech recognition service | Enables speech recognition. Receives (downloads) speech recognition models from an external model source (a recognition server). | Disk Memory Single server |
Service for managing speech recognition models | Stores speech recognition models and distributes them among other production servers. | Disk Single server |
Cluster state | Contains dynamic data about cluster state and composition. | Replication No migration |
Testing | Simulates user operations with 1C:Enterprise cluster. | Migration- |
Transaction locks | Contains transaction locks for managed mode. | Memory Migration+ Instancing by infobases |
Debug item management | Manages debugger connection to server debug items. | No migration |
Background database configuration update | Performs background database restructuring. Before migrating this service between cluster managers, stop all working process. The system background job must be stopped as well. Therefore, the background update will be paused immediately after migration. | Replication Migration+ Instancing by infobases |
Binary data storages | Maintains the operation of the binary data storage service. | Disk Migration- |
Terms used in the table:
- Disk. Resource-intensive service that causes high load on the disk subsystem.
- Memory. Resource-intensive service that causes high load on CPU and RAM.
- Replication. Replication between the main and reserve service instances is supported. Replication is activated whenever the fault-tolerance level of the cluster is not zero. For cluster configuration and cluster lock services, replication is activated whenever multiple working servers with selected Main server check box are registered in the cluster.
- Instancing by infobases. A separate service instance is used for each infobase.
- Migration between working servers:
- Migration+. Service migration between working servers is possible without any data loss.
- Migration–. Service migration between working servers is possible with some data loss.
- No migration. Service migration between working servers is impossible. Service can be located only on the computer hosting a main server of the cluster. Functionality assignment rules cannot be created for such services.
- Single server. Service migration between production servers is unavailable. The service can be located on any single production server, not only on the main server.
Cluster services are evenly distributed among working servers of the cluster by service types, infobases, and sessions.