Professional Documents
Culture Documents
Distributed Systems
17.2
Chapter Objectives
To provide a high-level overview of distributed systems and
systems
To explain general communication structure and
communication protocols
To describe issues concerning the design of distributed
systems
17.3
Overview
Distributed system is collection of loosely coupled processors
site A
server
network
resources
communication
client
site B
17.4
Resource sharing
4 Sharing
4 Processing
4 Using
17.5
17.6
Network-Operating Systems
Users are aware of multiplicity of machines
Access to resources of various machines is done explicitly
by:
network-based commands
17.7
Distributed-Operating Systems
Users not aware of multiplicity of machines
17.8
different sites
17.9
Network Structure
Local-Area Network (LAN) designed to cover small geographical
area
bus-based
17.10
Local-area Network
Router
LAN Switch
WAN Link
Firewall
LAN
17.11
WAN
Speeds
4 T1
4 T3
is 28 x T1s = 45 Mbps
4 OC-12
is 622 Mbps
4 Towers
17.12
user processes
communication
subsystem
CP
H
CP
CP
CP
network host
user processes
H
communication
processor
17.13
Communication Structure
The design of a communication network must address four basic
issues:
Naming and name resolution - How do two processes
network?
Connection strategies - How do two processes send a
sequence of messages?
Contention - The network is a shared resource, so how do
17.14
17.15
Routing Strategies
Fixed routing - A path from A to B is specified in advance; path
17.16
17.17
messages
Must have at least 2 network connections
Maybe special purpose or just function running on host
Checks its tables to determine where destination host is, where
to send messages
17.18
17.19
Connection Strategies
Circuit switching - A permanent physical link is established for
17.20
Communication Protocol
The communication network is partitioned into the following multiple
layers:
Layer 1: Physical layer handles the mechanical and
17.21
17.22
computer B
AP
AP
application layer
presentation layer
session layer
transport layer
network layer
link layer
physical layer
A-L (7)
P-L (6)
S-L (5)
T-L (4)
N-L (3)
L-L (2)
P-L (1)
data network
network environment
OSI environment
real systems environment
17.23
application layer
syntax-independent message
interchange service
transfer-syntax negotiation
data-representation transformations
dialog and synchronization
control for application entities
presentation layer
session layer
network-independent
message-interchange service
end-to-end message transfer
(connection management, error control,
fragmentation, flow control)
transport layer
network layer
data-link control
link layer
(framing, data transparency, error control)
mechanical and electrical
network-interface connections
physical layer
physical connection to
network termination equipment
data-communication network
17.24
message
data-link-layer trailer
17.25
TCP/IP
HTTP, DNS, Telnet
SMTP, FTP
application
presentation
not defined
session
not defined
transport
TCP-UDP
network
IP
data link
not defined
physical
not defined
17.26
Example: TCP/IP
The transmission of a network packet between hosts on an
Ethernet network
Every host has a unique IP address and a corresponding
Ethernet Media Access Control (MAC) address
Communication requires both addresses
addresses to IP addresses
17.27
An Ethernet Packet
bytes
7
preamblestart of packet
2 or 6
destination address
2 or 6
source address
01500
046
4
length in bytes
data
message data
pad (optional)
frame checksum
17.28
Robustness
Failure detection
Reconfiguration
17.29
Failure Detection
Detecting hardware failure is difficult
To detect a link failure, a heartbeat protocol can be used
Assume Site A and Site B have established a link
17.30
- Site B is down
- The direct link between A and B is down
- The alternate link from A to B is down
- The message has been lost
However, Site A cannot determine exactly why the failure
has occurred
17.31
Reconfiguration
When Site A determines a failure has occurred, it must
2.
17.32
Design Issues
Transparency the distributed system should appear as a
17.33
17.34
DFS Structure
Service software entity running on one or more machines
cross-machine interaction
17.35
17.36
Naming Structures
Location transparency file name does not reveal the
17.37
A single global name structure spans all the files in the system
user-level names
17.38
17.39
More reliable
17.40
Variation scan cache at regular intervals and flush blocks that have
been modified since the last scan
Best for files that are open for long periods and frequently
modified
17.41
Consistency
Is locally cached copy of the data consistent with the master
copy?
Client-initiated approach
Server-initiated approach
17.42
End of Chapter 17