Cluster Playground
A small Hadoop cluster that runs in your browser. Upload files and watch HDFS split and replicate them, break nodes and racks, fail over the NameNode, and run a MapReduce job with and without data locality. Nothing is installed and nothing can break for real.
The full cluster
Three racks of three DataNodes, a client (edge node), two NameNodes (active and standby) and a ResourceManager. Everything you can do in the lessons is switched on here. Use the checklist as a guided tour, or just experiment.
What each part of the picture means
hdfs and hadoop jar commands. Not a DataNode, so the first replica of an upload goes to any node.Defaults follow real Hadoop: 128 MB blocks, replication 3, rack-aware placement, heartbeat every 3 seconds, a DataNode declared dead after 10 minutes 30 seconds. Transfer and task times are simplified, and some things that take minutes in a real cluster (such as noticing a lost task) happen immediately here.
Lessons that use the playground
- 1.1 Server, node, rack and data centre: the pieces of a cluster
- 1.2 What is a cluster? Masters and workers: break a worker during a job
- 1.3 Scale out in practice: 3 vs 6 vs 9 nodes
- 1.4 Failures are normal: how much can you break?
- 1.5 Move the code, not the data: locality on and off
- 2.1 The problem Hadoop solved: store, process, survive
- 2.3 How Hadoop solved each problem: test every fix
- 2.4 Hadoop 1, 2 and 3: NameNode failover
- 3.1 Hadoop architecture: spot the daemons
- 3.2 The life of a file and a job: follow the Event log
- 3.3 Node roles: break each role
- 4.2 Standalone, pseudo and fully distributed: one node, then many
- 4.4 Configuration files and web UIs: block size and replication per file
- 5.1 NameNode and DataNode: metadata here, data there
- 5.2 Blocks: same file, different block sizes
- 5.3 Replication and rack awareness: replicas across racks
- 5.5 Heartbeats and block reports: silence means dead