UNIT III. cache/replicas maintenance Main memory No No No 1 RAM File system n No Yes No 1 UNIX file system Distributed file

Similar documents

Introduction. Distributed file system. File system modules. UNIX file system operations. File attribute record structure

Lecture 7: Distributed File Systems

Chapter 12 Distributed File Systems. Copyright 2015 Prof. Amr El-Kadi

DFS Case Studies, Part 1

Distributed File Systems. CS432: Distributed Systems Spring 2017

A DNS Tutorial

Introduction. Chapter 8: Distributed File Systems

CS454/654 Midterm Exam Fall 2004

DISTRIBUTED SYSTEMS [COMP9243] Lecture 9a: Naming WHAT IS NAMING? Name: Entity: Slide 3. Slide 1. Address: Identifier:

Chapter 8: Distributed File Systems. Introduction File Service Architecture Sun Network File System The Andrew File System Recent advances Summary

CS6601 DISTRIBUTED SYSTEM / 2 MARK

04 Identifiers. UUID URI Format Characteristics. Coulouris, Ch 9 rfc3986 Ahmed, 2005 Subharthi, 2009

Distributed File Systems

Networking Applications

04 Identifiers UUID. Coulouris, Ch 9 URI. rfc3986 Format. Ahmed, 2005 Characteristics. Subharthi, 2009

Naming. To do. q What s in a name q Flat naming q Structured naming q Attribute-based naming q Next: Content distribution networks

EECS 122: Introduction to Computer Networks DNS and WWW. Internet Names & Addresses

Client Server Concepts, DNS, DHCP

Development of the Domain Name System

Chapter 8 Distributed File Systems

DISTRIBUTED FILE SYSTEMS & NFS

Assignment 5. Georgia Koloniari

Systèmes Distribués. Master MIAGE 1. Andrea G. B. Tettamanzi. Université de Nice Sophia Antipolis Département Informatique

DNS Basics BUPT/QMUL

DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S. TANENBAUM MAARTEN VAN STEEN. Chapter 5 Naming

2. Introduction to Internet Applications

Chapter 19. Domain Name System (DNS)

PART B UNIT II COMMUNICATION IN DISTRIBUTED SYSTEM PART A

9.1 Introduction 9.2 Name services and the DNS 9.3 Discovery services 9.6 Summary

Application Layer Protocols

Distributed File Systems. File Systems

Outline Applications. Central Server Hierarchical Peer-to-peer. 31-Jan-02 Ubiquitous Computing 1


Protocol Classification

The Domain Name System

Naming. Naming. Naming versus Locating Entities. Flat Name-to-Address in a LAN

! Design constraints. " Component failures are the norm. " Files are huge by traditional standards. ! POSIX-like

Module 7 File Systems & Replication CS755! 7-1!

Distributed File Systems

Parallelism. Master 1 International. Andrea G. B. Tettamanzi. Université de Nice Sophia Antipolis Département Informatique

More Internet Support Protocols

ECE 650 Systems Programming & Engineering. Spring 2018

DNS. DNS is an example of a large scale client-server application.

Distributed System: Definition

Higher layer protocols

DNS and HTTP. A High-Level Overview of how the Internet works

DNS Concepts. Acknowledgements July 2005, Thimphu, Bhutan. In conjunction with SANOG VI. Bill Manning Ed Lewis Joe Abley Olaf M.

The Google File System (GFS)

Background. 20: Distributed File Systems. DFS Structure. Naming and Transparency. Naming Structures. Naming Schemes Three Main Approaches

Lecture 4 Naming. Prof. Wilson Rivera. University of Puerto Rico at Mayaguez Electrical and Computer Engineering Department

CS 403/534 Distributed Systems Midterm April 29, 2004

Announcements. me your survey: See the Announcements page. Today. Reading. Take a break around 10:15am. Ack: Some figures are from Coulouris

The Google File System

Windows Server 2003 Network Administration Goals

Chapter 18 Distributed Systems and Web Services

Today: Coda, xfs! Brief overview of other file systems. Distributed File System Requirements!

CSE 5306 Distributed Systems

Distributed Systems Question Bank UNIT 1 Chapter 1 1. Define distributed systems. What are the significant issues of the distributed systems?

Send me up to 5 good questions in your opinion, I ll use top ones Via direct message at slack. Can be a group effort. Try to add some explanation.

Database Management Systems

Name Services and DNS

Mobile and Heterogeneous databases Distributed Database System Transaction Management. A.R. Hurson Computer Science Missouri Science & Technology

The Design and Implementation of a Next Generation Name Service for the Internet (CoDoNS) Presented By: Kamalakar Kambhatla

Venugopal Ramasubramanian Emin Gün Sirer SIGCOMM 04

Ch. 7 Distributed File Systems

DNS is the mechanism by which Internet software translates names to attributes such as addresses.

Distributed File Systems. CS 537 Lecture 15. Distributed File Systems. Transfer Model. Naming transparency 3/27/09

DOMAIN NAME SYSTEM (DNS) BEYAZIT BESTAMİ YÜKSEL

Distributed Systems Final Exam

Electrical Engineering Department EE 400, Experiment # 4 IP Addressing and Subnetting

Types of Transfer. Connection-oriented Transfer. Connectionless Transfer. Networks generally provide two types of communication. Connection-oriented

Using peer to peer. Marco Danelutto Dept. Computer Science University of Pisa

CptS 464/564 Lecture 18

殷亚凤. Naming. Distributed Systems [5]

IP Addresses. An IPv4 address looks like this

Manual Configuration Stateful Address Configuration (i.e. from servers) Stateless Autoconfiguration : IPv6

CS555: Distributed Systems [Fall 2017] Dept. Of Computer Science, Colorado State University

GFS: The Google File System

Distributed systems. Lecture 6: distributed transactions, elections, consensus and replication. Malte Schwarzkopf

Distributed Systems. Hajussüsteemid MTAT Distributed File Systems. (slides: adopted from Meelis Roos DS12 course) 1/25

The Google File System

The Google File System

A Self-Configuring and Self-Administering Name System

DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S. TANENBAUM MAARTEN VAN STEEN. Chapter 1. Introduction

Layering and Addressing CS551. Bill Cheng. Layer Encapsulation. OSI Model: 7 Protocol Layers.

CS435 Introduction to Big Data FALL 2018 Colorado State University. 11/7/2018 Week 12-B Sangmi Lee Pallickara. FAQs

Chapter 11: Implementing File-Systems

Last Class: RPCs and RMI. Today: Communication Issues

PEER TO PEER SERVICES AND FILE SYSTEM

Today CSCI Coda. Naming: Volumes. Coda GFS PAST. Instructor: Abhishek Chandra. Main Goals: Volume is a subtree in the naming space

CCNA Exploration Network Fundamentals. Chapter 03 Application Functionality and Protocols

ITTC Science of Communication Networks The University of Kansas EECS 784 Identifiers, Names, and Addressing

Naming in Distributed Systems

ip dhcp-client network-discovery through ip nat sip-sbc

Chapter 18 Parallel Processing

Distributed Systems 16. Distributed File Systems II

Chapter 17: Distributed-File Systems. Operating System Concepts 8 th Edition,

File Management. Chapter 12

The Google File System

Transcription:

UNIT III 1. Enumerate the properties of storage system? Sharing Persistent Distributed Consistency Example cache/replicas maintenance Main memory No No No 1 RAM File system n No Yes No 1 UNIX file system Distributed file Yes Yes Yes Yes Sun NFS system web Yes Yes Yes No Web server Distributed shared Yes No Yes Yes Ivy(DSM) memory Remote Yes No No 1 CORBA objects(rmi/orb) Persistent object Yes Yes No 1 CORBA store persistent state service Peer to peer storage Yes Yes Yes 2 Ocean Store system 2. List out file system modules. Directory module: Relates file names to file IDs File module: Relates file IDs to particular files Access control module: Checks permission for operation requested File access module: Read or writes file data or attributes Block module: Accesses and allocates disk blocks Device module: Disk I/O and buffering 3. Sketch the file attributes and record structure. File Length Creation Time stamp Read Timestamp Write time stamp Attribute time stamp Reference count Owner File Type Access control List CS6601-DISTRIBUTED SYSTEMS Page 1

4.List out the UNIX file system Operations: fieldes=open(name,mode) fieldes=create(name,mode) status=close(fieldes) count=read(fieldes,buffer,n) count=write(fieldes,buufer,n) pos=iseek(filedes,offset,whence) status=unlink(nmae) status=link(name1,nmae2) status=stat(name,buffer) 5. List out the transparencies in file system. i. Access transparency ii. Location transparency iii. Mobility transparency iv. Performance transparency v. Scaling transparency 6. What is meant by concurrency control? Changes to a file by one client should not interfere with the operation of other clients simultaneously accessing or changing the same file. This is well-known issue of concurrency control.the need for concurrency control for accss to shared data in many applications Is widely accepted and techniques are known for its implementation,but they are costly.most current file services follow morden UNIX standards in providing advisery or mandatoryfile or record-level locking. 7. What is file replication? In a file service that supports replication, a file may be represented by several copies of its contents at different locations. This has two benefits-its enables multiple servers to share the load of providing a service to clients accessing the same set of files, enhancing the scalability of the service, and it enhances fault tolerance by enabling clients to locate another server that holds a CS6601-DISTRIBUTED SYSTEMS Page 2

copy of the file when one has failed. Few file services support replication fully, but most support the catching of files or portions of files locally, a limited form of replication. 8. What is meant by directory services? The directory services provide a mapping between text names for files and their UFIDs. Client may obtain the UFIDs of a file by quoting its text name to the directory services. The directory services provides the function needed to generate directories, to add new file name to directories and to obtain UFIDs from directories. It is client of the flat file services; its directory is stored in files of the flat services. When a hierarchic file-naming scheme is adopted as in UNIX, directories hold references to other directories. 9.Sketch the file service architecture? 10. List the flat file service operation. Read (file/d,i,n)>data-throws bad position - if 1 1 length(file):reads a sequence of up to N items From a file starting at item/and returns it in data Write(File/D,I,Ddata)-throws bad position - if 1 1 length(file)+1: writes a sequence of data to a File, starting at item 1,extending the file if necessary Create()->FileID -creates a new file of length 0 and delivers a UFID for it CS6601-DISTRIBUTED SYSTEMS Page 3

Delete(FileID) GetAttributes(FileID)->> SetAttributes(FileID) -removes the file from the file store -returns the file attributes for the file -sets the file attributes(only those attributes that not Shaded in) 11.List the directory service operation. Lookup(Dir,Name) FileID throws not found AddName(Dir,Name,File) UnName (Dir,Name) throws not found GetName(Dir,Pattern) Names Locate the text name in the directory and returns the relevant UFID.If name is not in the directory, throws an exception If the nameis not in the directory, adds(nmae,file) to the directory and updates the file s Attribute record.if name is already in the Directory;throws an exception. If name is in the directory: The entry containing name is removed from the directory. If name is not in the directory;throws an exception. Returns all the text names in the directory that match the regular expression pattern. 12. Sketch NFS architecture. CS6601-DISTRIBUTED SYSTEMS Page 4

13. List the NFS file server operation. Lookup(DirFH,Name) FH,Attr Create(DirFH,Name,Attr) NewFH,Attr Remove(DirFH,Name) Status GetAttr(FH) Attr Returns File handles and attributes for the File Name in the directory DirFH. Creates a new file in directory DirFH with Attributes Attr and Returns the new File handle and Attributes. Removes file name from directory DirFH. Returns the file attributes of file FH.(similar to UNIX stat system call) Read(FH,Offset,count) Attr,Dir Write(FH,Offset,count,Data) Attr Returns up to count bytes of data from the file starting at the offset,also return the attributes of the file. Writes count bytes of to a file starting at offset. Returns the attributes of the file after write has taken place. 14. what are the timestamps in called caching? i. Tc is the time when the cache entry was last validated. ii. Tm is the when the block was last modified at the server. iii. A cache entry is valid at time T if T-Tc is less than a freshness interval t,or if the value for Tm recorded t the client matches the value of Tm at the server (that is,the data has not been modified at the server since the cache entry was made). 15.what is condition used to validate caching? (T-Tc<t) v (Tm client=tm server) 16.write the measures to be considered to reduce traffic in getattr. Whenever a new value of Tmserver is received at a client, it is applied to all cache entries derived from the relevant file. The current attribute values are sent piggybacked with the result of every operation on a file, and if the value of Tmserver has changed the client uses it to update the cache entries relating to the file. CS6601-DISTRIBUTED SYSTEMS Page 5

The adaptive algorithm for setting freshness interval t outlined above reduces the traffic considerably for most files. 17. When the name is resolved? The name is resolved when it is translated into data about the named resource or object, often in order to invoke an action upon it. The association between a name and an object is called a binding. In general, names are bound to attributes of the named objects, rather than the implementation of the objects themselves. An attribute is the value of a property associated with an object. 18. What is meant by URI? URI-Uniform Resource Identifiers came about from the need to identify resources on the web, and other internet resources such as electronic mailboxes. An important goal was to identify resources in a coherent way, so that they could all be processed by common software such as browser. URIs is uniform in that their syntax incorporates that of indefinitely many individual types of resource identifier(i.e URI schemas),and there are procedures for managing the global namespace of schemas. The advantage of uniformity is that eases the process of introducing new types of identifier, as well as using existing types of identifier in new contexts without disrupting existing usage. 19. What is mean by URN? Uniform Resource Names are URIs that are used as pure resource names rather than locators. For example, the URI: Mid:0E4FC272-5C02-11D9-B115-000A95B55BC8@hpl.hp.com Is a URN that identifies the email message containing it in its message-id field. The URI distinguishes that message from any other email message. But it does not provide the message s address in any store, so a lookup operation is needed to find it. 20.What is global name services? The Global name Service developed at the Digital Equipment corporation systems, Research Center,is a descentdant of Grapevine with ambitious goals, including: com- Commercial organization. edu- universities and other educational institutions. gov- US governmental agencies mil- US military organization net- major network support centers org- organizations not mentioned above CS6601-DISTRIBUTED SYSTEMS Page 6

int International oragnisations. 21. What is meant by navigation? The process of locating naming data from than more than one name server in order to resolve a name is called navigation. The client name resolution software carries out navigation on behalf of the client. It communicates with name servers as necessary to resolve a name. 22. What is multicast navigation? In multicast navigation, a client multicast the name to be resolved and required object type to the group of name servers. Only the server that holds the named attributes responds to the request. Unfortunately, however, if the name proves to be unbound, the request is greeted with silence. 23. What is iterative navigation? One navigation model that DNS supports is known as iterative navigation. To resolve a name, a client present the name to the local name server, which attempts to resolve it. If the local name server has the name, it returns the result immediately. If it does not it will suggest another server that will ba able to help. Resolution proceeds at the new server, with further navigation as necessary until the name is located or is discovered to be unbounded. 24. What is meant by recursive and non recursive navigation? In the non recursive and non recursive server controlled navigation. Under non recursive server controlled navigation,any name server may be chosen by the client. This server communicates by multicast or iteratively with its peer in the style described above, as through it were a client. Under recursive server-controlled navigation,the client once more contacts a single server. If this server doesnot store the name,the server contains a peer to storing a prefix of the CS6601-DISTRIBUTED SYSTEMS Page 7

name,which in turn attempts to resolve it. This procedure continues recursively until the name resolved. 25. Write the disadvantage of existing name service? This original scheme was soon seen to suffer from three major shortcomings: It did not scale to large numbers of computers. Local organization wished to administer their own naming system. A general name service was needed- not one that serves only for looking up computers address. 26. What is meant by DNS? The domain name system is a name service design whose main naming database is used across the internet. It was devised principally by mockapetris and specified in RFC 1034 and RFC 1035. DNS replaced the original internet naming scheme in which all host names and address were held in a single central master file and downloaded by FTP to all computer that required them. Domain Names: The DNS is designed for use in multiple implementations, each of which may have its own name space. In practice, however, only one is in widespread use, and that is one used for naming across the internet. The internet DNS name space is partitioned both organizationally and according to geography. The names are written with the highest-level domain on the right. The original top-level organizational domains in use across the internet were: CS6601-DISTRIBUTED SYSTEMS Page 8

27. What is meant by zone? The DNS naming data are divided into zones. A zone contains the following data: Attributes data for names in a domain, less any subdomains administrates by lower level authorities. The names and address of at least two name servers that provide authoritative data for the zone. These are versions of zone data that can be relied upon as being reasonably up to date. The names of name servers that hold authoritative data for delegated sub domains; and glue data giving the IP address of these servers. Zone-management parameters, such as those governing the catching and replication of zone data. 28. What is lookup operation? 29. List out options of NFS write operation? Data in write operation received from client is stored in the memory cache at the server and written to disk before a reply is sent to the client. This is called writethrough caching. The client can be sure that is data stored persistently as soon as reply has been received. Data in write operation is stored only in the memory cache. It will be written to disk when a commit operation is received for the relevant file. The client can be sure that the data is persistent stored only when a reply to a commit operation for the relevant file has been received. Standard NFS clients use this mode of operation, issuing a commit whenever a file that was open for writing is closed. 30. What is BIND implementation of DNS? The Berkeley internet name domain is an implementation of the DNS for computers running UNIX. Client programs link in library software as the resolver. DNS name server computers run the named deamon. BIND allows for three categories of name server: primary server, secondary yserver, caching only servers. The named program implements just one of these types, according to the content of a configuration file. Caching only servers read in form a configuration file sufficient names and address of authoritative servers to resolve any name. Thereafter, they only store this data and data they learn by resolving names for clients. 31. Write the motivation openness? Name management is separated from other service largely because of the openness of distributed system, which brings the following motivation: Unification CS6601-DISTRIBUTED SYSTEMS Page 9

Integration 32. Define name space. A namespace is the collection of all valid names recognized by a particular service. The service will attempt to look up a valid name, even though that name may prove not to correspond to any object. Name space requires a syntactic definition to separate. PART B 1. Discuss in details file service architecture An architecture that offers a clear separation of the main concerns in providing access to files is obtained by structuring the file service as three components a flat file service, a directory service and a client module. The division of responsibilities between the modules can be defined as follows: Flat file service: The flat file service is concerned with implementing operations on the contents of files. Directory service: The directory service provides a mapping between text names for files and their UFIDs. Client module: A client module runs in each client computer, integrating and extending the operations of the flat file service and the directory service under a single application programming interface that is available to user-level programs in client computers. 2. Explain in detail about napster and its legacy The first application in which a demand for a globally scalable information storage and retrieval service emerged was the downloading of digital music files. Napster s architecture included centralized indexes, but users supplied the files, which were stored and accessed on their personal computers. Limitations: Napster used a (replicated) unified index of all available music files. For the application in question, the requirement for consistency between the replicas was not strong, so this did not hamper performance, but for many applications it would constitute a limitation. Unless the access path to the data objects is distributed, object discovery and addressing are likely to become a bottleneck CS6601-DISTRIBUTED SYSTEMS Page 10

Application dependencies Music files are never updated, avoiding any need to make sure all the replicas of files remain consistent after updates. No guarantees are required concerning the availability of individual files if a music file is temporarily unavailable, it can be downloaded later. This reduces the requirement for dependability of individual computers and their connections to the Internet. 3. Explain the name caches in details Characteristics: High degree of locality of name lookup Slow update of name information database On-use consistency of cached information Types of name Caches Directory cache Prefix cache Full name cache Name cache implementation A cache per process A single cache for all process of a node. Multicache consistency Immediate Invalidate On-Use Update 4. Illustrate routing overlays The routing overlay ensures that any node can access any object by routing each request through a sequence of nodes, exploiting knowledge at each of them to locate the destination object. Peer-to-peer systems usually store multiple replicas of objects to ensure availability. The main task of a routing overlay is the following: Routing of requests to objects Insertion of objects Deletion of objects Node addition and removal CS6601-DISTRIBUTED SYSTEMS Page 11

5. Describe LDAP LDAP stands for Lightweight Directory Access Protocol Access Protocol. LDAP defines a standard method for accessing and updating information in a directory. LDAP uses: Centrally manage users, groups and other data Don t have to manage separate directories for each application Allows users to find data that they need. Not locked into a particular server. LDAP is well suited for Information that is referenced by many entities and applications Information that needs to be accessed from more than one location Information that is read more often than it is written LDAP is not well suited for Information that changes often. Information that is unstructured. CS6601-DISTRIBUTED SYSTEMS Page 12