GTM.conf_file_and_long_option

Here's a list of candidate parameters in gtm.conf and long option for GTM, GTM-Standby and GTM-Proxy.

OptionDescriptionGTMGTM-StandbyGTM-Proxy

my_host
Own host to listen
Yes
Yes
Yes

my_port
Own port to listen
Yes
Yes
Yes

destination_host
Host to connect
No
Yes
Yes

destination_port
Port to connect
No
Yes
Yes

log_file
Log file name
Yes
Yes
Yes

log_min_message
Message to log
Yes
Yes
Yes

initial_gxid
GXID value to begin
?
No
No

start_opt
GTM ACT or SBY
Yes
Yes
No

err_reporter
Command to report error to outside
Yes
Yes
Yes

status_reader
Command to collect cluster status
Yes
Yes
Yes

err_wait_opt
If wait for reconnect at failure
No
No
Yes

err_wait_interval
How long to wait (in sec)
No
No
Yes

err_wait_count
How many times to wait
No
No
Yes

keepalive_idle
See tcp_keepalive_time
Yes
Yes
Yes

keepalive_interval
See tcp_keepalive_intvl
Yes
Yes
Yes

keepalive_count
See tcp_keepalive_probes
Yes
Yes
yes

Further description is as follows:

• GTM may be allowed to have destination_host and desitnation_port to specify connection point used at the time of switchover.
• I'm not sure if initial_gxid should appear in gtm.conf because this is needed only at the the first time or when GTM restarts after crash, where restart GXID value is not reliable. I'm thinking to leave this in the command option.
• err_reporter and status_reader is an external command to report any error or to obtain global XC cluster status respectively. It is supposed that they are a part of XCM module. Because they are not called frequently, it would be better not to include XCM libaries in GTM.
• err_wait_opt, err_wait_interval and err_wait_count control the behavior of GTM-Proxy when it detects errors in send/receive data with GTM. This is needed to wait for "reconnect" operation when GTM fails.