HBase architecture (RegionServer, HMaster) in Hadoop - Step-by-Step Execution

Concept Flow - HBase architecture (RegionServer, HMaster)

Client Request

↓

HMaster

↓

RegionServer 1

↓

Regions

↓

Data Storage

Client sends requests to HMaster, which manages RegionServers. RegionServers handle data regions and storage.

Execution Sample

Hadoop

Client -> HMaster -> RegionServer -> Region -> Data Storage

Shows the flow of a client request through HBase architecture components.

Execution Table

Step	Component	Action	Result
1	Client	Sends read/write request	Request received by HMaster
2	HMaster	Locates RegionServer for region	Identifies RegionServer managing target region
3	RegionServer	Processes request on region	Reads/writes data in region
4	Region	Handles data operations	Data updated or retrieved
5	RegionServer	Sends response to client	Client receives requested data or confirmation
6	HMaster	Monitors RegionServers' health	Balances load and manages failures
7	Exit	No more requests	System waits for next client request

💡 Execution stops when client has no more requests to process.

Variable Tracker

Component	Initial State	After Step 2	After Step 4	Final State
Client	Idle	Request sent	Waiting for response	Received response
HMaster	Idle	Located RegionServer	Monitoring RegionServers	Idle
RegionServer	Idle	Received request	Processed data	Sent response
Region	Data stored	Ready	Data updated/retrieved	Ready

Key Moments - 3 Insights

Why does the client send the request to HMaster instead of directly to RegionServer?

Because HMaster knows which RegionServer holds the data region needed, as shown in step 2 of the execution_table.

What happens if a RegionServer fails?

HMaster monitors RegionServers (step 6) and will reassign regions to other RegionServers to keep data available.

Does the RegionServer store all data?

No, each RegionServer manages only some regions (parts) of the data, as shown in the concept_flow.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the RegionServer process the client request?

A Step 3

B Step 2

C Step 5

D Step 6

💡 Hint

Check the 'Component' and 'Action' columns in execution_table row for step 3.

According to variable_tracker, what is the state of the Client after Step 4?

A Idle

B Waiting for response

C Request sent

D Received response

💡 Hint

Look at the Client row under 'After Step 4' in variable_tracker.

If HMaster did not monitor RegionServers, which step in execution_table would be affected?

A Step 2

B Step 4

C Step 6

D Step 5

💡 Hint

Refer to the action described in step 6 of execution_table.

Concept Snapshot

HBase architecture has two main parts:
- HMaster: manages RegionServers, assigns regions, monitors health.
- RegionServer: stores and serves data regions.
Clients send requests to HMaster, which directs them to the right RegionServer.
RegionServers handle data read/write for their regions.
HMaster balances load and handles failures.

Full Transcript

HBase architecture consists of HMaster and RegionServers. Clients send requests to HMaster. HMaster finds which RegionServer holds the needed data region. The RegionServer processes the request by reading or writing data in its region. After processing, the RegionServer sends the response back to the client. HMaster continuously monitors RegionServers to manage load and detect failures. Each RegionServer manages only parts of the data called regions. This setup helps HBase scale and stay reliable.