PowerPoint Presentation
Chapter 17:
Distributed Systems
2
Chapter 17: Distributed Systems
Advantages of Distributed Systems
Types of Network-Based Operating Systems
Network Structure
Communication Structure
Communication Protocols
An Example: TCP/IP
Robustness
Design Issues
Distributed File System
3
Chapter Objectives
To provide a high-level overview of distributed systems and the networks that interconnect them
To discuss the general structure of distributed operating systems
To explain general communication structure and communication protocols
To describe issues concerning the design of distributed systems
4
Distributed System
A collection of loosely coupled processors that do not share memory or a clock
Each node has its own memory. Nodes communicate through networks such as high speed busses and the internet.
A site refers to a location of a machine.
A node refers to a specific system at a site.
Generally, one node at one site, the server, has a resource that another node at another site, the client or user, would like to use.
5
Reasons for Distributed Systems
Resource sharing
Sharing and printing files at remote sites
Processing information in a distributed database
Using remote specialized hardware devices
Computation speedup – load sharing or job migration
Reliability – detect and recover from site failure, function transfer, reintegrate failed site
Communication – message passing
All higher-level functions of a standalone system can be expanded to encompass a distributed system
Computers can be downsized, more flexibility, better user interfaces and easier maintenance by moving from large system to multiple smaller systems performing distributed computing
6
Types of Distributed Operating Systems
Simpler to implement
More difficult for users to access and utilize
Network Operating Systems
Users access remote resources in the same way they access local resources
Distributed Operating Systems
7
Network-Operating Systems
Users are aware of multiplicity of machines
Access to resources of various machines is done explicitly by:
Remote logging into the appropriate remote machine (telnet, ssh)
Remote Desktop (Microsoft Windows)
Transferring data from remote machines to local machines, via the File Transfer Protocol (FTP, SFTP) mechanism
Users must change paradigms – establish a session, give network-based commands, and know the command set of the remote system (windows vs unix)
All general purpose operating systems and Android and iOS are network operating systems.
8
Distributed Operating Systems
Users not aware of multiplicity of machines
Access to remote resources same as access to local resources
Data Migration – transfer data by transferring entire file, or transferring only those portions of the file necessary for the immediate task and automatically writing back any changes made by the remote user
e.g., Andrew, Microsoft SMB, Sun NFS
Computation Migration – when it is more efficient to transfer the computation, rather than the data, across the system and send the results back to the user.
Via remote procedure calls (RPCs) -synchronous
or via messaging system -asynchronous
9
Distributed-Operating Systems (Cont.)
Process Migration – OS determines to execute an entire process, or parts of it, at different sites
Load balancing – distribute processes across network to even the workload
Computation speedup – subprocesses can run concurrently on different sites
Hardware preference – process execution may require specialized processor (e.g., matrix inversion on an array processor)
Software preference – required software may be available at only a particular site
Data access – run process remotely, rather than transfer all data locally
Consider the World Wide Web with servers sending Java scripts and Java applets to run on client computers.
10
Network structure
Local –Area Networks (LAN)
Composed of hosts distributed over a single building or a number of adjacent buildings.
Wide-Area Networks (WAN)
Systems distributed over large areas (e.g. USA)
Differences include:
Major variations in speed
Reliability of the communications network
Impact distributed OS design
5
Network Structure
Local-Area Network (LAN) – designed to cover small geographical area
Multiple topologies like star or ring
Speeds from 1Mb per second (Appletalk, bluetooth) to 40 Gbps for fastest Ethernet over twisted pair copper or optical fibre
12
Local Area network
Consists of multiple computers (mainframes through mobile devices), peripherals (printers, storage arrays), routers (specialized network communication processors) providing access to other networks
Ethernet most common way to construct LANs
Multiaccess bus-based
Defined by standard IEEE 802.3
Wireless spectrum (WiFi) increasingly used for networking
I.e. IEEE 802.11g standard implemented at 54 Mbps. IEEE 802.11n with speeds ~75Mbps.
13
Local-area Network
star configuration
14
Nat
network address translation
Introduced when the explosive popularity of the internet made the 4 billion IPv4 addresses inadequate to service the voracious appetite of users to connect to the Web.
Routers perform this translation.
Need goes away with IPv6 addresses that can have up to 340 undecillion unique addresses.
4:25
Wide-Area Network (WAN)
Links geographically separated sites
(Arpanet was the first one.. In 1968)
Point-to-point connections over long-haul lines (often leased from a phone company)
Implemented via connection processors known as routers
Internet WAN enables hosts world wide to communicate
Hosts differ in all dimensions but WAN allows communications speeds
16
Wide-Area Network (WAN)
T1 link is 1.544 Megabits per second
T3 is 28 x T1s = 45 Mbps
OC-12 is 622 Mbps
WANs and LANs interconnect, similar to cell phone network:
Cell phones use radio waves to cell towers (LAN)
Towers connect to other towers and hubs (WAN)
17
Wan network architecture
18
Communication Structure
Naming and name resolution – How do two processes locate each other to communicate?
Routing strategies – How are messages sent through the network?
Connection strategies – How do two processes send a sequence of messages?
Contention – The network is a shared resource, so how do we resolve conflicting demands for its use?
The design of a communication network must address four basic issues:
19
Naming and Name Resolution
20
Name systems in the network
Address messages with the process-id
Identify processes on remote systems by
Domain name system (DNS) – specifies the naming structure of the hosts, as well as name to address resolution (Internet)
How DNS works
Hosts on the internet are logically addressed with multipart names.
Names progress from specific to general separated by periods e.g. bob.cs.brown.edu
Logical name is converted into Internet host-id in reverse order
Let’s follow the steps take when system A wishes to communicate with bob.cs.brown.edu….
HOW DNS WORKS
System A issues a request to the name server for the edu domain asking for the address of the name server for brown.edu.
The edu name server returns the address of the host on which the brown.edu name server resides.
System A then queries the brown.edu name server asking about cs.brown.edu.
An address is returned.
System A asks for the address of bob.cs.brown.edu and it receives 128.148.31.100 as the internet address (IP address).
6:46
Routing Strategies
Fixed routing – A path from A to B is specified in advance; path changes only if a hardware failure disables it
Since the shortest path is usually chosen, communication costs are minimized
Fixed routing cannot adapt to load changes
Ensures that messages will be delivered in the order in which they were sent
Virtual routing- A path from A to B is fixed for the duration of one session. Different sessions involving messages from A to B may have different paths
Partial remedy to adapting to load changes
Ensures that messages will be delivered in the order in which they were sent
23
Routing Strategies (Cont.)
Dynamic routing – The path used to send a message from site A to site B is chosen only when a message is sent
Usually a site sends a message to another site on the link least used at that particular time
Adapts to load changes by avoiding routing messages on heavily used path
Messages may arrive out of order
This problem can be remedied by appending a sequence number to each message
Most complex to set up
Tradeoffs mean all methods are used
UNIX provides ability to mix fixed and dynamic
Hosts may have fixed routes and gateways connecting networks together may have dynamic routes
24
Routing Strategies (Cont.)
Router is communications processor responsible for routing 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
Static routing – table only changed manually
Dynamic routing – table changed via routing protocol
25
Routing Strategies (Cont.)
More recently, routing managed by intelligent software more intelligently than routing protocols
OpenFlow is device-independent, allowing developers to introduce network efficiencies by decoupling data-routing decisions from underlying network devices
Messages vary in length – simplified design breaks them into packets (or frames, or datagrams)
Connectionless message is just one packet
Otherwise need a connection to get a multi-packet message from source to destination
26
Connection Strategies
Circuit switching – A permanent physical link is established for the duration of the communication (i.e., telephone system)
Requires setup time, but incurs less overhead for shipping each message, and may waste network bandwidth
Message switching – A temporary link is established for the duration of one message transfer (i.e., post-office mailing system)
Packet switching – Messages of variable length are divided into fixed-length packets which are sent to the destination
Each packet may take a different path through the network
The packets must be reassembled into messages as they arrive
Message and packet switching require less setup time, but incur more overhead per message
27
Communication Protocol
Layer 1: Physical layer – handles the mechanical and electrical details of the physical transmission of a bit stream
Layer 2: Data-link layer – handles the frames, or fixed-length parts of packets, including any error detection and recovery that occurred in the physical layer
Layer 3: Network layer – provides connections and routes packets in the communication network, including handling the address of outgoing packets, decoding the address of incoming packets, and maintaining routing information for proper response to changing load levels
The communication network is partitioned into the following multiple layers:
28
Communication Protocol (Cont.)
Layer 4: Transport layer – responsible for low-level network access and for message transfer between clients, including partitioning messages into packets, maintaining packet order, controlling flow, and generating physical addresses
Layer 5: Session layer – implements sessions, or process-to-process communications protocols
Layer 6: Presentation layer – resolves the differences in formats among the various sites in the network, including character conversions, and half duplex/full duplex (echoing)
Layer 7: Application layer – interacts directly with the users, deals with file transfer, remote-login protocols and electronic mail, as well as schemas for distributed databases
29
Communication Via ISO Network Model
30
The ISO Protocol Layer
31
The ISO Network Message
32
The TCP/IP Protocol Layers
33
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
Domain Name Service (DNS) can be used to acquire IP addresses
Address Resolution Protocol (ARP) is used to map MAC addresses to IP addresses
Broadcast to all other systems on the Ethernet network
If the hosts are on the same network, ARP can be used
If the hosts are on different networks, the sending host will send the packet to a router which routes the packet to the destination network
34
An Ethernet Packet
35
Robustness
Failure detection
Reconfiguration
36
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
At fixed intervals, each site will exchange an I-am-up message indicating that they are up and running
If Site A does not receive a message within the fixed interval, it assumes either (a) the other site is not up or (b) the message was lost
Site A can now send an Are-you-up? message to Site B
If Site A does not receive a reply, it can repeat the message or try an alternate route to Site B
37
Failure Detection (Cont.)
If Site A does not ultimately receive a reply from Site B, it concludes some type of failure has occurred
Types of failures:
– 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
38
Reconfiguration
When Site A determines a failure has occurred, it must reconfigure the system:
If the link from A to B has failed, this must be broadcast to every site in the system
If a site has failed, every other site must also be notified indicating that the services offered by the failed site are no longer available
When the link or the site becomes available again, this information must again be broadcast to all other sites
39
Design Issues
Transparency – the distributed system should appear as a conventional, centralized system to the user
Fault tolerance – the distributed system should continue to function in the face of failure
Scalability – as demands increase, the system should easily accept the addition of new resources to accommodate the increased demand
Consider Hadoop open source programming framework for processing large datasets in distributed environments (based on Google search indexing)
Clusters – a collection of semi-autonomous machines that acts as a single system
40
Distributed File System
Distributed file system (DFS) – a distributed implementation of the classical time-sharing model of a file system, where multiple users share files and storage resources
A DFS manages set of dispersed storage devices
Overall storage space managed by a DFS is composed of different, remotely located, smaller storage spaces
There is usually a correspondence between constituent storage spaces and sets of files
Challenges include:
Naming and Transparency
Remote File Access
41
DFS Structure
Service – software entity running on one or more machines and providing a particular type of function to a priori unknown clients
Server – service software running on a single machine
Client – process that can invoke a service using a set of operations that forms its client interface
A client interface for a file service is formed by a set of primitive file operations (create, delete, read, write)
Client interface of a DFS should be transparent, i.e., not distinguish between local and remote files
Sometimes lower level intermachine interface need for cross-machine interaction
42
Naming and Transparency
Naming – mapping between logical and physical objects
Multilevel mapping – abstraction of a file that hides the details of how and where on the disk the file is actually stored
A transparent DFS hides the location where in the network the file is stored
For a file being replicated in several sites, the mapping returns a set of the locations of this file’s replicas; both the existence of multiple copies and their location are hidden
43
Naming Structures
Location transparency – file name does not reveal the file’s physical storage location
Location independence – file name does not need to be changed when the file’s physical storage location changes
44
Naming Schemes — Three Main Approaches
Files named by combination of their host name and local name; guarantees a unique system-wide name
Attach remote directories to local directories, giving the appearance of a coherent directory tree; only previously mounted remote directories can be accessed transparently
Total integration of the component file systems
A single global name structure spans all the files in the system
If a server is unavailable, some arbitrary set of directories on different machines also becomes unavailable
In practice most DFSs use static, location-transparent mapping for user-level names
Some support file migration
Hadoop supports file migration but without following POSIX standards
45
Remote File Access
Remote-service mechanism is one transfer approach
Reduce network traffic by retaining recently accessed disk blocks in a cache, so that repeated accesses to the same information can be handled locally
If needed data not already cached, a copy of data is brought from the server to the user
Accesses are performed on the cached copy
Files identified with one master copy residing at the server machine, but copies of (parts of) the file are scattered in different caches
Cache-consistency problem – keeping the cached copies consistent with the master file
Could be called network virtual memory
46
Cache Location – Disk vs. Main Memory
Advantages of disk caches
More reliable
Cached data kept on disk are still there during recovery and don’t need to be fetched again
Advantages of main-memory caches:
Permit workstations to be diskless
Data can be accessed more quickly
Performance speedup in bigger memories
Server caches (used to speed up disk I/O) are in main memory regardless of where user caches are located; using main-memory caches on the user machine permits a single caching mechanism for servers and users
47
Cache Update Policy
Write-through – write data through to disk as soon as they are placed on any cache
Reliable, but poor performance
Delayed-write (write-back) – modifications written to the cache and then written through to the server later
Write accesses complete quickly; some data may be overwritten before they are written back, and so need never be written at all
Poor reliability; unwritten data will be lost whenever a user machine crashes
Variation – scan cache at regular intervals and flush blocks that have been modified since the last scan
Variation – write-on-close, writes data back to the server when the file is closed
Best for files that are open for long periods and frequently modified
48
Consistency
Is locally cached copy of the data consistent with the master copy?
Client-initiated approach
Client initiates a validity check
Server checks whether the local data are consistent with the master copy
Server-initiated approach
Server records, for each client, the (parts of) files it caches
When server detects a potential inconsistency, it must react
49
Send email to CISC3320.bc@gmail.com
Within the next 90 seconds
End of Chapter 17
51
.MsftOfcThm_Background1_Fill {
fill:#FFFFFF;
}
.MsftOfcThm_Background1_Fill {
fill:#FFFFFF;
}
.MsftOfcThm_Background1_Fill {
fill:#FFFFFF;
}
.MsftOfcThm_Background1_Fill {
fill:#FFFFFF;
}
fg17_02.eps
LAN Switch
Firewall
Router WAN Link
LAN WAN
fg17_03.eps
communication
processor
communication
subsystem
H
H
H
H
H
user processes
user processes
network host
network host
host operating system
host operating system
CP
CP
CPCP
17_06.eps
real systems environment
OSI environment
network environment
data network
computer A
application layer
presentation layer
session layer
transport layer
network layer
link layer
physical layer
AP
computer B
A-L (7)
P-L (6)
S-L (5)
T-L (4)
N-L (3)
L-L (2)
P-L (1)
AP
o.06.eps
data-communication network
end-to-end message transfer
(connection management, error control,
fragmentation, flow control)
physical connection to
network termination equipment
transport layer
network routing, addressing,
call set-up and clearing
transfer-syntax negotiation
data-representation transformations
network-independent
message-interchange service
presentation layer
file transfer, access, and management;
document and message interchange;
job transfer and manipulation
syntax-independent message
interchange service
end-user application process
distributed information
services
application layer
dialog and synchronization
control for application entities
session layer
network layer
link layer
physical layer
data-link control
(framing, data transparency, error control)
mechanical and electrical
network-interface connections
16-08.eps
data-link-layer header
network-layer header
transport-layer header
session-layer header
presentation layer
application layer
message
data-link-layer trailer
17_09.eps
data link
transport
application
HTTP, DNS, Telnet
SMTP, FTP
not defined
not defined
not defined
OSI TCP/IP
not defined
IP
TCP-UDP
physical
network
session
presentation
preamble—start of packet
start of frame delimiter
destination address
source address
length of data section
pad (optional)
frame checksum
bytes
7
1
2 or 6
2 or 6
2
each byte pattern 10101010
pattern 10101011
Ethernet address or broadcast
Ethernet address
length in bytes
message data
message must be > 63 bytes long
for error detection
0–1500
0–46
4
data