This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
QlikView Load Balancing Scenarios
OverviewThis document shows several scenarios for load balancing clustered servers with
QlikView 9 and above. It is intended to act as a guide for discussions and
architecture planning for large deployments. These scenarios are not best
practices, but are instead examples of configurations that provide distinct
advantages for different scalability scenarios.
The subsequent pages in this document describe the scenarios. Please note: while
all of these scenarios depict two (2) QlikView Servers clustered together, the same
capabilities apply to clusters of 3-to-n servers. A 2-server cluster was shown on
each scenario to simplify the diagram and discussion to the relevant points.
It is assumed that the audience is familiar with the QlikView architecture and
clustering concepts prior to reading these scenarios.
trademarks or registered trademarks of QlikTech International AB. All other company names, products and services used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice.
This publication is for informational purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The only warranties for QlikTech products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting any additional warranty.
QlikView Load Balancing Scenarios
Key Features of QlikView for Load BalancingLoad balancing has been available with QlikView prior to version 9, but it required external
hardware and software to make it work, namely an NLB or switch device to determine the load
balancing methodology and to route the traffic accordingly.
With QlikView 9 and above, the QlikView AccessPoint now has the capability of performing
most of these capabilities for us, and goes beyond the traditional features with its new
document awareness capability. The ability for the AccessPoint to determine whether or not a
document is already loaded in memory on each of the clustered servers means that it can now
accommodate unbalanced clusters of servers. Meaning, we can take advantage of certain
applications (QlikView documents) only residing on some of the servers and not others.
This allows us to configure clusters that provide the traditional failover and redundancy, but
can also be dedicated to certain applications. It is important to note that when an application
(QlikView document) is loaded on one server but not the other server in a cluster, the server
with the application loaded in memory will receive all of the sessions requesting that
application, until that server has no availability, at which time the other server will load the
application into memory and begin serving requested sessions. The pre-loading of
applications into the servers is what drives this behavior. This functionality is not yet built into
the QlikView Management Console. This means manual pre-loading or an external process
to pre-load will be needed until this feature is integrated into the QEMC.
Scenarios 1 and 2 are the most popular with large QlikView deployments, but the other
scenarios are also useful when dealing with more specific technical requirements.
trademarks or registered trademarks of QlikTech International AB. All other company names, products and services used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice.
This publication is for informational purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The only warranties for QlikTech products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting any additional warranty.
SAN/NAS/Shared Disk
QlikView Load Balancing Scenarios
Goal is equal distribution of load
When you need high availability and
resiliency both
When the web traffic for AJAX clients
and custom web apps is light enough to
not need dedicated AccessPoints
Server Availability
Round robin
Session counts
RAM/CPU available
When would you use this:
Pros:
Cons:
Scenario #1:
Balanced cluster utilizing NLB or switch and resident AccessPoints
trademarks or registered trademarks of QlikTech International AB. All other company names, products and services used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice.
This publication is for informational purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The only warranties for QlikTech products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting any additional warranty.
Note: AccessPoints are
resident on the QlikView
servers in this scenario
SAN/NAS/Shared Disk
QlikView Load Balancing Scenarios
Goal is equal distribution of load
When you need high availability and
resiliency both
When the web traffic for AJAX clients
and custom web apps is heavy enough
to need dedicated AccessPoints
Server Availability
Round robin
Session counts
RAM/CPU available
When would you use this:
Pros:
Cons:
Scenario #2:
Balanced cluster utilizing NLB or switch and dedicated AccessPoints
trademarks or registered trademarks of QlikTech International AB. All other company names, products and services used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice.
This publication is for informational purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The only warranties for QlikTech products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting any additional warranty.
trademarks or registered trademarks of QlikTech International AB. All other company names, products and services used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice.
This publication is for informational purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The only warranties for QlikTech products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting any additional warranty.
Note: AccessPoint can
be on dedicated server
or resident on one of the
two QlikView Servers in
the diagram
Goal is primary server with clustered
secondary server providing failover
Primary server RAM/CPU sufficient for
all production sessions
When would you use this:
Pros:
Cons:
Scenario #4:
Full failover cluster utilizing QlikView AccessPoint
trademarks or registered trademarks of QlikTech International AB. All other company names, products and services used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice.
This publication is for informational purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The only warranties for QlikTech products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting any additional warranty.
trademarks or registered trademarks of QlikTech International AB. All other company names, products and services used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice.
This publication is for informational purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The only warranties for QlikTech products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting any additional warranty.
trademarks or registered trademarks of QlikTech International AB. All other company names, products and services used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice.
This publication is for informational purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The only warranties for QlikTech products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting any additional warranty.
trademarks or registered trademarks of QlikTech International AB. All other company names, products and services used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice.
This publication is for informational purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The only warranties for QlikTech products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting any additional warranty.