PM79860: Failover placement can occur prematurely if a container fails before the grid is initially placed.

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

  • Even with placement suspended via suspendBalance, placement can
    occur if a container fails. This is by design to avoid
    scenarios in which failover does not occur.
    
    However, the failover placement can occur if a container fails
    before the data grid is initially placed.  This can cause more
    issues in larger environments if placement is triggered
    prematurely.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Any eXtreme Scale user, particularly those  *
    *                  with large numbers of partitions (1000 or   *
    *                  more).                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When the catalog server submits         *
    *                      placement work that takes over 30       *
    *                      seconds to complete, some of that       *
    *                      work might time out.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Timed out placement that is sent to container servers might
    not complete.  Artifacts of timed out worked are cleaned
    up on the catalog server. However, the work is not resubmitted
    to the container servers.
    

Problem conclusion

  • The catalog server resends the timed out work.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM79860

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-02

  • Closed date

    2013-01-29

  • Last modified date

    2013-01-29

  • 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

  • R850 PSY

       UP

  • R860 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere eXtreme Scale

Software version:

850

Reference #:

PM79860

Modified date:

2013-01-29

Translate my page

Machine Translation

Content navigation