Election AlgorithmsCS-4513, D-Term 20071 Synchronization (continued) CS-4513 D-Term 2007 (Slides include materials from Operating System Concepts, 7 th.

Slides:



Advertisements
Similar presentations
CS 542: Topics in Distributed Systems Diganta Goswami.
Advertisements

CS425 /CSE424/ECE428 – Distributed Systems – Fall 2011 Material derived from slides by I. Gupta, M. Harandi, J. Hou, S. Mitra, K. Nahrstedt, N. Vaidya.
Replication. Topics r Why Replication? r System Model r Consistency Models r One approach to consistency management and dealing with failures.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED.
Domain Name System. DNS is a client/server protocol which provides Name to IP Address Resolution.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved Naming (2) DISTRIBUTED.
CS 582 / CMPE 481 Distributed Systems
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
GrapevineCS-4513, D-Term Introduction to the Grapevine Distributed System CS-4513 Distributed Computing Systems.
More on Replication and Consistency CS-4513, D-Term More on Replication and Consistency CS-4513 D-Term 2007 (Slides include materials from Operating.
Election AlgorithmsCS-4513 D-term Election Algorithms CS-4513 Distributed Computing Systems (Slides include materials from Operating System Concepts,
Oct 21, 2004CS573: Network Protocols and Standards1 IP: Addressing, ARP, Routing Network Protocols and Standards Autumn
NamingCS-4513, D-Term Naming CS-4513 Distributed Computing Systems (Slides include materials from Operating System Concepts, 7 th ed., by Silbershatz,
Application Layer At long last we can ask the question - how does the user interface with the network?
SynchronizationCS-4513, D-Term Synchronization in Distributed Systems CS-4513 D-Term 2007 (Slides include materials from Operating System Concepts,
Replication and Consistency CS-4513 D-term Replication and Consistency CS-4513 Distributed Computing Systems (Slides include materials from Operating.
Synchronization in Distributed Systems CS-4513 D-term Synchronization in Distributed Systems CS-4513 Distributed Computing Systems (Slides include.
Domain Name System: DNS
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
MCTS Guide to Microsoft Windows Server 2008 Network Infrastructure Configuration Chapter 5 Introduction to DNS in Windows Server 2008.
Distributed Systems CS Programming Models- Part I Lecture 13, Oct 13, 2014 Mohammad Hammoud 1.
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network, Enhanced Chapter 7: Planning a DNS Strategy.
NamingCS-4513, D-Term Naming CS-4513 Distributed Computing Systems (Slides include materials from Operating System Concepts, 7 th ed., by Silbershatz,
Naming Names in computer systems are used to share resources, to uniquely identify entities, to refer to locations and so on. An important issue with naming.
More on Replication and Consistency CS-4513 D-term More on Replication and Consistency CS-4513 Distributed Computing Systems (Slides include materials.
Computer Science Lecture 12, page 1 CS677: Distributed OS Last Class Vector timestamps Global state –Distributed Snapshot Election algorithms.
DNS. Outline r Domain Name System r DNS Hierarchy r Resolution.
DNS Domain Name Service References: Wikipedia 1.
Election Algorithms and Distributed Processing Section 6.5.
Election Algorithms. Topics r Issues r Detecting Failures r Bully algorithm r Ring algorithm.
Domain Name Services Oakton Community College CIS 238.
1 Chapter Overview Understanding Windows Name Resolution Using WINS.
Hands-On Microsoft Windows Server 2008 Chapter 8 Managing Windows Server 2008 Network Services.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Microsoft Windows 2003 Server. Client/Server Environment Many client computers connect to a server.
Name Resolution Domain Name System.
Chapter 16 – DNS. DNS Domain Name Service This service allows client machines to resolve computer names (domain names) to IP addresses DNS works at the.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved Chapter 6 Synchronization.
5.1 Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED.
Naming Chapter 4.
October 8, 2015 University of Tulsa - Center for Information Security Microsoft Windows 2000 DNS October 8, 2015.
Computer Science Lecture 10, page 1 CS677: Distributed OS Last Class: Naming Name distribution: use hierarchies DNS X.500 and LDAP.
Computer Science Lecture 9, page 1 CS677: Distributed OS Last Class: Naming Name distribution: use hierarchies DNS Iterative versus Recursive name resolution.
Page 1 Distributed Systems Election Algorithms* *referred to slides by Prof. Hugh C. Lauer at Worcester Polytechnic Institute.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Configuring Name Resolution and Additional Services Lesson 12.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Replication (1). Topics r Why Replication? r System Model r Consistency Models – How do we reason about the consistency of the “global state”? m Data-centric.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
DNS DNS overview DNS operation DNS zones. DNS Overview Name to IP address lookup service based on Domain Names Some DNS servers hold name and address.
Replication (1). Topics r Why Replication? r System Model r Consistency Models r One approach to consistency management and dealing with failures.
DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S
Linux Operations and Administration
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Page 1 Mutual Exclusion & Election Algorithms Paul Krzyzanowski Distributed Systems Except as otherwise noted, the content.
TCP/IP Protocol Suite 1 Chapter 17 Upon completion you will be able to: Domain Name System: DNS Understand how the DNS is organized Know the domains in.
COMP 655: Distributed/Operating Systems Summer 2011 Dr. Chunbo Chu Week 6: Synchronyzation 3/5/20161 Distributed Systems - COMP 655.
Mutual Exclusion Algorithms. Topics r Defining mutual exclusion r A centralized approach r A distributed approach r An approach assuming an organization.
CSE 486/586 CSE 486/586 Distributed Systems Leader Election Steve Ko Computer Sciences and Engineering University at Buffalo.
Basics of the Domain Name System (DNS) By : AMMY- DRISS Mohamed Amine KADDARI Zakaria MAHMOUDI Soufiane Oujda Med I University National College of Applied.
Distributed Systems Lecture 9 Leader election 1. Previous lecture Middleware RPC and RMI – Marshalling 2.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
IMPLEMENTING NAME RESOLUTION USING DNS
Distributed Processing Election Algorithm
Net 323 D: Networks Protocols
7.1. CONSISTENCY AND REPLICATION INTRODUCTION
DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S
Presentation transcript:

Election AlgorithmsCS-4513, D-Term Synchronization (continued) CS-4513 D-Term 2007 (Slides include materials from Operating System Concepts, 7 th ed., by Silbershatz, Galvin, & Gagne, Modern Operating Systems, 2 nd ed., by Tanenbaum, and Distributed Systems: Principles & Paradigms, 2 nd ed. By Tanenbaum and Van Steen)

Election AlgorithmsCS-4513, D-Term Review Real time not very good tool for some kinds of synchronization is distributed systems Logical “clocks” Always monotonic Moved forward whenever a “later” message appears Mutual exclusion Centralized control Decentralized & Distributed control Token control

Election AlgorithmsCS-4513, D-Term NTP (Network Time Protocol) Question: what is  = T B – T A ? Assume transit time is approximately the same both ways Assume that B is the time server that A wants to synchronize to A B T1T1 T2T2 T3T3 T4T4

Election AlgorithmsCS-4513, D-Term NTP (Network Time Protocol) A knows (T 4 – T 1 ) from its own clock B reports T 3 and T 2 in response to NTP request A computes total transit time of A B T1T1 T2T2 T3T3 T4T4

Election AlgorithmsCS-4513, D-Term One-way transit time is approximately ½ total, i.e., B’s clock at T 4 reads approximately NTP (Network Time Protocol) A B T1T1 T2T2 T3T3 T4T4

Election AlgorithmsCS-4513, D-Term NTP (Network Time Protocol) B’s clock at T 4 reads approximately (from previous slide) Thus, difference between B and A clocks at T 4 is A B T1T1 T2T2 T3T3 T4T4

Election AlgorithmsCS-4513, D-Term Questions?

Election AlgorithmsCS-4513, D-Term Election Algorithms If we are using one process as a coordinator for a shared resource … …how do we select that one process? Often, there is no owner or master that is automatically considered as coordinator E.g., Grapevine, there is no owner for a Registry By contrast:–DNS has a master for every domain

Election AlgorithmsCS-4513, D-Term Solution – an Election All nodes currently involved get together to choose a coordinator If the coordinator crashes or becomes isolated, elect a new coordinator If a previously crashed or isolated node, comes on line, a new election may have to be held.

Election AlgorithmsCS-4513, D-Term Election Algorithms Wired systems Bully algorithm Ring algorithm Wireless systems Very large-scale systems

Election AlgorithmsCS-4513, D-Term Bully Algorithm Assume All processes know about each other Processes numbered uniquely Suppose P notices no coordinator Sends election message to all higher numbered processes If none response, P takes over as coordinator If any responds, P yields …

Election AlgorithmsCS-4513, D-Term Bully Algorithm (continued) … Suppose Q receives election message Replies OK to sender, saying it will take over Sends a new election message to higher numbered processes Repeat until only one process left standing Announces victory by sending message saying that it is coordinator

Election AlgorithmsCS-4513, D-Term Bully Algorithm (continued)

Election AlgorithmsCS-4513, D-Term Bully Algorithm (continued) … Suppose R comes back on line Sends a new election message to higher numbered processes Repeat until only one process left standing Announces victory by sending message saying that it is coordinator (if not already coordinator) Existing (lower numbered) coordinator yields Hence the term “bully”

Election AlgorithmsCS-4513, D-Term Alternative – Ring Algorithm All processed organized in ring Independent of process number Suppose P notices no coordinator Sends election message to successor with own process number in body of message (If successor is down, skip to next process, etc.) Suppose Q receives an election message Adds own process number to list in message body …

Election AlgorithmsCS-4513, D-Term Alternative – Ring Algorithm Suppose P receives an election message with its own process number in body Changes message to coordinator message, preserving body All processes recognize highest numbered process as new coordinator If multiple messages circulate … …they will all contain same list of processes (eventually) If process comes back on-line Calls new election

Election AlgorithmsCS-4513, D-Term Ring Algorithm (continued)

Election AlgorithmsCS-4513, D-Term Wireless Networks Different assumptions Message passing is less reliable Network topology constantly changing Expanding ring of broadcast Election messages Decision rules for when to yield Not very well developed. Topic of current research

Election AlgorithmsCS-4513, D-Term Very Large Scale Networks Sometimes more than one node should be selected Nodes organized as peers and super-peers Elections held within each peer group Super-peers coordinate among themselves

Election AlgorithmsCS-4513, D-Term Questions?

Election AlgorithmsCS-4513, D-Term Digression Domain Name Service

Election AlgorithmsCS-4513, D-Term DNS Maps names of the form to IP addresses Maps aliases to names Maps mailbox requests to names Maps service requests to names Maps IP addresses to names I.e., reverse mapping

Election AlgorithmsCS-4513, D-Term DNS Naming Hierarchy

Election AlgorithmsCS-4513, D-Term Iterative Resolution of Names

Election AlgorithmsCS-4513, D-Term Iterative Resolution of Names

Election AlgorithmsCS-4513, D-Term DNS Domain Registry Database Text file containing records Each record is {Name, Type, value(s)}

Election AlgorithmsCS-4513, D-Term Example

Election AlgorithmsCS-4513, D-Term DNS Implementation One master copy per domain or subdomain Edited manually by system administrator Multiple slave copies Automatically copied / updated periodically from master Stored in file on slave server, reloaded up restart Caching in DNS clients Lots and lots of caching Entries include TTL (time-to-live) specification

Election AlgorithmsCS-4513, D-Term Implementation in Linux/Unix BIND — Berkeley Internet Name Domain named — the Name Daemon –Implements local DNS service –Multiple databases Primary or secondary Secondary database points back to primary –Pointer to “higher level” service For resolving names not in own database

Election AlgorithmsCS-4513, D-Term Example Want to find My DNS contacts DNS server A Comcast server specified in my DHCP lease Comcast DNS service Almost certainly has root (global) domain in cache Probably has many.edu entries in cache (very large) Possibly has.wpi.edu in cache (many local users) May have.cs.wpi.edu Consults cache or official server for IP address nslookup

Election AlgorithmsCS-4513, D-Term Example (continued) C:\>nslookup cs.wpi.edu Server: cns.chelmsfdrdc2.ma.boston.comcast.net Address: Non-authoritative answer: Name: cs.wpi.edu Address:

Election AlgorithmsCS-4513, D-Term Some Special Cases Google Yahoo MSN Need to distribute names geographically Need to distribute different addresses for same name Special handling of replicated databases More (perhaps) later in term

Election AlgorithmsCS-4513, D-Term Naming Privacy Problem:– corporations need to have own domains Some public hosts – mail server, web server, etc. Does not want to expose names of internal hosts to outside world E.g., proprietary stuff But wants to make them visible internally hotspur.merl.com

Election AlgorithmsCS-4513, D-Term Solution Two name services for same domain name! Internal External External — visible to Internet (DMZ) Database contains only a few names Points to other internet DNS’s for resolution of internet names Internal — seen only by internal hosts Database contains all internal names Points to external version for resolution of internet names

Election AlgorithmsCS-4513, D-Term Result Internal names can be resolved internally, not externally hotspur.merl.com Internal names and IP addresses are invisible on Internet All external names can be resolved internally Two levels of indirection

Election AlgorithmsCS-4513, D-Term Questions? Next Topic