The application placement controller is designed to work with the default settings. However, there can be times when fine tuning the application placement controller becomes necessary to ensure the best results.
Depending on your administrative role, you are allowed the following specific privileges when you are configuring the application placement controller:
Setting | Description |
---|---|
Enable | Enables or disables the application placement controller. If you disable the application placement controller, you are disabling all autonomic operations for the dynamic clusters. After the placement controller is disabled, no dynamic changes occur with regard to the size and placement of applications on the dynamic cluster. This action is equivalent to turning all dynamic clusters to static clusters. |
Approval timeout | Controls how long the runtime task sits in the
queue awaiting action before it expires automatically. Acceptable
time values are 1 to 60 minutes. This setting is particular to the
supervised operating mode. When the operating environment is set to
run in supervised mode, the application placement controller creates
tasks, but must wait for approval from the system administrator before
making changes. The application placement controller treats runtime tasks that are timed out as user-rejected tasks. |
Server operation timeout | Represents the amount of time, in minutes, that
the application placement controller waits for a start or stop operation
to complete before the operation is considered a failure. Set this value to the predicted worst case time to start or stop a server. Note: When the completion time for an operation and the
server operation timeout exceed the amount of time configured for
the request timeout, increase the request timeout to a value greater
than the value for the server operation timeout.
Servers are not automatically placed in maintenance mode when the servers fail to start before the server operation timeout. Instead, a runtime task is generated a when the server fails to start. The application placement controller does not attempt to start this server again until the server is successfully started manually. When you successfully start the server manually, the application placement controller receives a notification that the server has started. If you want the servers to be put into maintenance mode, you can set the maintenanceModeOnOperationFail custom property on the application placement controller. If you want to take servers out of maintenance mode after starting successfully, you can specify the unsetMaintenanceModeAfterStart custom property on the application placement controller. |
Minimum time between placement change | Specifies the amount of time that the application
placement controller waits before initiating a new batch of changes.
The application placement controller might wait for a batch of changes
after completing previous changes, or encountering a timeout. Acceptable
values can range from 1 minute to 24 hours. When setting this value, consider the overhead that is associated with starting and stopping servers. Starting or stopping servers can take several minutes and might introduce an additional load to the nodes. If you allow the placement controllers to readjust application placement too often, the added overhead negates the increased performance gains that can be earned by readjusting the size of dynamic clusters. For example, if a server takes one minute to start, and the setting for the minimum time between placement changes is 20 minutes, then placement changes have a performance impact of approximately 5%. Set this value at least 20 to 30 times larger than the time necessary to start a server. A value greater than several hours prevents application placement changes from happening more than once a day. If you believe that traffic load and application demands adjust several times during a day, you might want to allow placement changes to occur more frequently. |
The application placement controller is tuned for its best performance.