The Project Presentation April 28, 2006 18-749: Fault-Tolerant Distributed Systems Team 7-Sixers Kyu Hou Minho Jeung Wangbong Lee Heejoon Jung Wen Shu.

Slides:



Advertisements
Similar presentations
Performance Testing - Kanwalpreet Singh.
Advertisements

Database Architectures and the Web
Sanjay Ghemawat, Howard Gobioff and Shun-Tak Leung
Chapter 13 (Web): Distributed Databases
A Dependable Auction System: Architecture and an Implementation Framework
Chapter 16 Client/Server Computing Patricia Roy Manatee Community College, Venice, FL ©2008, Prentice Hall Operating Systems: Internals and Design Principles,
Team 1: Box Office : Analysis of Software Artifacts : Dependability Analysis of Middleware JunSuk Oh, YounBok Lee, KwangChun Lee, SoYoung Kim,
Distributed Systems Architectures
A brief look at CORBA. What is CORBA Common Object Request Broker Architecture developed by OMG Combine benefits of OO and distributed computing Distributed.
Team 2: The House Party Blackjack Mohammad Ahmad Jun Han Joohoon Lee Paul Cheong Suk Chan Kang.
Introduction to Web Interface Technology (CSE2030)
Multiple Tiers in Action
Milos Kobliha Alejandro Cimadevilla Luis de Alba Parallel Computing Seminar GROUP 12.
Team 6: Slackers 18749: Fault Tolerant Distributed Systems Team Members Puneet Aggarwal Karim Jamal Steven Lawrance Hyunwoo Kim Tanmay Sinha.
1 Philippe. Team 3: Spam’n’Beans : Analysis of Software Artifacts : Dependability Analysis of Middleware Gary Ackley Andrew Boyer Charles.
Chapter 12 Distributed Database Management Systems
1 Programming systems for distributed applications Seif Haridi KTH/SICS.
Introduction to Web Interface Technology (CSE2030)
Team 4: : Fault-Tolerant Distributed Systems Bryan Murawski Meg Hyland Jon Gray Joseph Trapasso Prameet Shah Michael Mishkin.
DISTRIBUTED COMPUTING
Database System Architectures  Client-server Database System  Parallel Database System  Distributed Database System Wei Jiang.
Parallel & Distributed databases Agenda –The problem domain of design parallel & distributed databases (chp 18-20) –The data allocation problem –The data.
1 Copyright © 2009, Oracle. All rights reserved. Exploring the Oracle Database Architecture.
© 2011 IBM Corporation 11 April 2011 IDS Architecture.
Sys Prog & Scripting - HW Univ1 Systems Programming & Scripting Lecture 15: PHP Introduction.
Distributed Data Stores – Facebook Presented by Ben Gooding University of Arkansas – April 21, 2015.
1 Distributed Processing, Client/Server, and Clusters Chapter 13.
Database Design – Lecture 16
B.Ramamurthy9/19/20151 Operating Systems u Bina Ramamurthy CS421.
M i SMob i S Mob i Store - Mobile i nternet File Storage Platform Chetna Kaur.
Fundamentals of Database Chapter 7 Database Technologies.
By Matt Deakyne, Adam Krasny, and Derek Meek. History of ICE ICE stands for Internet Communications Engine Object-oriented middleware allowed programmers.
1 of of 25 3 of 25 ORBs (Object Request Broker) – A distributed software bus for communication among middleware services and applications – To.
SUMA: A Scientific Metacomputer Cardinale, Yudith Figueira, Carlos Hernández, Emilio Baquero, Eduardo Berbín, Luis Bouza, Roberto Gamess, Eric García,
Client – Server Architecture. Client Server Architecture A network architecture in which each computer or process on the network is either a client or.
Contents 1.Introduction, architecture 2.Live demonstration 3.Extensibility.
Database Systems: Design, Implementation, and Management Ninth Edition Chapter 12 Distributed Database Management Systems.
Team 5: Virtual Online Blackjack : Analysis of Software Artifacts : Dependability Analysis of Middleware Philip Bianco John Robert Vorachat.
Middleware for FIs Apeego House 4B, Tardeo Rd. Mumbai Tel: Fax:
FailSafe SGI’s High Availability Solution Mayank Vasa MTS, Linux FailSafe Gatekeeper
Introduction to dCache Zhenping (Jane) Liu ATLAS Computing Facility, Physics Department Brookhaven National Lab 09/12 – 09/13, 2005 USATLAS Tier-1 & Tier-2.
SE-02 COMPONENTS – WHY? Object-oriented source-level re-use of code requires same source code language. Object-oriented source-level re-use may require.
Lecture 22: Client-Server Software Engineering
Lesson Overview 3.1 Components of the DBMS 3.1 Components of the DBMS 3.2 Components of The Database Application 3.2 Components of The Database Application.
Title Line Subtitle Line Top of Content Box Line Top of Footer Line Left Margin LineRight Margin Line Top of Footer Line Top of Content Box Line Subtitle.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 14 Database Connectivity and Web Technologies.
Shuman Guo CSc 8320 Advanced Operating Systems
Database Server Concepts and Possibilities Lee Lueking D0 Data Browser Workshop April 8, 2002.
Process Architecture Process Architecture - A portion of a program that can run independently of and concurrently with other portions of the program. Some.
System Center Lesson 4: Overview of System Center 2012 Components System Center 2012 Private Cloud Components VMM Overview App Controller Overview.
Module 4: Design IIS Maintenance and UDDI. Designing Internet Information Services Backup and Recovery Specifying Monitoring requirements Deploying UDDI.
WEB SERVER SOFTWARE FEATURE SETS
Distributed System Architectures Yonsei University 2 nd Semester, 2014 Woo-Cheol Kim.
The Storage Resource Broker and.
EJB Enterprise Java Beans JAVA Enterprise Edition
1 LM 6 Database Applications Dr. Lei Li. Learning Objectives Explain three components of a client-server system Describe differences between a 2-tiered.
 Project Team: Suzana Vaserman David Fleish Moran Zafir Tzvika Stein  Academic adviser: Dr. Mayer Goldberg  Technical adviser: Mr. Guy Wiener.
Data Sharing Service Kiran Devaram Samatha Gangapuram Harish Maringanti Prashant Shanti Kumar Pradeep Tallogu.
Architecture Review 10/11/2004
Introduction to Distributed Platforms
PHP / MySQL Introduction
Software Engineering Introduction to Apache Hadoop Map Reduce
Replication Middleware for Cloud Based Storage Service
Database Driven Websites
Operating Systems Bina Ramamurthy CSE421 11/27/2018 B.Ramamurthy.
Operating Systems : Overview
Operating Systems : Overview
Operating Systems : Overview
COMPONENTS – WHY? Object-oriented source-level re-use of code requires same source code language. Object-oriented source-level re-use may require understanding.
UFCEUS-20-2 Web Programming
Presentation transcript:

The Project Presentation April 28, : Fault-Tolerant Distributed Systems Team 7-Sixers Kyu Hou Minho Jeung Wangbong Lee Heejoon Jung Wen Shu Tang

2 Members Kyu Hou MSE Min Ho Jeung MSE Wangbong Lee MSE Heejoon Jung MSIT-SE Wen Shu Tang ECE

3 Baseline Application Express Bus Ticket Center Express Bus Ticket Center Application Application Online express bus ticketing application Configuration Configuration Operating System: Linux servers Programming Language: Java Database: MySQL Middleware: CORBA Baseline Application Feature Baseline Application Feature Users can retrieve bus schedules and tickets. Users can buy tickets. Users can cancel the tickets.

4 Baseline Architecture Database Pool of Customers Bus Ticket System ① ② ③ ④ ① ④ Allocation View-Deployment Style Legend Internet Client Server Database Request Call Response Call Request Query Response Query

5 Baseline Architecture Database Pool of CustomersBus Ticket System ① ③④ Allocation View-Deployment Style Legend Client Server Database Request Call Response Call Request Query Response Query ② User Interface Client CORBA Interface MySQL Server CORBA Interface JDBCBusiness Logic

6 Client requests should be preserved, when exception is occurred. Replication  There are 2 copies of server which perform same operations for fault- tolerance on the chess and risk machine.  Replication Type Active Replication Advantage: Performance Disadvantage: More memory and processing cost  State Stateless We stored the state into database.  Replication Manager No specific replication manager exists. As soon as client application begins, the application acquires the replication informaion which is stored in Naming Server. Elements of Fault-Tolerance Framework  Global Manager: Heartbeat  Recovery Manager Re-instantiating a failed replication The recovery result is written into a log file in Database.  Fault injector: Shell Fault-Tolerance Goals

7 Scenario Scenario 1. Client requests the names of server to the naming server. 2. The naming server sends the names of servers. 3. Client sends its state to all servers. a. When the client receives an exception message, then the fault is detected. a. When the client receives an exception message, then the fault is detected. b. The client will communicate with another replication server. b. The client will communicate with another replication server. 4. All servers send the results to clients. 5. Client receives the results, and checks duplication. FT-Baseline Architecture

Exception Cases Exception Cases  Server_Timeout Checked by using thread pool  Database_Timeout: Checked by using connection pool  Dead_Server Solved by using heartbeat (check servers per 2 seconds) Global Recovery Manager: Heartbeat When do you obtain the names of the server references? What if you run out of live references? Mechanisms for Fail-Over

9 Performance measurement 48 Configurations 48 Configurations Buy and cancel ticket Buy and cancel ticket

us Performance measurement

Component break down

1 Client 1000 requests Cancel ticket request Fault Injection measurements

Performance measurement w/o fault injection

17 RT-FT Baseline Architecture Active Active

18 Thread Pool  We need to avoid the overhead of thread creation for each request.  Create a number of threads at initialize time Dynamic configuration  Without Thread Pool AVG RTT: 47.5 msec  With Thread Pool AVR RTT: 38.1 msec  Improve the performance about 20% RT-FT Performance Strategy

19 Thread Pool / No Thread Pool RT-FT Performance Measurement

20 List other features  Fault Injector – Shell Script  Log4j – Logging information  Apach DB Connection Pool (DBCP) What lessons by other features?  Useful utilities  Improve performance by DBCP  Powerful shell scripts Other Feature