Page History
Each Yellowfin node will be configured by default to run background tasks. The cluster should be properly configured for task execution, depending on the cluster type.
...
A node may be configured to become Master but never a Slave. To do this, do not include any TaskType in the ClusterManagement servlet block in web.xml. If multiple nodes are configured to become the Master to allow for failover, then the node that gets started first becomes the Master.
A node may be configured to become a Slave but never a Master. To do this, add the following to the MIStartup servlet block in web.xml:
Code Block language xml <init-param> <param-name>DisableTaskScheduler<name>DisableTaskSchedulerPolling</param-name> <param-value>TRUE</param-value> </init-param>Web-facing nodes may be configured to never become a Master or Slave. This way, background tasks don’t compete for resources with online processing. To do this, add the following to the MIStartup Servlet block in web.xml:
Code Block language xml <init-param> <param-name>DisableTaskScheduler</param-name> <param-value>TRUE</param-value> </init-param>
And ensure to not include any TaskType in the ClusterManagement servlet block in web.xml.
...
Nodes may be configured to run specific tasks. The maximum number of concurrent tasks of each type should also be configured. To do this, add the following snippet in the ClusterManagement servlet block in web.xml.
Code Block language xml <init-param> <param-name>TaskTypes</param-name> <param-value> FILTER_CACHE, ETL_PROCESS_TASK, SOURCE_FILTER_REFRESH </param-value </init-param> <init-param> <param-name>MaxParallelTaskCounts</param-name> <param-value> 1, 5, 3 </param-value> </init-param>This configures the node to run a maximum of one Filter Cache refresh task, five Data Transformation tasks and three Source Filter Refresh tasks at the same time.
If this snippet is not configured in the ClusterManagement servlet, the node will not run any background task.
...
A node running only SIGNALS_DCR_TASK, SIGNALS_ANALYSIS_TASK and SIGNALS_CLEANUP_TASK will be designated as a “Signals Node”. The node may run one or more of these types, but it shouldn’t run any others. A cluster may have one or more Signals Nodes. Signals nodes are specially licensed and cannot be used for processing web requests or other background tasks. A Signals node cannot become a Master.
| Code Block | ||
|---|---|---|
| ||
<init-param>
<param-name>TaskTypes</param-name>
<param-value>
SIGNALS_DCR_TASK,
SIGNALS_ANALYSIS_TASK,
SIGNALS_CLEANUP_TASK
</param-value
</init-param>
<init-param>
<param-name>MaxParallelTaskCounts</param-name>
<param-value>2,5,2
</param-value>
</init-param>
|
...
| Section | |||||||
|---|---|---|---|---|---|---|---|
|
...