Property (Cluster)

CLUSTER_LINK_BUFFER_SIZE

The size of the send / receive buffer.

If this size is insufficient, the transmission will retry until the buffer is empty.

The default value is 32M.

CLUSTER_LINK_SEND_RETRY_COUNT

Number of times to retry sending until the send buffer is empty.

Every retry will take 1ms off. If you retry beyond this number, you will be disconnected.

The default value is 5000 (msec).

CLUSTER_LINK_HOST

Host name of the current Node to connect to a specific Node and Cluster Socket

CLUSTER_LINK_LONG_TERM_CALLBACK_INTERVAL

If the execution time of Receive Callback to process a message received on Cluster Socket exceeds the set value, it is recognized as Long-Term Callback. 
Since the number of receive Threads is limited, Receive Callback should not process messages for a long time. 
If Receive Callback processes the message after this time, it recognizes it as Long-Term Callback and records it in Trace Log.
The default value is 1 second.

CLUSTER_LINK_LONG_WAIT_INTERVAL

If the time until the arrival of a message received on Cluster Socket exceeds the set value, it is recognized as Long-Wait Message.
If the time from receiving start to receiving end is long, it can be regarded as a problem of the network environment. 
If the received message does not arrive after this time, it is recognized as a Long-Wait Message and recorded in the Trace Log.
The default value is 1 second.

CLUSTER_LINK_MAX_LISTEN

The maximum number of Socket's Accept Queue when connecting to a specific Node

CLUSTER_LINK_MAX_POLL

The maximum number of Events that can be retrieved at a time by Poll when communicating with a specific node

CLUSTER_LINK_PORT_NO

The port number of the current Node for connecting the specific Node to the Cluster Socket

CLUSTER_LINK_RECEIVE_TIMEOUT

Timeout until the Timeout Thread determines that the connection has been disconnected since the last reception
Connections that exist in the 'Linked List' should be continuously receiving because the connection between Cluster Nodes is terminated when the reception is complete.
If the last received time is not updated after the set time has elapsed, the Timeout Thread records its contents in the Trace Log and closes the Socket.

CLUSTER_LINK_REQUEST_TIMEOUT

Timeout from when a request message is sent from the Cluster Socket to when a response to the request is received
For specific messages, specify the time to wait for a response after the request. 
If the response message does not arrive at this time, write to the Trace Log and close the Socket.
The default value is 60 seconds,  and the Timeout is long because it is not known what kind of message and receive processing will happen.

CLUSTER_LINK_SEND_TIMEOUT

Timeout to set when sending messages through Cluster Socket
Set the corresponding timeout when transmitting 
If transmission is not completed until Timeout,  it is recorded in the Trace Log.

CLUSTER_LINK_SESSION_TIMEOUT

Timeout until the Timeout thread determines that the connection has been disconnected since the last receive in a specific session.
Cluster connection manages the session of all messages internally, which is a necessary property in case the session can suddenly not be fixed. 
If the last receive time for the session is not updated after this time, the Timeout Thread writes to the Trace Log and closes the session.
The default value is 1 hour.

CLUSTER_LINK_THREAD_COUNT

The number of Threads to process the received messages when communicating with a specific Node
If the size of the Cluster grows or the number of operations to be processed increases, the number of Threads that can be received increases.

CLUSTER_QUERY_STAT_LOG_ENABLE

Outputs statistical information about the executed query to the trace log.

CLUSTER_REPLICATION_BLOCK_SIZE

The size of the data to be sent at once when the Replication for adding Node is performed in the Cluster Edition
The Property must be applied directly to the warehouse (=Transmitting Warehouse) that becomes the Replication Active.
The default value is 640 KB.

CLUSTER_WAREHOUSE_DIRECT_DML_ENABLE

It is made possible to connect directly to the Warehouse to perform DML in Cluster Edition.

• 1: Executable
• 2: Not executable. An error is returned.

When directly performing the DML in Warehouse, there are performance advantages over Brokers but  there is an issue where the DML is not propagated to the same Group. 
Therefore, it is used only for emergency recovery due to data discrepancies, or if the data discrepancies of the Group can be taken into account.
You must apply Properties directly to the specific Warehouse you want.
The default value is 0.

COORDINATOR_DBS_PATH

Specifies the directory where the Coordinator data file will be created
The default value is set to ?/dbs, and ? is replaced with the $ MACHBASE_COORDINATOR_HOME environment variable. 
This is an environment variable $MACHBASE_COORDINATOR_HOME/dbs directory.
It must be applied to the Coordinator, and it has no effect on other Nodes.

COORDINATOR_DDL_REQUEST_TIMEOUT

Timeout until the Coordinator waits after requesting the Node to execute DDL
This value refers to the time the Coordinator waits after requesting each Node to perform DDL.

COORDINATOR_DDL_TIMEOUT

Timeout until the Broker waits after requesting Coordinator to perform DDL through CC
This value refers to the time that the Broker waits after requesting the Coordinator to perform DDL for the entire Cluster.

COORDINATOR_DECISION_DELAY

Timeout until the Coordinator requests the status change and effectively reflects it.
If the status does not actually change over this time, disable the cluster status. 
If the status of the Warehouse Active is not changed but the connected Standby exists, the Fail-Over operation starts.

COORDINATOR_DECISION_INTERVAL

Time to determine how often the Coordinator changes status

COORDINATOR_HOST_RESOURCE_COLLECT_INTERVAL

Interval at which Cluster Nodes collect Host Resources

COORDINATOR_HOST_RESOURCE_INTERVAL

Interval at which the Coordinator exchanges Host Resources with Nodes

COORDINATOR_HOST_RESOURCE_REQUEST_TIMEOUT

Time that the Coordinator waits after requesting the Host Resource information from the Nodes

COORDINATOR_NODE_REQUEST_TIMEOUT

Timeout until the Coordinator waits after requesting the Node to execute the command
Because the Add/Remove-node and Add/Remove-Package includes the Node command execution, if it is caught in a short time, the command processing may not be completed.

COORDINATOR_NODE_TIMEOUT

Time the Coordinator waits before determining that the Node has failed

COORDINATOR_STARTUP_DELAY

Grace time until activating the Decision Thread immediately after Coordinator startup
If it takes a long time to run the entire Cluster, you can start the Node control of Coordinator later by setting a larger value. 
If the Decision Thread runs before the entire drive, there is a high likelihood that the Coordinator will be misplaced.

COORDINATOR_STATUS_NODE_INTERVAL

Interval in which the Coordinator exchanges status inquiry messages with the Node

COORDINATOR_STATUS_NODE_REQUEST_TIMEOUT

Time the Coordinator waits after requesting status inquiries from Nodes.
If there is no status inquiry response during that time, the Coordinator proceeds without updating the status of the corresponding Node. 
If the network situation is not good and you need to update the state, you could consider increasing the value. 
Instead, if there is no status query response, the Coordinator will wait for as much as the value was increased.

DEPLOYER_DBS_PATH

Specifies the directory where the Deployer's data files will be created.
The default value is set to?/dbs, and ? is replaced with the $ MACHBASE_DEPLOYER_HOME environment variable. 
This is an environment variable $MACHBASE_DEPLOYER_HOME /dbs directory.
It must be applied to Deployer, and it has no effect on other Nodes.

EXECUTION_STAGE_MEMORY_MAX

The maximum amount of Memory used by the Stage Thread performing the SELECT query in Cluster Edition
Because it is the maximum size of each Stage, the complexity of the SELECT query with an increase in the number of Stages can lead to a larger memory requirement. 
If there is a Stage that exceeds the maximum size, the Stage is canceled and the Query is canceled with an error.
You must apply Properties directly to the specific Warehouse you want.
The default value is 1GB.

HTTP_ADMIN_PORT

Port number to receive requests from MWA or machcoordinatoradmin

HTTP_CONNECT_TIMEOUT

Timeout used when connecting to machcoordinatoradmin

HTTP_RECEIVE_TIMEOUT

Timeout used when communicating with machcoordinatoradmin

HTTP_SEND_TIMEOUT

Timeout used when communicating with machcoordinatoradmin

INSERT_BALANCE_MODE

When append or INSERT-SELECT is executed, it is instructed to input uniformly to each group.
If it is 0, it turns off the feature. If it is 1, it turns on the feature.

INSERT_BULK_DATA_MAX_SIZE

Maximum size of input data block when executing Append or INSERT-SELECT

INSERT_RECORD_COUNT_PER_NODE

Number of data inputs that lead to the warehouse group conversion when performing the input

STAGE_RESULT_BLOCK_SIZE

Maximum block size created in one stage