Scaling Progress OpenEdge Appservers. Syed Irfan Pasha Principal QA Engineer Progress Software

Transcription

1 Scaling Progress OpenEdge Appservers Syed Irfan Pasha Principal QA Engineer Progress Software

2 Michael Jackson Dies and Twitter Fries

3 Twitter s Fail Whale 3

4 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 4

5 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 5

6 Focus for Scalability in Progress OpenEdge Components Presentation Layer OpenEdge Clients Open Clients Rollbase Mobile Enterprise Services JMS Web Services ESB Application Server OpenEdge Appserver Where to focus on scalability? OpenEdge RDBMS Database Server OpenEdge Replication 6

7 OpenEdge Appservers and Applications 2 3 OpenEdge Non-OpenEdge Clients Web Server (OpenEdge Services/ Applications) Classic Appserver Pacific Appserver for OE 1 OpenEdge Appservers 7

8 Key Areas to be Focused for Scalability Classic Appserver Webserver(Tomcat) Load Balancing 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? Most of the OpenEdge s and certified using standard Java Container, which is Tomcat Tomcat acts a Java Container for Pacific AS for OE 8

9 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 9

10 Tuning Classic Appserver for Better Scalability

11 Tuning Options of Classic Appserver Client Requests ABL Web Clients Classic Appserver Open Clients 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 11

12 OpenEdge Applications and its Environment Mobile Clients SOAP Clients Webspeed Clients Web Server Webspeed SOAP AIA REST OpenEdge Services/Applications OpenEdge Appserver OpenEdge Appserver OpenEdge Appserver 12

13 Understanding the Tomcat Web Application Server

14 Tomcat and its Pieces Service Server Connectors Instance of the Tomcat Web Application Server which contains one or more services Routes requests between Clients and Web Applications Host1 Engine Host2 Handles communications between client and the Engine WebApp1 WebApp2 WebApp3 WebApp4 Highest level of Container for processing servlets Web Applications deployed in multiple hosts 14

15 Tuning Options in Tomcat Webserver Tuning Webserver to scale for maximum client requests JVM Tuning Threads and its Properties Compression Cache for Static Files 15

16 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 JVM Tuning Compression Threads and its Properties Cache for Static Files setenv.{bat/sh} JAVA_OPTS -Xms <value> -Xmx <value> -XX:MaxGCPauseMillis <value> -XX:+PrintGC -XX:+PrintGCDetails 16

17 Tuning Options in Tomcat Webserver Threads Concurrent User Requests AcceptCount Kernel s listen queue Accept Count OS buffers TCP (kernel s listen queue) Further client requests will be refused JVM Tuning Compression Threads and its Properties Cache for Static Files minsparethreads(10) maxthreads(50) + acceptcount(50) Maxthreads : Optimize based on your Application Threads Configuration 17

18 Tuning Options in Tomcat Webserver Monitoring Threads Server Status Properties can be configured in server.xml as below <Connector port="8080 connectiontimeout="20000 maxthreads="500 /> 18

19 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 Execution Time in ms Client Execution Time for the Payload of Records Create Update Read Delete Operations Performed Improvement of 110% in execution time after enabling compression Compression Disabled Compression Enabled Network Payload/Bytes Transferred were 150 times less with compression 19

20 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 JVM Tuning Compression Threads and its Properties Cache for Static Files content.xml <Context cachemaxsize= cachettl= cachingallowed= true > 20

21 Tomcat Connectors

22 Tomcat Connectors From the Perspective of OpenEdge Server Connectors HTTP & AJP Engine Web Applications Handles communications client and the Engi Listens on a defined single port for connections Starts Agents OpenEdge Clients Ubroker Handles and manages communication between Client and Agent Agents HTTP - HTTP 1.1 Protocol AJP Apache Jserv Protocol ABL Business Logic 22

23 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 Web Server HTTP AJP HTTP HTTP 1.1 Protocol BIO Blocking Input Output NIO Non-blocking Input Output APR Apache Portable Runtime 23

24 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 24

25 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 Tomcat Connectors Why AJP Apache serves better static content and better caching mechanism Secures tomcat with its inbuilt security features and third party libraries HTTP AJP Widely used as secure proxy servers Examples modjk, mod_proxy, mod_http_proxy AJP Apache Jserv Protocol 25

26 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? 26

27 Applying Scalability with a Load Balancer Mobile Clients SOAP Clients Webspeed Clients Nameserver(alike) Web Server Instance 1 Web Server Instance 2 Webspeed SOAP AIA REST Webspeed SOAP AIA REST OpenEdge Services/Applications OpenEdge Services/Applications OpenEdge Appserver OpenEdge Appserver OpenEdge Appserver OpenEdge Appserver OpenEdge Appserver OpenEdge Appserver 27

28 Applying Scalability with a Load Balancer Mobile Clients SOAP Clients Webspeed Clients Nameserver(alike) Web Server Instance 1 Web Server Instance 2 Webspeed SOAP AIA REST Webspeed SOAP AIA REST OpenEdge Services/Applications OpenEdge Services/Applications OpenEdge Appserver OpenEdge Appserver OpenEdge Appserver OpenEdge Appserver OpenEdge Appserver OpenEdge Appserver 28

29 Applying Scalability with a Load Balancer Mobile Clients SOAP Clients Webspeed Clients Load Balancing using AJP Web Server Instance 1 Web Server Instance 2 Webspeed SOAP AIA REST Webspeed SOAP AIA REST OpenEdge Services/Applications OpenEdge Services/Applications OpenEdge Appserver OpenEdge Appserver OpenEdge Appserver OpenEdge Appserver OpenEdge Appserver OpenEdge Appserver 29

30 Load Balancing and its Techniques

31 Load Balancing With Apache Tomcat instance 1 Apache HTTPD Tomcat instance 2 Load Balancer (mod_jk) Tomcat instance 3 Tomcat instance 4 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 31

32 Load Balancing With Apache 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> Properties for Each 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 32

33 Load Balancing With Apache Tomcat instance 1 1 st Request Apache HTTPD Tomcat instance 2 Load Balancer (mod_jk) Tomcat instance 3 Tomcat instance 4 33

34 Load Balancing With Apache Tomcat instance 1 Apache HTTPD Load Balancer (mod_jk) Tomcat instance 2 2 nd Request Tomcat instance 3 Tomcat instance 4 34

35 Load Balancing With Apache Tomcat instance 1 Apache HTTPD Tomcat instance 2 Load Balancer (mod_jk) Tomcat instance 3 3 rd Request Tomcat instance 4 35

36 Load Balancing With Apache Tomcat instance 1 Apache HTTPD Tomcat instance 2 Load Balancer (mod_jk) Tomcat instance 3 Tomcat instance 4 4 th Request 36

37 Load Balancing With Apache Tomcat instance 1 Apache HTTPD Load Balancer (mod_jk) X Tomcat stance 2 Tomcat instance 3 Tomcat instance 4 37

38 Load Balancing With Apache Tomcat instance 1 Apache HTTPD Load Balancer (mod_jk) 5 th Request X Tomcat stance 2 Tomcat instance 3 Tomcat instance 4 38

39 Load Balancing With Apache Tomcat instance 1 Apache HTTPD Load Balancer (mod_jk) X Tomcat stance 2 Tomcat instance 3 6 th Request Tomcat instance 4 39

40 Load Balancing With Tomcat Clusters HTTP Stateless Clients HTTP Stateful Clients Basic Load Balancer Allows a user to route the traffic across different nodes Sticky Sessions/ Session Affinity Persists the users session for a single node Session Replication Replicates the session across multiple nodes of the load balancer 40

41 Load Balancing With Tomcat Clusters Session Replication Provides High Availability and Fail-over tolerance in a clustered environment Multicast Tomcat Session Manager Enables all the cluster nodes join the multicast group and sends the heartbeat signals for certain intervals Enable multicast routing in your server machine Enable/Add Cluster configuration in Tomcat Add <distributable> tag to the Web Application As part of creating and managing the session, it replicates the session to all tomcat nodes Configuring Session Replication 41

42 Load Balancing With Tomcat Clusters Session created for 1 st Request Tomcat instance 1 Session Context Apache HTTPD Tomcat instance 2 Load Balancer (mod_jk) Tomcat instance 3 Tomcat instance 4 1 st Request 42

43 Load Balancing With Tomcat Clusters Tomcat instance 1 Session Context Apache HTTPD Load Balancer (mod_jk) Tomcat instance 2 Tomcat instance 3 Replicating the session across multiple instances using Apache Tribes Group Tomcat instance 4 1 st Request 43

44 Load Balancing With Tomcat Clusters Tomcat instance 1 Session Context Apache HTTPD Load Balancer (mod_jk) Tomcat instance 2 Tomcat instance 3 Session Context Session Context 1 st Request Tomcat instance 4 Session Context 44

45 Load Balancing With Tomcat Clusters Tomcat instance 1 Session Context Apache HTTPD Load Balancer (mod_jk) Tomcat instance 2 Tomcat instance 3 Session Context Session Context 2 nd Request Tomcat instance 4 Session Context 45

46 Load Balancing With Tomcat Clusters Tomcat instance 1 Session Context Apache HTTPD Load Balancer (mod_jk) Tomcat instance 2 Tomcat instance 3 Session Context Session Context 3 rd Request Tomcat instance 4 Session Context 46

47 Load Balancing With Tomcat Clusters Tomcat instance 1 Session Context Apache HTTPD Load Balancer (mod_jk) Tomcat instance 2 Tomcat instance 3 Session Context Session Context 4 th Request Tomcat instance 4 Session Context 47

48 Load Balancing With Tomcat Clusters X Tomcat tance 1 Session Context Apache HTTPD Load Balancer (mod_jk) Tomcat instance 2 Tomcat instance 3 Session Context Session Context 4 th Request Tomcat instance 4 Session Context 48

49 Summary 1. Tuning Classic Appserver 2. Properties and best practices Classic Appserver 1. Applying Load balancing for OpenEdge Applications 2. Stateless and Stateful Requests Load Balancing Scalability Tomcat Web Server 1. Tuning Tomcat Webserver 2. Choosing the right Connector 49

50 References doc/config/http.html uningapachetomcat-part2.pdf 50

51 Q&A

52 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 elearning: Via the Progress Education Community ( OpenEdge Developer Catalog: $1500 per user per year OpenEdge Administrator Catalog: $900 per user per year User Assistance videos: 26

53 Visit the Resource Portal Get session details & presentation downloads Complete a survey Access the latest Progress product literature

54