Why Distributed file systems in HLD? - Purpose & Use Cases

The Big Idea

What if your files could live everywhere at once, safe and ready for everyone to use?

The Scenario

Imagine you have a huge photo album stored on one computer. Now, you want to share it with your friends who live far away, and everyone wants to add their photos too. You try to send files back and forth manually, but it quickly becomes a mess.

The Problem

Manually sharing files means copying and sending them one by one. It is slow, confusing, and easy to lose or overwrite photos. If the computer storing the album breaks, all photos might be lost. Also, many friends cannot work on the album at the same time without causing conflicts.

The Solution

Distributed file systems solve this by spreading the files across many computers that work together. They keep copies safe, let many people add or change files at once, and make sure everyone sees the latest version without confusion.

Before vs After

✗ Before

copy file1 to friendA
copy file2 to friendB
wait for updates
merge changes manually

✓ After

mount distributed_fs
save photo.jpg
all friends access and update instantly

What It Enables

Distributed file systems make it easy and safe for many users to store, share, and update huge amounts of data together, no matter where they are.

Real Life Example

Cloud storage services like Google Drive or Dropbox use distributed file systems so millions of users can save and share files seamlessly across the world.

Key Takeaways

Manual file sharing is slow and risky for big or shared data.

Distributed file systems spread data across many machines for safety and speed.

They allow many users to work together smoothly on the same files.

Practice

1. What is the main role of a metadata server in a distributed file system?

easy

A. To keep track of file locations and directory structure

B. To store the actual file data

C. To provide network connectivity between clients

D. To encrypt files before storage

Solution

1. Step 1: Understand metadata server function

   The metadata server manages information about where files are stored and their organization.

2. Step 2: Differentiate from storage nodes

   Storage nodes hold the actual file data, not metadata servers.

3. Final Answer:

   To keep track of file locations and directory structure -> Option A

4. Quick Check:

   Metadata server = file info tracker [OK]

Hint: Metadata servers track file info, not data storage [OK]

Common Mistakes:

• Confusing metadata server with storage node
• Thinking metadata server stores file data
• Assuming metadata server handles encryption

2. Which of the following is the correct sequence when a client reads a file in a distributed file system?

easy

A. Client contacts only the storage node

B. Client contacts storage node, then metadata server

C. Client contacts only the metadata server

D. Client contacts metadata server, then storage node

Solution

1. Step 1: Identify client interaction flow

   The client first asks the metadata server for file location details.

2. Step 2: Access data from storage node

   After getting location info, the client reads the actual file data from the storage node.

3. Final Answer:

   Client contacts metadata server, then storage node -> Option D

4. Quick Check:

   Read flow = metadata server then storage node [OK]

Hint: Client asks metadata first, then reads data [OK]

Common Mistakes:

• Reversing the order of contacting servers
• Assuming client contacts only one server type
• Ignoring metadata server role in locating files

3. Consider a distributed file system where a file is split into 3 chunks stored on different storage nodes. If the metadata server returns chunk locations as [Node1, Node2, Node3], what happens when the client requests the file?

medium

A. Client reads all chunks sequentially from Node1 only

B. Client reads chunks in parallel from Node1, Node2, and Node3

C. Client reads chunks randomly from any node

D. Client reads only the first chunk from Node1

Solution

1. Step 1: Understand chunk distribution

   The file is divided into chunks stored on separate nodes for parallel access.

2. Step 2: Client reads chunks efficiently

   To speed up reading, the client fetches all chunks at the same time from their respective nodes.

3. Final Answer:

   Client reads chunks in parallel from Node1, Node2, and Node3 -> Option B

4. Quick Check:

   Parallel chunk reads = faster file access [OK]

Hint: Chunks read in parallel from all nodes [OK]

Common Mistakes:

• Assuming client reads all chunks from one node
• Thinking chunks are read randomly
• Ignoring parallelism benefits

4. A distributed file system client tries to read a file but gets an error because the metadata server is unreachable. What is the most likely cause?

medium

A. Client has no network access to metadata server

B. Storage nodes are down

C. File data is corrupted on storage nodes

D. Client requested a non-existent file chunk

Solution

1. Step 1: Identify error source

   The error is due to inability to reach the metadata server, not storage nodes.

2. Step 2: Analyze network access

   Most likely, the client cannot connect to the metadata server because of network issues or firewall rules.

3. Final Answer:

   Client has no network access to metadata server -> Option A

4. Quick Check:

   Metadata server unreachable = network issue [OK]

Hint: Metadata server unreachable means network problem [OK]

Common Mistakes:

• Blaming storage nodes for metadata server errors
• Assuming file corruption causes metadata errors
• Confusing chunk existence with server reachability

5. You are designing a distributed file system for a company with many users reading large files frequently but rarely writing. Which design choice improves read performance the most?

hard

A. Disable caching to ensure fresh data on every read

B. Store all file chunks on a single storage node to simplify access

C. Use multiple metadata servers with caching to reduce lookup latency

D. Limit the number of storage nodes to reduce network overhead

Solution

1. Step 1: Analyze workload pattern

   Many reads and few writes mean caching metadata can speed up file location lookups.

2. Step 2: Evaluate design options

   Multiple metadata servers with caching reduce latency and avoid bottlenecks, improving read speed.

3. Step 3: Reject other options

   Storing all chunks on one node limits scalability; disabling caching slows reads; fewer nodes reduce parallelism.

4. Final Answer:

   Use multiple metadata servers with caching to reduce lookup latency -> Option C

5. Quick Check:

   Metadata caching + multiple servers = faster reads [OK]

Hint: Cache metadata and use multiple servers for fast reads [OK]

Common Mistakes:

• Putting all data on one node limits scalability
• Disabling caching hurts read performance
• Reducing nodes lowers parallel access