Page History
...
Multicast Cluster Messaging (DYNAMIC mode)
Yellowfin application messaging is handled by a multicast messaging library called JGroups. Using this method will automatically find other nodes in the cluster sharing the same Yellowfin database.
The default configuration of JGroups uses UDP multicast messages to determine group membership and find new nodes. There may be environments where these types of messages cannot be sent. For example, Amazon does not allow multicast packets on its internal network between nodes. The Multicast Cluster Messaging adapter allows you to pass an XML configuration file to configure JGroups to use other methods for node discovery. This file can be referenced by passing the path to the BroadcastConfiguration servlet parameter within the ClusterManagement servlet.
Expand | |||||
---|---|---|---|---|---|
| |||||
The following servlet definition needs to be added to the web.xml on each node:
|
Multicast with Repository Discovery (REPOSITORY mode)
Repository Discovery is an implementation of DYNAMIC mode, but with a custom plugin for discovering nodes via the shared Yellowfin Repository. This can be useful for enabling clustering on environments where Multicast packets do not work.
This functionality can also be enabled with DYNAMIC mode with the RepositoryDiscovery servlet parameter set to true.
TaskTypes and MaxParallelTaskCounts must be fine-tuned for each node, based on which tasks, the deployment of Yellowfin is expected to run. The configuration specified above allows the node to run a maximum of two tasks of each type, in parallel. For detailed information, see here. |
Multicast with Repository Discovery (REPOSITORY mode)
Repository Discovery is an implementation of DYNAMIC mode, but with a custom plugin for discovering nodes via the shared Yellowfin Repository. This can be useful for enabling clustering on environments where Multicast packets do not work.
This functionality can also be enabled with DYNAMIC mode with the RepositoryDiscovery servlet parameter set to true.
Expand | |||||
---|---|---|---|---|---|
| |||||
The following servlet definition needs to be added to the web.xml on each node:
| |||||
Expand | |||||
| |||||
The following servlet definition needs to be added to the web.xml on each node:
TaskTypes and MaxParallelTaskCounts must be fine-tuned for each node, based on which tasks, the deployment of Yellowfin is expected to run. The configuration specified above allows the node to run a maximum of two tasks of each type, in parallel. For detailed information, see here. |
Web Service Cluster Messaging (LEGACY mode)
...
Property | Value | ||
ClusterType | Either DYNAMIC, REPOSITORY, or LEGACY. DYNAMIC will use multicast messaging and automatically find other nodes in the clusternodes in the cluster. REPOSITORY is an extension of DYNAMIC where multicast messaging doesn't work. LEGACY is the default, and will use web services to communicate with a defined list of cluster nodes. | ||
BroadcastConfiguration | A JGroups configuration file. This allows for a custom Jgroups configuration to be used in environments where multicast networking is not available. This is for DYNAMIC mode only and is optional. By default, JGroups will use the configuration defined in udp.xml. | ||
ServiceUser | User that will validate the web service connection to other nodes. For LEGACY mode only. | ||
and is optional. By default, JGroups will use the configuration defined in udp.xml. | |||
ServiceUser | User that will validate the web service connection to other nodes. For LEGACY mode only. | ||
ServicePassword | Password for the ServiceUser. For LEGACY mode only. | ||
ServicePasswordEncrypted | True/False. | ||
ServiceAddress | Address of the Yellowfin web service. For LEGACY mode only. | ||
ServicePort | Port on which Yellowfin is running. For LEGACY mode only. | ||
ClusterHosts | This is a comma-separated list of all nodes in the Cluster. These can include IP addresses or hostnames | ServicePassword | Password for the ServiceUser. For LEGACY mode only. |
ServicePasswordEncryptedSerialiseWebserviceSessions | True/False. Is the contents of the ServicePassword encrypted. | ||
ServiceAddress | Address of the Yellowfin web service. For LEGACY mode only. | ||
ServicePort | Port on which Yellowfin is running. For LEGACY mode only. | ||
ClusterHosts | This is a comma-separated list of all nodes in the Cluster. These can include IP addresses or hostnames. For LEGACY mode only. | ||
SerialiseWebserviceSessions | True/False. This is required if using Single Sign-On on the Cluster. It can serialise tokens to the database so that the token can be accessed from any node. | ||
This is required if using Single Sign-On on the Cluster. It can serialise tokens to the database so that the token can be accessed from any node. | |||
CheckSumRows | True/False. Security option to check sum the serialised web service session records in the database. This helps prevent modification to the table which could lead to the creation of unauthorised sessions in Yellowfin. | ||
EncryptSessionId | True/False. Security option to encrypt the serialised web service session id in the database. This helps prevent modification to the table which could lead to the creation of unauthorised sessions in Yellowfin. | ||
EncryptSessionDataCheckSumRows | True/False. Security option to check sum encrypt the serialised web service session records in the database. This helps prevent modification to the table which could lead to the creation of unauthorised sessions in Yellowfin. | ||
EncryptSessionId | True/False. Security option to encrypt the serialised web service session id in the database. This helps prevent modification to the table which could lead to the creation of unauthorised sessions in Yellowfin. | ||
EncryptSessionData | True/False. Security option to encrypt the serialised web service session records in the database. This helps prevent modification to the table which could lead to the creation of unauthorised sessions in Yellowfin. | ||
in the database. This helps prevent modification to the table which could lead to the creation of unauthorised sessions in Yellowfin. | |||
AutoTaskDelegation | True/False. This is only for DYNAMIC and REPOSITORY mode and is optional. When enabled, the Cluster will automatically assign a “Master” node which coordinates background task execution. When this is turned on, you do not need to manually configure a node to run background tasks. The Master node also runs System Tasks, provided they have not been explicitly disabled. When AutoTaskDelegation is disabled, each node operates like a LEGACY node. A specific node has to be designated for background task execution. This mode is not recommended. | ||
TaskTypes | This option is only for DYNAMIC and REPOSITORY modes. It is a comma separated list of task types which can run on the node. If this is not specified, the node will not run any background task. Available types are specified here. | ||
MaxParallelTaskCounts | This option is only for DYNAMIC and REPOSITORY modes. | AutoTaskDelegation | |
SessionReplication | True/False. Set this to true if container level Session Replication is enabled. This will modify the logic used for destroying sessions in a cluster. | ||
RepositoryDiscovery | True/False This option is for DYNAMIC mode only. This enables RepositoryDiscovery on builds prior to the REPOSITORY mode being supported. REPOSITORY mode is an alias for DYNAMIC mode with RepositoryDiscovery enabled. |
...