Use these custom properties for advanced configurations for core groups.
To configure a custom property, complete the following steps:
If the custom property is not in the list of defined custom properties, click New and then enter the name of the custom property in the Name field and an appropriate value in the Value field.
Use this custom property to eliminate a condition that is reported by a message that is displayed repeatedly in your SystemOut.log file.
[9/24/04 13:28:19:497 CDT] 00000013 VSync W DCSV2005W: DCS Stack DefaultAccessPointGroup.P at Member 172.16.1.86:9353: The amount of memory available for synchronization is low. The configured memory size is 418816 bytes. Currently used memory size is 420307 bytes.
If the member IP address is in the format of a dotted decimal IP address and port, you can eliminate these messages by increasing the amount of memory that is allocated to the core stack that is used for core group communication. Increase the value of this property until you no longer see the message in your SystemOut.log file. Because the memory is dynamically allocated, setting a larger stack size than you need does not cause memory problems.
See Core group bridge custom properties for more information about how to set the property at those levels.
Units | megabytes |
Default | 5 |
Use this custom property to adjust how frequently the core group IP cache is cleared.
The caching of name-to-IP address information at the core group level eliminates some of the system overhead required to assign IP addresses to core group members.
Units | seconds |
Default | 60 |
Acceptable values | Any positive integer. 1 is the minimum value that can be specified |
Use this custom property to change how frequently the high availability manager Discovery Protocol checks for new core group members. A new core group member is not able to communicate with other core group members until the Discovery Protocol establishes communication between the new member and the existing members.
Units | seconds |
Default | 30 seconds. |
Use this custom property to change how frequently the Failure Detection Protocol checks the core group network connections that the discovery protocol establishes. The Failure Detection Protocol notifies the Discovery Protocol if a connection failure occurs.
Units | seconds |
Default | 6 |
Use this custom property to change how many consecutive heartbeats a core group member must miss before that core group member is considered failed.
See Core group Failure Detection Protocol for more information about the Failure Detection Protocol.
Units | seconds |
Default | 6 |
Use this custom property to configure all of the members of the selected core group to run with a different version of the higher level core group protocol. You can change the value of this property while the core group members continue to run. After you save and synchronize the changed value to all of the nodes containing core group processes, the high availability manager automatically detects the configuration change and starts using the new core group protocol version to communicate with the core group members.
The following table lists the core group protocol version IDs that can be specified for this property.
Version ID | Required Minimum product Level | Description |
---|---|---|
6.0.2.31 | 6.0.2.31 for Version 6.0.2, 6.1.0.19 for Version 6.1 | This protocol version is the original or base version of the HAM protocol. This version was included in the 6.0.2.31, and 6.1.0.19 service packs to facilitate core group bridge scalability. This version is recommended for topologies that contain multiple core groups and core group bridges as part of their configuration. |
Use this custom property to explicitly enable exception handlers that are specific for OutOfMemoryExceptions that occur when sending or receiving network messages. When this property is set to Isolate, if an OutOfMemoryException occurs when a network message is being sent or received, these exception handlers stop High Availability Manager communications to the Out of Memory process.
If IBM_CS_OOM_ACTION=Isolate is not added to the configuration settings for a core group, if a core group process runs out of memory, the Out of memory process might not be able to respond to all messages. This situation prevents multi-step protocols from completing, and prevents the starting server from receiving its initial view of the distributed state.
Use this custom property to change the size of the socket buffer that the core group transport obtains.
Units | One of the following:
|
Default | 2 megabytes for all buffer types. |
Use this custom property to configure all of the members of the selected core group to run with a different version of the low level core group protocol. You can change the value of this property while the core group members continue to run. After you save and synchronize the changed value to all of the nodes containing core group processes, the high availability manager automatically detects the configuration change and starts using the new core group protocol version to communicate with the core group members.
The following table lists the core group protocol version IDs that can be specified for this property. 6.0.0 is the default value.
Version ID | Required Minimum product Level | Description |
---|---|---|
6.0.0 | Any | This protocol version is the original or base version. All versions of the high availability manager can use this protocol. If you do not specify a particular wire format protocol version, the high availability manager uses this version. |
6.0.2.9 | 6.0.2.9 for Version 6.0.2 6.1.0 for Version 6.1 |
This protocol version is included in the 6.0.2.9 service pack. This protocol is also included in Version 6.1 of the product. This protocol version facilitates core group bridge scalability. This version is recommended for large topologies that contain multiple core groups and core group bridges as part of their configuration. |
6.1.0 | 6.1.0 for Version 6.1 | This protocol version is included in Versions 6.1.0 of the product. This version adds core group scalability improvements, and more support for large topologies. |
To set a value for this custom property, in the administrative console, click
core_group_name. Then, under Additional Properties, click .