Scaling Progress OpenEdge Appserversmedia.progress.com/exchange/2014/slides/track2_scaling...•...

Scaling Progress OpenEdge Appservers

Syed Irfan Pasha Principal QA Engineer Progress Software

Michael Jackson Dies and Twitter Fries

© 2014 Progress Software Corporation. All rights reserved. 3

Twitter’s – Fail Whale


Twitter’s – Scalability Problem

Takeaways from the story of Twitter • Understand your software’s behavior and foresee its usage • Have a mechanism to identify Production issues and raise an alarm smartly

before your customers do it • Scalability acts as a key measure for the Quality of a Software


Agenda

OpenEdge Applications and Focus Areas for Scalability

Optimization Techniques for Appserver

Tomcat Web Server

• Tuning Techniques

• Different Types of Tomcat Connectors

Scaling OpenEdge Applications With Load Balancing

Q&A


Focus for Scalability in Progress OpenEdge Components

Presentation Layer OpenEdge Clients Open Clients Rollbase Mobile

Application Server OpenEdge Appserver

Database Server OpenEdge RDBMS OpenEdge Replication

Enterprise Services JMS Web Services ESB

Where to focus on scalability ?


OpenEdge Appservers and Applications

Classic Appserver

Pacific Appserver for OE

Web Server (OpenEdge Services/

Applications)

2 3

1 OpenEdge Appservers

OpenEdge

Non-OpenEdge Clients


Key Areas to be Focused for Scalability

Classic Appserver Webserver(Tomcat) Load Balancing

Most of the OpenEdge Adapters and certified using standard Java Container, which is Tomcat

Tomcat acts a Java Container for “Pacific AS for OE”

Optimization Techniques

Properties for high concurrency

Tuning techniques

Different Tomcat Connectors and their uses

Best Practices

Types of load balancing to be applied for OpenEdge applications

Methods for applying load balancing

Why Tomcat?


Typical Issues With Application Servers

No response from the server

Client request takes too long to execute

Server goes down very often

• Out of Memory

• Out of Heap space

• All kinds of requests goes to the same server

Web server needs to be restarted as the Application needs to be upgraded

Cannot execute more than a specific number of requests

Tuning Classic Appserver for Better Scalability


Tuning Options of Classic Appserver

maxClientInstance • Set to 512 by default

Heap Memory of the broker process • jvmArgs=-Xms<value> -Xmx<value>

Queuelimit • (Size of the Payload)/8k =

Queuelimit value

Deleting Persistent and Connection Procedures

Classic Appserver

Client Requests

ABL

Web Clients Open

Clients


OpenEdge Applications and its Environment

Mobile Clients

Webspeed Adapter

SOAP Adapter

AIA Adapter

REST Adapter

SOAP Clients

Webspeed Clients

OpenEdge Appserver

OpenEdge Services/Applications

OpenEdge Appserver OpenEdge Appserver

Web Server

Understanding the Tomcat Web Application Server


Handles communications between client and the Engine

Highest level of Container for processing servlets

Web Applications deployed in multiple hosts

Instance of the Tomcat Web Application Server which

contains one or more services

Routes requests between Clients and Web Applications

Server

Service

Tomcat and its Pieces

Engine

Host1

WebApp1

WebApp2

Host2

WebApp3

WebApp4

Connectors


Tuning Options in Tomcat Webserver

Tuning Webserver to scale for maximum client requests

JVM Tuning Threads and its

Properties

Compression Cache for Static Files


Tuning Options in Tomcat Webserver – JVM Tuning

The defaults are not for the Production Environment

Higher heap memory causes long pauses in Garbage Collection which will be affected in the response time

Know your needs and configure optimistic memory

Permgen space – Optimistic approach is to set almost 25–30% of total Java heap memory

JAVA_OPTS -Xms <value> -Xmx <value> -XX:MaxGCPauseMillis <value>

-XX:+PrintGC -XX:+PrintGCDetails

setenv.{bat/sh}


Properties



Tuning Options in Tomcat Webserver – Threads


Properties


minSpareThreads(10) maxThreads(50)

Con

curr

ent U

ser R

eque

sts

Threads Configuration + acceptCount(50)

Further client requests will be refused

OS buffers TCP (kernel’s listen queue)

Accept Count

AcceptCount ∝ Kernel’s listen queue

Maxthreads : 200 – 800 Optimize based on your Application


Tuning Options in Tomcat Webserver – Monitoring Threads

Properties can be configured in server.xml as below <Connector port="8080“ connectionTimeout="20000“ maxThreads="500“ />

http://<hostname>:<port>/manager Server Status


Tuning Options in Tomcat Webserver – Compression

Compression • Reduces the network payload but gobbles the computational power • Client and the webserver both should be configured for compression

0 2000 4000 6000 8000

10000 12000 14000 16000 18000

Create Update Read Delete

Exec

utio

n Ti

me

in m

s

Operations Performed

Client Execution Time for the Payload of 10000 Records

Compression Disabled Compression Enabled

Improvement of 110% in execution time after enabling compression

Network Payload/Bytes Transferred were

150 times less with compression


Tuning Options in Tomcat Webserver – Caching Static files

Allows caching the static files in the browser with a future expiration date

Reduces the load of calling the static files every time from the webserver

Mostly used for css, images, javascript and static html


Properties


<Context cacheMaxSize=”10240” cacheTTL=”60000” cachingAllowed=”true”>

content.xml

Tomcat Connectors


Tomcat Connectors – From the Perspective of OpenEdge

Server

Connectors

HTTP & AJP

Handles communications client and the Engi

Listens on a defined single port for connections

Engine

Web Applications

Ubroker

Starts Agents

OpenEdge Clients

Handles and manages communication between Client and Agent

ABL Business Logic

Agents

http://localhost:8080

AJP – Apache Jserv Protocol HTTP - HTTP 1.1 Protocol


Tomcat Connectors – HTTP

BIO Connector • Executes multiple requests on multiple threads

• Stable performance for applications with moderate traffic

• Consumes more system resources on a burst of requests

NIO Connector • Handles multiple connections using a couple

of poller threads

• Better managing of threads which shares threads for multiple concurrent users

APR Connector • Uses Apache Native Runtime library

• Mostly used for SSL as it uses OpenSSL library which is fastest

HTTP AJP

Web Server

HTTP – HTTP 1.1 Protocol

BIO – Blocking Input Output

NIO – Non-blocking Input Output

APR – Apache Portable Runtime


Tomcat HTTP Connectors – Which One to Choose

Option-1 Option-2

Stability BIO APR SSL APR NIO Low Concurrency BIO APR High Concurrency No Keep-Alive BIO APR High Concurrency Keep-Alive APR NIO


Tomcat Connectors – AJP

Tomcat to Apache over a Wire Protocol

Mostly used to serve tomcat behind Apache httpd and handle the traffic to the Tomcat clusters

Apache serves better static content and better caching mechanism

Secures tomcat with its inbuilt security features and third party libraries

Widely used as secure proxy servers

Examples – modjk, mod_proxy, mod_http_proxy

HTTP AJP

Tomcat Connectors – Why AJP

AJP – Apache Jserv Protocol


After Applying Tuning in Appserver and Webserver

What if your application is getting more and more hits • Followed all tuning possibilities and best practices

– Optimal JVM options, heap space etc. – Choosing right Connector for the Application – Enabled Compression – Optimal number of threads, connection timeouts

• What might go wrong – More and more requests conquer your webserver – Webserver Out of Memory – Client Requests exceeds the maximum number

of requests

Is adding more Computational resources

an ultimate solution for Scalability?

With all the tuning options, can we take

advantage of horizontal scalability?


Applying Scalability with a Load Balancer

Webspeed Adapter

SOAP Adapter

AIA Adapter

REST Adapter

OpenEdge Appserver



Web Server Instance 1

Webspeed Adapter

SOAP Adapter

AIA Adapter

REST Adapter

OpenEdge Appserver




Nameserver(alike)

Mobile Clients

SOAP Clients

Webspeed

Clients



Webspeed Adapter

SOAP Adapter

AIA Adapter

REST Adapter

OpenEdge Appserver




Webspeed Adapter

SOAP Adapter

AIA Adapter

REST Adapter

OpenEdge Appserver




Nameserver(alike)

Mobile Clients

SOAP Clients

Webspeed

Clients



Webspeed Adapter

SOAP Adapter

AIA Adapter

REST Adapter

OpenEdge Appserver




Webspeed Adapter

SOAP Adapter

AIA Adapter

REST Adapter

OpenEdge Appserver




Load Balancing using AJP

Mobile Clients

SOAP Clients

Webspeed

Clients

Load Balancing and its Techniques


Load Balancing With Apache

Tomcat instance 2

Tomcat instance 4

Tomcat instance 3

Tomcat instance 1

Apache HTTPD

Load Balancer

(mod_jk)

Configurations Tomcat – Set the AJP Port Mod_jk – Configure worker.properties with Tomcat instances details Apache HTTPD – Configure to send the traffic to the balancer



Mod_jk Configuration • Mod_jk acts a load balancer that is configured in the Apache HTTPD Server

• Properties of this connector is configured in worker.properties file

• Structure of the properties file – Worker.<tomcat node>.type = ajp13

– Worker.<tomcat-node>.port = <ajp port>

– Worker.<tomcat-node>.host = < hostname of the tomcat-node>

– Worker.list = <list of workers>

– Worker.balancer.type = lb

– Worker.balancer.balancer_workers = <tomcat-node1>,<tomcat-node2>

– Worker.stat.type = <any defined name for your worker status>

Generic Properties

Properties for Each Node



Tomcat instance 2

Tomcat instance 4

Tomcat instance 3

Tomcat instance 1

Apache HTTPD

Load Balancer

(mod_jk)

http://<hostname>:<apacheport>/myApp

1st Request



Tomcat instance 2

Tomcat instance 4

Tomcat instance 3

Tomcat instance 1

Apache HTTPD

Load Balancer

(mod_jk)


2nd Request



Tomcat instance 2

Tomcat instance 4

Tomcat instance 3

Tomcat instance 1

Apache HTTPD

Load Balancer

(mod_jk)


3rd Request



Tomcat instance 2

Tomcat instance 4

Tomcat instance 3

Tomcat instance 1

Apache HTTPD

Load Balancer

(mod_jk)


4th Request



Tomcat stance 2

Tomcat instance 4

Tomcat instance 3

Tomcat instance 1

Apache HTTPD

Load Balancer

(mod_jk)


X



Tomcat stance 2

Tomcat instance 4

Tomcat instance 3

Tomcat instance 1

Apache HTTPD

Load Balancer

(mod_jk)


5th Request

X



Tomcat stance 2

Tomcat instance 4

Tomcat instance 3

Tomcat instance 1

Apache HTTPD

Load Balancer

(mod_jk)


6th Request

X


Load Balancing With Tomcat Clusters

Basic Load Balancer Sticky Sessions/ Session Affinity Session Replication

Allows a user to route the traffic across different nodes

Persists the users session for a single node

Replicates the session across multiple nodes of the load balancer

HTTP Stateless Clients HTTP Stateful Clients



Session Replication • Provides High Availability and Fail-over tolerance in a clustered environment

• Enable multicast routing in your server machine

• Enable/Add Cluster configuration in Tomcat

• Add <distributable> tag to the Web Application

Enables all the cluster nodes join the multicast group and sends the heartbeat

signals for certain intervals

As part of creating and managing the session, it replicates the session to all

tomcat nodes

Multicast Tomcat Session Manager

Configuring Session Replication



Tomcat instance 2

Tomcat instance 4

Tomcat instance 3

Tomcat instance 1

Apache HTTPD

Load Balancer

(mod_jk)


1st Request

Session Context

Session created for 1st Request



Tomcat instance 2

Tomcat instance 4

Tomcat instance 3

Tomcat instance 1

Apache HTTPD

Load Balancer

(mod_jk)


1st Request

Session Context

Replicating the session across multiple instances using Apache Tribes Group



Tomcat instance 2

Tomcat instance 4

Tomcat instance 3

Tomcat instance 1

Apache HTTPD

Load Balancer

(mod_jk)


1st Request

Session Context

Session Context

Session Context

Session Context



Tomcat instance 2

Tomcat instance 4

Tomcat instance 3

Tomcat instance 1

Apache HTTPD

Load Balancer

(mod_jk)


2nd Request

Session Context

Session Context

Session Context

Session Context



Tomcat instance 2

Tomcat instance 4

Tomcat instance 3

Tomcat instance 1

Apache HTTPD

Load Balancer

(mod_jk)


3rd Request

Session Context

Session Context

Session Context

Session Context



Tomcat instance 2

Tomcat instance 4

Tomcat instance 3

Tomcat instance 1

Apache HTTPD

Load Balancer

(mod_jk)


4th Request

Session Context

Session Context

Session Context

Session Context



Tomcat instance 2

Tomcat instance 4

Tomcat instance 3

Tomcat tance 1

Apache HTTPD

Load Balancer

(mod_jk)


4th Request

Session Context

Session Context

Session Context

Session Context

X


Summary

Classic Appserver

Tomcat Web Server

Load Balancing

1. Tuning Classic Appserver 2. Properties and best practices

1. Tuning Tomcat Webserver 2. Choosing the right Connector

Scalability

1. Applying Load balancing for OpenEdge Applications 2. Stateless and Stateful Requests


References

http://tomcat.apache.org/tomcat-7.0-doc/config/http.html

http://tomcatexpert.com/sites/default/files/PerformanceTuningApacheTomcat-Part2.pdf

http://tomcat.apache.org/connectors-doc/generic_howto/loadbalancers.html

http://tomcat.apache.org/connectors-doc/generic_howto/loadbalancers.html

Q&A


Want to Learn More About OpenEdge 11?

Role-based learning paths are available for OpenEdge 11

Each course is available as Instructor-led training or eLearning

Instructor-led training:

• $500 per student per day

• https://www.progress.com/support-and-services/education/instructor-led-training

eLearning:

• Via the Progress Education Community (https://wbt.progress.com):

• OpenEdge Developer Catalog: $1500 per user per year

• OpenEdge Administrator Catalog: $900 per user per year

User Assistance videos: https://www.progress.com/products/pacific/help/openedge

Get session details & presentation downloads Complete a survey Access the latest Progress product literature

www.progress.com/exchange2014

Visit the Resource Portal

Date post:	18-Mar-2018
Category:	Documents
Upload:	buidien
View:	222 times
Download:	5 times

Scaling Progress OpenEdge Appserversmedia.progress.com/exchange/2014/slides/track2_scaling...•...

Documents