Page History
| Table of Contents | ||
|---|---|---|
|
Overview
Yellowfin can be clustered on multiple servers to allow for high-availability and load-balancing. The function of load-balancing (multiplexing requests from external requests) can be achieved with a hardware load-balancer, or load-balancing software. This guide will outline the modifications required to Yellowfin's configuration to enable clustering, but not the external environment that directs incoming requests to particular nodes.
It is required that the load-balancing infrastructure delivers network traffic to the Yellowfin application server transparently - as if the packets were connecting directly to the application server. If Session Replication is not enabled, the load-balancing infrastructure will need to provide “sticky-session” functionality. This is where traffic for a user’s session is sent to the same node for the duration of their session.
Clustered Environment Components
...
Click here to learn more about this configuration.
Container Level Session Replication
...
Click here to learn more about this configuration.
Yellowfin Database Clustering
...
The Yellowfin license file is stored in the Yellowfin database, and because of this, the license must contain a reference to all hostnames in the cluster. A clustered license can be requested from Yellowfin.
Guide Topics
The following topics will help set up a Yellowfin cluster.
- Yellowfin cluster installation
- Application level messaging
- Background tasks
- Container level session replication
...
| Section | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
...