PI45073: When restarting individual container servers without placement constraints, extra primary shards can occur.

APAR status

• Closed as program error.

Error description

• After starting multiple container servers without using any
  placement contstraints, the following exception occurs:
  
  java.lang.IllegalStateException:
  java.lang.IllegalStateException
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere eXtreme Scale users starting      *
  *                  servers in a staggered fashion, but without *
  *                  a placement constraint, where the placement *
  *                  work started for the previous container     *
  *                  server does not complete before the next    *
  *                  container server starts.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: When restarting individual container    *
  *                      servers without placement constraints,  *
  *                      extra primary shards can occur.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  After starting multiple container servers without using any
  placement constraints, such as using the xscmd commands
  suspendBalancing and resumeBalancing, extra primary shards can
  occur. This can occur when a new container server is started
  before the placement work completed for the prior container
  server. A primary shard attempts to promote from a previous
  primary that is still in transition, itself. The following
  exception occurs in the FFDC logs:
  java.lang.IllegalStateException:
  java.lang.IllegalStateException:A non-primary shard (type:
  SynchronousReplica) on vc2cmmka039827np_pzn_container_1_C-0
  received a primary shard action to abdicateLeadership for
  pznGrid:segmentMapSet:127:primary
  

Problem conclusion

• In the fix, a promoting shard allows more time for the previous
  primary to complete its transition before completing the next
  promotion.
  

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