CKS Scheduler - Processor Thread - ACS - Reference Guides

ACS Installation and Administration Guide

Product
ACS
AFS_Version
7.11
Category
Reference Guides
language
English
audience
public

CKS Scheduler Processor thread parameters are located in the following configuration file:

/usr/local/afs7/conf/conf.xml

The following lines show an example of CKS Scheduler parameters:

<?xml version="1.0" encoding="iso-8859-1" standalone="yes"?>
<afs:conf xmlns:afs="http://ref.antidot.net/v7/afs#">
<afs:QEng>
<afs:QueryManager>
<afs:host value="afsk4ccr"/>
</afs:QueryManager>
</afs:QEng>
<afs:Alerts>
<afs:ScheduledSearches>
<afs:PaFId value="last_paf_id"/>
<afs:minDelayS value="10"/>
<afs:poolSize value="10"/>
<afs:timeout value="30"/>
</afs:ScheduledSearches>
<afs:Router>
<afs:route>
<afs:mapItem key="CKS" value=":15002"/>
</afs:route>
</afs:Router>
</afs:Alerts>
</afs:conf>

  • afs:minDelayS: time interval between to searches run on QM in the same instance (in milliseconds).
  • afs:poolSize: number of Processor threads processing scheduled searches. Default value is "5". This value must be set according to the number set for the CKS Server Notifier CorePoolSize parameter.
  • afs:timeout: timeout to process a schedule search on QM (in seconds). Default value is "30".

To apply modifications, run the following command:

As root user

systemctl restart cks-alerts.service

CKS Server Notifier thread parameters are located in the following configuration file:

/usr/local/afs7/cks-server/conf/conf.ws

The following lines show an example of CKS Scheduler parameters:

<?xml version="1.0" encoding="utf-8" standalone="no"?>
<Conf xmlns="http://www.antidot.net/core/configuration"  xmlns:a="http://www.antidot.net/bows/configuration"xmlns:c="http://www.antidot.net/cks/ws/configuration"  xmlns:w="http://www.antidot.net/ws/core/configuration">
...
<c:NotificationListener appId="CKS">
<c:port>15002</c:port>
<c:NotificationThreadPool>
<corePoolSize>30</corePoolSize>
<maximumPoolSize>30</maximumPoolSize>
<keepAliveTime>30</keepAliveTime>
</c:NotificationThreadPool>
</c:NotificationListener>
</c:CKSModule>
</Conf>

  • CorePoolSize: number of fixed threads executing CKS_server Notifier Thread instances. This value must be equal to or higher than the number entered for the CKS Scheduler afs:poolSize parameter.
  • maximumPoolSize: number of maximum threads executing CKS_server Notifier Thread instances.
  • keepAliveTime: maximum execution time for threads between CorePoolSize and maximumPoolsize number (in seconds).

If CorePoolSize value differs from maximumPoolSize value:

Notifier Thread instances are threaded according to corePoolSize value, other instances can be launched on demand to process numerous requests in a maximumPoolSize value limit.

In this configuration, instances launched over the corePoolSize value are monitored and terminated after the keepAliveTime value is reached in seconds.

This configuration may limit continuous server resources needs, but will induce more variations in resources use depending on the variation of threads amount.

It will also process slowly as instances are managed, started and terminated asking for more running time on the system.

If CorePoolSize and maximumPoolSize are set to the same value:

The keepAliveTime parameter is not used to limit the amount of instances duration and Notifier Thread run on a set number of instances.

This configuration is faster to process as threads are not started and terminated, but the amount of resources on the server is continuously fixed to a higher level.

We recommend to enter the same values for CorePoolSize and maximumPoolsize in order to establish a set load for the server.

To apply modifications, run the following command:

As root user

systemctl restart cks-alerts.service