This module provides a generic database clustering system. It can be used as a middle layer between modules and database connectors. Via clustering, database operations can be executed across multiple servers, based on policies such as parallel write, serial or round robin write and read. The following database commands are considered to be write operations: INSERT, DELETE, UPDATE, REPLACE, INSERT-DELAYED, INSERT-UPDATE, INSERT-ASYNC. The read operations are done for database commands: QUERY and RAW-QUERY. Note: if INSERT-ASYNC is not implemented by DB connector module, then standard INSERT operation is done.
| Parámetro | Tipo | Descripción |
|---|---|---|
| connection | str | 3.2. cluster (str) 3.3. inactive_interval (int) 3.4. max_query_length (int) |
| cluster | str | 3.3. inactive_interval (int) 3.4. max_query_length (int) |
| inactive_interval | int | 3.4. max_query_length (int) |
| max_query_length | int | 3.1. connection (str) |
| connection | str | Specify the connection to a real database system. The format is 'conid=>DBURL' - providing a connection id and the database URL used by the database driver used. |
| cluster | str | Specify the cluster definition. The format is 'clsid=>conid1=def1;conid2=def2' - providing a cluster id and the list of database connections to be used. For each connection you have to provide a usage |
| inactive_interval | int | How long (seconds) a connection is considered inactive after a DB operations failed on it. |
| max_query_length | int | How long (seconds) a failed db operation needs to last before deactivating the connection for inactive_interval seconds. This prevents disabling of connections that reply fast with error codes, thus b |
Copyright © 2012 asipto.com
