Grid Create Configuration Options
The following configuration options can be used with the tibdg grid create command.
| Option | Description | Default Value | Valid Values |
|---|---|---|---|
| checkpoint_interval | The interval, in seconds, between periodic checkpoints. The default value of 0.0 seconds disables periodic checkpoints. | 0.0 | |
| checkpoint_retention_limit | The number of checkpoints (manual and periodic) to keep at a time. When the total number of checkpoints (manual and periodic) on disk exceeds the
checkpoint_retention_limit, the oldest checkpoint is deleted.
The default value of 0 indicates that all checkpoints should be kept. To determine the proper setting for this option, multiply the checkpoint_retention_limit by the checkpoint_interval. This value indicates the duration in seconds a checkpoint is retained. This option should typically be set to a small number to avoid excessive disk usage. |
0 | Minimum: 0 |
| client_req_timeout | The time (in seconds) the client API synchronously waits for completion of a request (such as GET or PUT operation), before timing out. | 5.0 | Minimum: 0.0 |
| compaction | A value less than six indicates more emphasis on performance and less on the compaction of the disk space.
Conversely, a higher value indicates more emphasis on the compaction of the disk space than performance. |
7 | Minimum:
0
Maximum: 10 |
| consistent_query_limit | The maximum number of iterators and statements (queries) that a node can handle concurrently. | 64 | Minimum: 1 |
| copyset_size | The number of nodes in a copyset. | 2 | Minimum: 1 |
| encrypted_connections | Specifies which connections in the data grid get encrypted. | none | all or none |
| expiration_scanner_max_rows | Determines the maximum number of rows that are expired each time a table is scanned for expired rows. | 1000000 | Minimum: 1 |
| expiration_scanner_wakeup | Determines how frequently the leader of each copyset scans a table for rows to expire. The unit of measurement is in seconds. | 5 | Minimum: 1 |
| full_table_scans | Defines the behavior when processing a query that requires a full table scan. This option takes ones of the following values:
|
warn | warn
enable disable |
| grid_internal_subnet_mask | See Configure Internal Subnet Masks. | none | See Configure Internal Subnet Masks. |
| iter_inactivity_timeout |
The time, in seconds, taken by the proxy to wait for the next client request on a table iterator or statement query before automatically closing the table iterator or statement query. |
600.0 | Minimum: 0.0 |
| minimum_replication_factor | The minimum number of nodes (including the primary and any secondary nodes) in a copyset that must be in an Alive state before WRITE operations are allowed. | 1 | Minimum: 1 |
| mirroring_max_batch_size_rows | The maximum rows in a batch that is mirrored collectively to the mirror grid. This size should be an integer >=1. It can typically be left at the default value unless transport loss is seen during mirroring operations. If transport loss is experienced during mirroring, this value should be reduced. | 256 | |
| mirroring_interval | The default mirroring interval (in seconds). This option determines how frequently a mirror grid checks for new checkpoints to be mirrored. Setting this option to 0 disables mirroring. | 30.0 | |
| node_detailed_stats_collection | Retrieves detailed statistics of a node configuration. The option can take one of the following values:
enable or
disable.
When this option is enabled, the nodes enable extra statistics collection around all disk operations. The statistics can be retrieved by using the tibdg node status command. Additionally, these statistics are logged to the node log at the status:verbose level once every 60 seconds. Enabling node_detailed_stats_collection results in a 5-10% performance penalty. node_detailed_stats_collection is disabled by default. |
disable | |
| node_read_cache_size |
Every node, stores a read cache that holds uncompressed blocks of data in memory. The size of a read cache is specified in bytes. There are some memory usage considerations to be made when using this option. For details, see Memory Usage Considerations with the node_read_cache_size Option. |
1073741824 (1 gigabyte) | Minimum:
0
Maximum: 9223372036854775806 (LLONG_MAX - 1) |
| node_storage_timeout | The time (in seconds) a node waits for a successful response from a READ or WRITE operation to complete before timing it out. | 60 | Minimum: 0 |
| proxy_client_listen_external_host | The host name or the IP address that external clients connect to when attempting to reach a proxy. See Configuration Options when the Proxy and Client are on Different Subnets. | none | |
| proxy_client_listen_external_port | This is the default port that external clients connect to when attempting to reach a proxy. See Configuration Options when the Proxy and Client are on Different Subnets. | none | |
| proxy_client_listen_subnet_mask | See Configure Network Interfaces | none | See Configure Network Interfaces. |
| proxy_client_listen_port | See Configure Ports. | none | See Configure Ports. |
| statekeeper_count | The number of state keeper processes expected to be run.
Due to the requirement that state keepers must be run in a quorum, the supported values are 1 or 3. |
3 | Minimum: 1 |