Management

    These are the global rule configurations, which can include transaction configuration, SQL parser configuration, etc.

    1. - !TRANSACTION
    2.   defaultType: XA
    3.   providerType: Atomikos
    4. - !SQL_PARSER
    5.   sqlCommentParseEnabled: true

    /props

    These are the properties configuration. Please refer to the for more details.

    1. ds_0:
    2.   initializationFailTimeout: 1
    3.   validationTimeout: 5000
    4.   maxLifetime: 1800000
    5.   leakDetectionThreshold: 0
    6.   password: root
    7.   idleTimeout: 60000
    9.   dataSourceClassName: com.zaxxer.hikari.HikariDataSource
    10.   maximumPoolSize: 50
    11.   connectionTimeout: 30000
    12.   username: root
    13.   poolName: HikariPool-1
    14. ds_1:
    15.   initializationFailTimeout: 1
    16.   validationTimeout: 5000
    17.   maxLifetime: 1800000
    18.   leakDetectionThreshold: 0
    19.   minimumIdle: 1
    20.   password: root
    21.   idleTimeout: 60000
    22.   jdbcUrl: jdbc:mysql://127.0.0.1:3306/ds_1?serverTimezone=UTC&useSSL=false
    23.   dataSourceClassName: com.zaxxer.hikari.HikariDataSource
    24.   connectionTimeout: 30000
    26.   poolName: HikariPool-2

    /metadata/${databaseName}/versions/${versionNumber}/rules

    Rule configurations, including sharding, read/write splitting, data encryption, and shadow DB configurations.

    Use separate node storage for each table, dynamic modification of metadata content is not supported currently.

    1. name: t_order                             # Table name
    2. columns:                                  # Columns
    3.   id:                                     # Column name
    4.     caseSensitive: false
    5.     dataType: 0
    6.     generated: false
    7.     name: id
    8.     primaryKey: trues
    9.   order_id:
    10.     caseSensitive: false
    11.     dataType: 0
    12.     generated: false
    13.     name: order_id
    14.     primaryKey: false
    15. indexs:                                   # Index

    /nodes/compute_nodes

    The identifiers are temporary nodes, which are registered when instances are online and cleared when instances are offline. The registry center monitors the change of those nodes to govern the database access of running instances and other things.

    It can orchestrate replica database, and delete or disable data dynamically.