HP-UX Workload Manager A.02.03.01 Release Notes for HP-UX 11i V1.0 and HP-UX 11i V2.0

HP-UX Workload Manager Release Notes

Known problems and workarounds

Unable to get CPU allocation due to number of processes

Issue

WLM provides a workload group its allocation on a system by granting the

group its allocation on each CPU. If the group does not have at least one

process for each CPU, WLM increases the allocations for the processes to

compensate. For example, for a workload group with a single-threaded

process, 10% of four CPUs is allocated as 40% of one CPU.

Assume this same group were allocated 50% of the four CPUs. WLM would

allocate 100% of two CPUs to the workload group. However, because the

group has only the one thread, it can use only one CPU, resulting in an

allocation of 25%.

Workaround

There is no workaround. However, be aware of how your applications run so

that you do not give them resource allocations they cannot use.

Collectors abort when updated while running

Issue

If you update (overwrite) a data collector executable (be it a binary or a

script) while it is providing data to WLM, the collector may abort.

Workaround

There are two workarounds to this issue:

• Update the data collector in place

1. Stop WLM (wlmd -k)

2. Update the data collector

3. Re-start WLM (wlmd -a configuration_file)

• Replace the data collector

1. Move the current data collector aside

2. Install the new data collector in place of the collector you just moved

aside

3. Re-start WLM (wlmd -a configuration_file)