Hadoop: Lessons Learned
summary
A practical rundown of running Hadoop in production: a 20-node grep vs MapReduce test (1.5 GB per node) shows MapReduce overhead often outweighs benefit; an ETL on Amazon Elastic MapReduce cuts a migration from two weeks to two days; choose snappy compression for CPU/IO balance; prefer many reducers, use combiners and partitioners to cut IO, watch small-file pressure on the NameNode and append/record-reader quirks, and serialize with proto buffers for faster parsing — use Hadoop only if you must.
AI-written summary · about
chapters (29)
- 0:00Intro
- 1:20Why Hadoop
- 4:57HDFS
- 7:13Benchmarks
- 14:35Integration
- 22:15MapReduce
- 25:00Output
- 27:35Pipeline
- 28:50Append
- 29:25Serialization
- 30:30Map Writable
- 32:00GetBytes
- 32:50Iterator
- 33:45Leucine
- 34:25Data Structures
- 35:15Use many reducers
- 36:30Operations
- 37:00Hardware configuration
- 37:15Monitoring
- 38:27snappy
- 39:10Hadoop expired
- 40:25One major bug
- 41:15Record weirdness
- 42:30Replication factor
- 42:50Community
- 43:20Enterprise effect
- 44:40Incremental realtime
- 44:50Other projects
- 46:15Takeaway
related talks
10mSeparating Hadoop Myths from Reality
29mBig Data Analysis
08mHadoop and Big Data Hype
34mAvoiding Big Data Antipatterns
10mMapReduce in 10 Minutes
45mHadoop in the Cloud: The Story of Migrating Hundreds of Petabytes
47mSolving Real & Big (Data) Problems Using Hadoop
56mResistance is Futile: What You Need to Know about Big Data
