Implementing round-robin transaction-level workload balancing

The Db2® client makes workload balancing decisions based on the contents of the server list. If all members have the same priority work is routed evenly between all members.

Before you begin

You must have an existing member subset.

About this task

Rather than using the member load-based transaction level workload balancing algorithm, to balance transactions evenly you can configure a member subset to use a round-robin algorithm by specifying the WLM_ALTER_MEMBER_SUBSET routine parameter '<memberPriorityBasis>equalPriority</memberPriorityBasis>'. Connections that are assigned to the member subset distribute transactions equally between all active members. The member priority in the member subsets server list for each active member is 101.


Restrictions

DBADM or WLMADM authority is required.

Procedure

To configure a member subset to use round-robin transaction level workload balancing:

  1. To alter the basis that is used for member priorities for a member subset: 
    CALL SYSPROC.WLM_ALTER_MEMBER_SUBSET( 'subset-name', '<memberPriorityBasis>equalPriority</memberPriorityBasis>', NULL )
    where:
    • subset-name is the member subset name
  2. To validate that the member priorities for the member subset are equal priorities instead of being based member load by querying the MON_GET_SERVERLIST table function. Verify that the non-zero member priorities are always equivalent. 
    SELECT * FROM TABLE
  ( MON_GET_SERVERLIST( 'OLTP_SUBSET', -1 ) )
  AS SERVER_LIST