PI33793: Scaling controller does not start a server to meet minimum insta nces when a host with capacity becomes available

8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• By design, the scaling controller won't start a server to
  meet a scaling policy's minimum number of instances if it
  cannot find a host with capacity.  However when capacity
  later becomes available the scaling controller still won't
  start a server to meet the minimum number of instances.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of the auto scaling function in   *
  *                  IBM WebSphere Application Server Liberty    *
  *                  Profile                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Scaling controller does not start a     *
  *                      cluster member to meet minimum          *
  *                      instances when a host with capacity     *
  *                      becomes available                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The scaling controller will not start a cluster member to meet a
  scaling policy's minimum number of instances if it cannot find a
  host with capacity.  However when a host with capacity later
  becomes available the scaling controller still won't start a
  cluster member to meet the policy's minimum number of
  instances.
  
  This problem occurs only when there are multiple servers running
  per host and at least one server is already active and reporting
  metric data to the scaling controller.  A host is considered to
  have capacity if its metric data falls below the upper
  thresholds of the scaling policy.
  

Problem conclusion

• The scaling controller is changed such that when it receives
  updated host metric data it tries again to start a cluster
  member to meet the scaling policy's minimum number of
  instances.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.5.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP