IBM Support

PI45445: With two or more synchronous replicas placed, uncommitted transactions are possible after failover.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When two or more synchronous replicas are defined and a failover
    occurs while transactions are mid-flight, some sync replicas can
    Until the transactions time out on the sync replicas, the
    promoted primary shard can throw
    ReplicationVotedToRollbackExceptions if the minimum synchronous
    replicas option is set (minSyncReplica >=  1 in the deployment
    policy file).
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere eXtreme Scale users running with  *
    *                  two or more synchronous replicas that are   *
    *                  defined and placed.                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: With two or more synchronous replicas   *
    *                      placed, uncommitted transactions are    *
    *                      possible after failover.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When two or more synchronous replicas are defined and a
    failover
    occurs while transactions are mid flight, some synchronous
    replicas can have uncommitted transactions.
    Until the transactions time out on the sync replicas, the
    promoted primary shard can throw
    ReplicationVotedToRollbackExceptions, if the minimum
    synchronous
    replicas option is set (minSyncReplica >=  1) in the deployment
    policy file.
    

Problem conclusion

  • The promotion path was fixed to force any additional replicas
    to roll back existing transactions and re-enter peer mode
    against the newly promoted replica shard.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI45445

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-07-23

  • Closed date

    2015-07-30

  • Last modified date

    2015-07-30

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"860","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
30 July 2015