PM82142: When doing a rolling restart, data can be lost with synchronous replication enabled.

APAR status

• Closed as program error.

Error description

• Revision data stays behind and does not catch up for
  synchronous replicas.  Because of this issue, when a sync
  replica becomes primary, data is not fully replicated to the
  new synchronous replica.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of WebSphere eXtreme Scale who use    *
  *                  synchronous replication.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: A new synchronous replica does not get  *
  *                      all the data when a synchronous         *
  *                      replica becomes primary on a rolling    *
  *                      restart or failover.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Transactions that did not change the data
  grid but incremented the revision count on the primary were
  not being replicated correctly to the synchronous replica.
  This issue was corrected so that the revision number is
  incremented correctly on the synchronous replica to match the
  primary.
  

Problem conclusion

• This APAR is included in the 8.6.0.1 release.
  

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:

Fix information

• Fixed component name

  WS EXTREME SCAL

• Fixed component ID

  5724X6702

Applicable component levels

• R860 PSY

     UP