PM56174: Asynchronous replication can get behind and not stay current, while under continuous load.

APAR status

• Closed as program error.

Error description

• Asynchronous replication does not update enough data on each
  replicating cycle when grids contain a large number of maps.
  While under continuous load, the replica cannot stay current.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of WebSphere eXtreme Scale who have   *
  *                  several maps in their data grids and use    *
  *                  asynchronous replication.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Asynchronous replication can fall       *
  *                      behind when the primary is under load.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When looking at the revisions information for a primary and
  replica, the replica can fall behind even though the primary
  is able to stay current with a large load.  When many maps
  exist, the replication code is conservative so as not
  to go out of memory when replicating.  Therefore, the
  replication packets sent to the replica can be smaller.
  

Problem conclusion

• The code was updated to make sure that more data is sent
  during each replication cycle.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PM56180

Fix information

• Fixed component name

  XD EXTREME SCAL

• Fixed component ID

  5724J3402

Applicable component levels

• R710 PSY

     UP