solidDB Help : solidDB reference : Server-side configuration parameters : Grid section
  
Grid section
The following table describes the parameters that can be used in the [Grid] section of the server-side solid.ini file.
For a description of the access modes, see Access mode and persistence of parameter modifications.
 
[Grid]
Description
Factory value
Access mode
AvailabilityManagerActionsEnabled
If set to no, grid availability manager actions are disabled, see Grid Availability Manager.
yes
RW
DDLSyncTimeout
Maximum wait time (in seconds) before DDL synchronization times out.
DDL statements such as ALTER TABLE, DROP TABLE, DROP SCHEMA, and DROP CATALOG, are executed as synchronously replicated transactions on all nodes in a grid. Therefore, before executing the transaction, the grid leader must wait until all nodes have acknowledged that the associated tables are locked.
60
RW
DistributedReadMaxBlobSize
Maximum BLOB size (in bytes) that can be supported in a distributed read query.
Follow the value with K (to specify a value in KB) or M (to specify a value in MB).
2M
RW
DistributedReadThreadCount
Number of threads available to a distributed read query.
16
RW/
Startup
GridEnabled
If GridEnabled is set to yes, the server can act as a grid node.
no
RO
RaftElectionTimeout
Maximum interval (in milliseconds) within which subsequent heartbeats must arrive from the leader.
A random value between the time set (T) and 2T is selected (in order to avoid split votes in the election).
Minimum value is 2 x RaftHeartbeatTimeout.
If the election timeout elapses, the node moves to candidate state and starts a new leader election.
300
RW
RaftHeartbeatTimeout
Maximum interval (in milliseconds) within which the leader must receive subsequent heartbeats from each follower or candidate.
When the heartbeat timeout elapses, the leader moves the node to suspicious state (the node has no participation in voting or commits).
The default heartbeat timeout value is 1/3 of the election timeout because each follower has less load than the leader and so should usually respond more quickly than the leader.
Maximum value is 1/2 x RaftElectionTimeout.
100
RW
RaftLeaderStickinessEnabled
If set to yes, ‘leader stickiness’ is enabled in the grid.
For an explanation of ‘leader stickiness’, see solidDB consensus algorithm.
yes
RW
RaftPreVoteEnabled
If set to yes, ‘pre-voting’ is enabled in the grid.
For an explanation of ‘pre-voting’, see solidDB consensus algorithm.
yes
RW
RaftReElectionTimeout
Maximum duration (in milliseconds), by which vote responses must arrive from all voters to a candidate.
A random value between the time set (T) and 2T is selected (in order to avoid split votes in the re-election).
If the re-election timeout elapses, the node remains in candidate state and restarts the leader election.
50
RW
Go up to
Server-side configuration parameters