Large-Scale Data Processing With Hadoop and PHP (PHPBNL2012 2012-01-27)

Presentation given at the PHP Benelux 2012 conference on January 27, 2012 in Antwerp, Belgium.

Transcript

1. LARGE-SCALE DATA PROCESSING WITH HADOOP AND PHP
2. David Zuelke
3. David Zülke
5. http://en.wikipedia.org/wiki/File:München_Panorama.JPG
6. Founder
8. Lead Developer
10. @dzuelke
11. THE BIG DATA CHALLENGE Distributed And Parallel Computing
12. we want to process data
13. how much data exactly?
14. SOME NUMBERS • Facebook • New data per day: • 200 GB (March 2008) • 2 TB (April 2009) • 4 TB (October 2009) • 12 TB (March 2010) • Google • Data processed per month: 400 PB (in 2007!) • Average job size: 180 GB
15. what if you have that much data?
16. what if you have just 1% of that amount?
17. “No Problemo”, you say?
18. reading 180 GB sequentially off a disk will take ~45 minutes
19. and you only have 16 to 64 GB of RAM per computer
20. so you can't process everything at once
21. general rule of modern computers:
22. data can be processed much faster than it can be read
23. solution: parallelize your I/O
24. but now you need to coordinate what you’re doing
25. and that’s hard
26. what if a node dies?
27. is data lost? will other nodes in the grid have to re-start? how do you coordinate this?
28. ENTER: OUR HERO Introducing MapReduce
29. in the olden days, the workload was distributed across a grid
30. and the data was shipped around between nodes
31. or even stored centrally on something like an SAN
32. which was fine for small amounts of information
33. but today, on the web, we have big data
34. I/O bottleneck
35. along came a Google publication in 2004
36. MapReduce: Simplified Data Processing on Large Clusters http://labs.google.com/papers/mapreduce.html
37. now the data is distributed
38. computing happens on the nodes where the data already is
39. processes are isolated and don’t communicate (share-nothing)
40. BASIC PRINCIPLE: MAPPER • A Mapper reads records and emits <key, value> pairs • Example: Apache access.log • Each line is a record • Extract client IP address and number of bytes transferred • Emit IP address as key, number of bytes as value • For hourly rotating logs, the job can be split across 24 nodes* * In pratice, it’s a lot smarter than that
41. BASIC PRINCIPLE: REDUCER • A Reducer is given a key and all values for this specific key • Even if there are many Mappers on many computers; the results are aggregated before they are handed to Reducers • Example: Apache access.log • The Reducer is called once for each client IP (that’s our key), with a list of values (transferred bytes) • We simply sum up the bytes to get the total traffic per IP!
42. EXAMPLE OF MAPPED INPUT IP Bytes 212.122.174.13 18271 212.122.174.13 191726 212.122.174.13 198 74.119.8.111 91272 74.119.8.111 8371 212.122.174.13 43
43. REDUCER WILL RECEIVE THIS IP Bytes 212.122.174.13 18271 212.122.174.13 191726 212.122.174.13 198 212.122.174.13 43 74.119.8.111 91272 74.119.8.111 8371
44. AFTER REDUCTION IP Bytes 212.122.174.13 210238 74.119.8.111 99643
45. PSEUDOCODE function  map($line_number,  $line_text)  {    $parts  =  parse_apache_log($line_text);    emit($parts['ip'],  $parts['bytes']); } function  reduce($key,  $values)  {    $bytes  =  array_sum($values);    emit($key,  $bytes); } 212.122.174.13  210238 74.119.8.111      99643 212.122.174.13  -­‐  -­‐  [30/Oct/2009:18:14:32  +0100]  "GET  /foo  HTTP/1.1"  200  18271 212.122.174.13  -­‐  -­‐  [30/Oct/2009:18:14:32  +0100]  "GET  /bar  HTTP/1.1"  200  191726 212.122.174.13  -­‐  -­‐  [30/Oct/2009:18:14:32  +0100]  "GET  /baz  HTTP/1.1"  200  198 74.119.8.111      -­‐  -­‐  [30/Oct/2009:18:14:32  +0100]  "GET  /egg  HTTP/1.1"  200  43 74.119.8.111      -­‐  -­‐  [30/Oct/2009:18:14:32  +0100]  "GET  /moo  HTTP/1.1"  200  91272 212.122.174.13  -­‐  -­‐  [30/Oct/2009:18:14:32  +0100]  "GET  /yay  HTTP/1.1"  200  8371
46. A YELLOW ELEPHANT Introducing Apache Hadoop
48. The name my kid gave a stuffed yellow elephant. Short, relatively easy to spell and pronounce, meaningless and not used elsewhere: those are my naming criteria. Kids are good at generating such. Googol is a kid’s term. Doug Cutting
49. Hadoop is a MapReduce framework
50. it allows us to focus on writing Mappers, Reducers etc.
51. and it works extremely well
52. how well exactly?
53. HADOOP AT FACEBOOK (I) • Predominantly used in combination with Hive (~95%) • 8400 cores with ~12.5 PB of total storage • 8 cores, 12 TB storage and 32 GB RAM per node • 1x Gigabit Ethernet for each server in a rack • 4x Gigabit Ethernet from rack switch to core http://www.slideshare.net/royans/facebooks-petabyte-scale-data-warehouse-using-hive-and-hadoop Hadoop is aware of racks and locality of nodes
54. HADOOP AT FACEBOOK (II) • Daily stats: • 25 TB logged by Scribe • 135 TB of compressed data scanned • 7500+ Hive jobs • ~80k compute hours • New data per day: • I/08: 200 GB • II/09: 2 TB (compressed) • III/09: 4 TB (compressed) • I/10: 12 TB (compressed) http://www.slideshare.net/royans/facebooks-petabyte-scale-data-warehouse-using-hive-and-hadoop
55. HADOOP AT YAHOO! • Over 25,000 computers with over 100,000 CPUs • Biggest Cluster: • 4000 Nodes • 2x4 CPU cores each • 16 GB RAM each • Over 40% of jobs run using Pig http://wiki.apache.org/hadoop/PoweredBy
56. OTHER NOTABLE USERS • Twitter (storage, logging, analysis. Heavy users of Pig) • Rackspace (log analysis; data pumped into Lucene/Solr) • LinkedIn (friend suggestions) • Last.fm (charts, log analysis, A/B testing) • The New York Times (converted 4 TB of scans using EC2)
57. JOB PROCESSING How Hadoop Works
58. Just like I already described! It’s MapReduce! \o/
59. BASIC RULES • Uses Input Formats to split up your data into single records • You can optimize using combiners to reduce locally on a node • Only possible in some cases, e.g. for max(), but not avg() • You can control partitioning of map output yourself • Rarely useful, the default partitioner (key hash) is enough • And a million other things that really don’t matter right now ;)
60. HDFS Hadoop Distributed File System
61. HDFS • Stores data in blocks (default block size: 64 MB) • Designed for very large data sets • Designed for streaming rather than random reads • Write-once, read-many (although appending is possible) • Capable of compression and other cool things
62. HDFS CONCEPTS • Large blocks minimize amount of seeks, maximize throughput • Blocks are stored redundantly (3 replicas as default) • Aware of infrastructure characteristics (nodes, racks, ...) • Datanodes hold blocks • Namenode holds the metadata Critical component for an HDFS cluster (HA, SPOF)
63. there’s just one little problem
64. you need to write Java code
65. however, there is hope...
66. STREAMING Hadoop Won’t Force Us To Use Java
67. Hadoop Streaming can use any script as Mapper or Reducer
68. many configuration options (parsers, formats, combining, …)
69. it works using STDIN and STDOUT
70. Mappers are streamed the records (usually by line: <line>\n) and emit key/value pairs: <key>\t<value>\n
71. Reducers are streamed key/value pairs: <keyA>\t<value1>\n <keyA>\t<value2>\n <keyA>\t<value3>\n <keyB>\t<value4>\n
72. Caution: no separate Reducer processes per key (but keys are sorted)
73. STREAMING WITH PHP Introducing HadooPHP
74. HADOOPHP • A little framework to help with writing mapred jobs in PHP • Takes care of input splitting, can do basic decoding et cetera • Automatically detects and handles Hadoop settings such as key length or field separators • Packages jobs as one .phar archive to ease deployment • Also creates a ready-to-rock shell script to invoke the job
75. written by
77. http://github.com/dzuelke/hadoophp
78. DEMO Hadoop Streaming & PHP in Action
79. !e End
80. RESOURCES • http://www.cloudera.com/developers/learn-hadoop/ • Tom White: Hadoop. The Definitive Guide. O’Reilly, 2009 • http://www.cloudera.com/hadoop/ • Cloudera Distribution for Hadoop is easy to install and has all the stuff included: Hadoop, Hive, Flume, Sqoop, Oozie, …
81. Questions?
82. THANK YOU! This was http://joind.in/4752 by @dzuelke. Contact me or hire us: david.zuelke@bitextender.com