Jump to: navigation, search

haflip-detect-timeout

Section: general
Default Value: 10
Valid Values: 1–2147483647
Changes Take Effect: Immediately


Specifies the time interval, in seconds, for which Solution Control Server detects the flipping of the monitoring applications from Primary to Backup to Primary or vice versa, and prints the following standard log messages depending on the state of the applications or SCS:

  • 10327—Indicates that the operation mode (primary or backup) of the application has changed frequently.
  • 10328—Indicates that the application is in a stable state.
  • 10329—Indicates that "split brain" condition may have occurred for SCS.
  • 10330—Indicates that SCS has recovered from the split brain state.

Notes:

  • You can configure this timeout interval for a specific application by setting this option in the [log] section of that application.
  • When this option is not configured in the [log] section, the value of this option set in the [general] section is used.

haflip-detect-timeout

Section: general
Default Value: 10
Valid Values: 1–2147483647
Changes Take Effect: Immediately


Specifies the time interval, in seconds, for which Solution Control Server detects the flipping of the monitoring applications from Primary to Backup to Primary or vice versa, and prints the following standard log messages depending on the state of the applications or SCS:

  • 10327—Indicates that the operation mode (primary or backup) of the application has changed frequently.
  • 10328—Indicates that the application is in a stable state.
  • 10329—Indicates that "split brain" condition may have occurred for SCS.
  • 10330—Indicates that SCS has recovered from the split brain state.

Notes:

  • You can configure this timeout interval for a specific application by setting this option in the [log] section of that application.
  • When this option is not configured in the [log] section, the value of this option set in the [general] section is used.

8.5.100.39

Solution Control Server Release Notes


9.0
Solution Control Server is part of 9.0 starting in 8.5.100.25.
Release Date Release Type Restrictions AIX Linux Solaris Windows
02/28/19 General X X X X

Helpful Links

Releases Info


Product Documentation

Management Framework

Genesys Products

List of Release Notes

What's New

This release contains the following new features and enhancements:

  • The following new Solution Control Server (SCS) Log Events are used to detect the state changes of the applications and SCS:
    • 43-10327 [+] show details
    • 43-10328 [+] show details
    • 43-10329 [+] show details
    • 43-10330 [+] show details

  • When Solution Control Servers configured as HA pair lost connection and did not recover within the haflip-detect-timeout time frame, both the servers enter into the split brain state and generate the Log Event, 10329, on becoming primary. When connection between Solution Control Servers is restored, the split brain condition is cleared and the Log Event, 10330, is generated.

  • The following Log Events related to read access activities have been enhanced with additional information, such as the IP address of host, tenant name, application name, and application type:
    • 43-10400 [+] show details
    • 43-10401 [+] show details
    • 43-20700 [+] show details
    • 43-20701 [+] show details
    • 43-20709 [+] show details

Resolved Issues

This release contains the following resolved issues:


When SCS enters the split brain state, SCS now performs a controlled switchover of applications within the timeout period configured using the haflip-detect-timeout option until SCS returns to the normal state. The Log Event, 10327, is generated when the applications switchover and 10328 is generated when the applications are stable. Previously, the applications switched over frequently when SCS entered the split brain state. (MFWK-21241)


Upgrade Notes

No special procedure is required to upgrade to release 8.5.100.39.

This page was last modified on February 28, 2019, at 10:24.

Feedback

Comment on this article:

blog comments powered by Disqus