consistent-port-selection
Section: system
Default Value: false
Valid Values: true, false
Changes Take Effect: At the next reconnect. For master Configuration Server, this option must be configured from the configuration files and it must be restarted for the changes to take effect. For proxies, this option can be configured at runtime and it must be specified in the application configuration objects.
When set to true, this option implements the following behavior in selecting ports for connections of Configuration Server Proxies to the master Configuration Server, including the connections of backup instances of both master and proxy to their primary peers:
- When a Configuration Server Proxy loses connection to the primary master Configuration Server, to reconnect to the primary backup instance, the proxy will consistently use the port with the same port ID that was used for its initial connection to the primary (specified in the command line). If the port with the same ID is not configured, the default port will be used. If a port with the ID default is not configured, any available port will be used.
- The backup instances of Configuration Servers, both master and proxy, will consistently use the ports marked as HA Sync to connect to their primary peers. If HA Sync port is not available, the default port will be used. If a port with the ID default is not configured, any available port will be used.
This option applies to the configurations where Configuration Server instances have multiple listening ports. If set to false (the default), this feature is disabled.
x-stat-print-interval
Section: log
Default Value: 0
Valid Values: 0 or any positive integer
Changes Take Effect: For the next scheduled printout
Specifies the interval (in seconds) between each logging printout of the statistics.
When the statistics printout interval is set, all statistics log entries are written in a separate log file with the suffix _stat in the file name and this file is placed in the same directory as the regular log file. The default value 0 (zero) means that the feature is disabled.
Note: The statistics log file is created and updated only if the following two conditions are met:
- The verbose option is set to debug or all.
- File logging is configured for the regular logs.
delay-reload-backup
Section: csproxy
Default Value: 0
Valid Values: 0 or any positive integer
Changes Take Effect: For the next reconnect to the master
Related Options: delay-reload, proxy-load-max
Specifies the time interval, in seconds, that the backup Configuration Server Proxies or the backup master server must wait to reload data from the master Configuration Server after the initial connection failed. You can specify a higher delay period for the backup Configuration Server proxies to ease the load on the master Configuration Server after network outages when multiple clients need to reload data at the same time.
The configured reload delay period applies to the master Configuration Server when it needs to reload data while running in the backup mode or after being switched to backup mode upon a switchover.
This option does not delay initial data load after Configuration Server restart and it does not delay the attempt to restore the previous session to the master Configuration Server. This option takes effect only if an attempt to restore the previous session with the master Configuration Server fails.
Tip: Specify different delay reload settings for different proxies to establish the order in which proxies initiate reload. You can use this option in conjunction with the [system].proxy-load-max option to further delay data reloading process for the proxies.
delay-reload
Section: csproxy
Default Value: 0
Valid Values: 0 or any positive integer
Changes Take Effect: For the next reconnect to the master
Related Options: delay-reload-backup, proxy-load-max
Specifies the time interval, in seconds, that Configuration Server Proxy waits to reload data from the master Configuration Server after the initial connection failed. When multiple proxies are connected to the master Configuration Server, this feature enables you to prioritize proxy reloads and decrease the time each proxy remains out of service while reloading the data.
This option does not delay initial data load after Configuration Server restart and it does not delay the attempt to restore the previous session to the master Configuration Server. This option takes effect only if an attempt to restore the previous session with the master Configuration Server fails.
Tip: Specify short but different delay reload settings for different proxies to establish the order in which proxies initiate reload. You can use this option in conjunction with the [system].proxy-load-max option to further delay data reloading process for the proxies.
8.5.101.38
Configuration Server Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 09/27/19 | General | X | X | X | X |
Contents
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- Configuration Server now allows you to selectively delay the data reload performed by multiple Configuration Server proxies while attempting to reconnect to the master Configuration Server after a previously failed attempt. This feature helps to avoid concurrent data reloads by retaining some Configuration Server Proxies in operation (in read-only mode) while other proxies are reloading data, thereby preventing overload of the master Configuration Server. The new configuration options, delay-reload and delay-reload-backup, can be used to enable this feature and configure the reload delay period for the primary and backup master Configuration Server and proxies, respectively. For more information, see Framework Deployment Guide. (MFWK-21414)
- Configuration Server now collects statistics on its operation, such as the current operating mode, the total number of clients connected, request processing time, and the application name, and periodically prints it to a separate log file. The statistics are collected on the application, reactor (CfgLib only), and client levels. You can enable this feature by configuring the statistics printout interval using the new configuration option, x-stat-print-interval. (MFWK-20979)
- When the Configuration Server instances have multiple listening ports, you can now configure both primary and backup instances of Configuration Server or Configuration Server Proxy to select ports consistently based on the listening port ID or the HA Sync attribute. You can enable this feature using the new configuration option, consistent-port-selection. (MFWK-20945)
Resolved Issues
This release contains the following resolved issue:
Configuration Server Proxy now properly reconnects to the master Configuration Server after multiple master Configuration Server switchovers. Previously, Configuration Server Proxy, which was initially connected to a non-default master port, failed to reconnect to the master Configuration Server after two consecutive switchovers and tried to connect to the former backup Configuration Server. (MFWK-21226)
Upgrade Notes
No special procedure is required to upgrade to release 8.5.101.38.