cancel
Showing results for 
Search instead for 
Did you mean: 

Technical Alert for EDB Postgres Failover Manager 3.2 to 3.5

Technical Alert/Update Information

Technical Alert Name
EDB Technical Alert for Postgres Failover Manager 3.2 to 3.6
Product Type
EDB Failover Manager
Severity
Moderate
Release Date
8/21/2019
Technical Alert Details
Technical Alert

ALERT FOCUS
All versions of EDB Failover Manager (EFM). The update has been tested with versions 3.2 through 3.5, and is included EFM 3.6 and later.

RECOMMENDED ACTIONS
Status: Moderate  
Recommended: This update fixes a slow memory leak in a 3rd party library used by EFM. Over a period of months with the current memory settings, EFM agents will run out of memory and fail. This does not affect running databases, but disables failover protection until the affected agents are restarted. It is recommended to apply this change when convenient.

WHAT IS IN THIS ALERT
This technical alert is notifying you of an available update to existing EFM installations to fix a memory leak.

This software update contains the following fixes:
The JGroups library version 4.0.19 that contains a fix for the memory leak issue.

IS THIS ALERT FOR ME?
This alert is for customers using:
  • EDB Failover Manager versions 3.2 through 3.5.
HOW TO GET THE UPDATE AND APPLY IT
This update can be obtained by downloading a 3rd party library .jar file to replace the existing one in an EFM installation. Because this version affects clusters running with IPv6 (see below), it is not an automatic update to EFM.
  • Stop the EFM agents to be updated. This should be all of the agents in a cluster; EFM should not be run with different versions of the code on different agents in the same cluster.
  • In the /usr/edb/efm-[version]/lib directory, rename the file jgroups-[version].Final.jar. For instance:
# cd /usr/edb/efm-3.2/lib
# mv jgroups-4.0.8.Final.jar jgroups-4.0.8.Final.jar_original
Note: If you are using IPv6, the above version of the JGroups jar file requires an update to your cluster properties file. The following must be added to the jvm.options property before starting the agent:

-Djava.net.preferIPv6Addresses=true

For example, if you had this previously:

# Extra information that will be passed to the JVM when starting the agent.
jvm.options=-Xmx128m

It should be changed to:

# Extra information that will be passed to the JVM when starting the agent.
jvm.options=-Xmx128m -Djava.net.preferIPv6Addresses=true

This property change will not be needed for EFM v3.6 and later. It is only needed for the specific version of JGroups that contains the memory fix and works with EFM 3.5 and older.
Version history
Revision #:
1 of 1
Last update:
‎08-21-2019 03:05 PM
Updated by:
 
Contributors