Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
courses:mapreduce-tutorial:step-8 [2012/01/25 15:54] straka |
courses:mapreduce-tutorial:step-8 [2012/01/29 20:58] straka |
||
---|---|---|---|
Line 6: | Line 6: | ||
The number of mappers is determined automatically according to input files sizes. Every input file is divided into //splits//. The default split size is 32MB. Every file split is then executed by a different mapper. | The number of mappers is determined automatically according to input files sizes. Every input file is divided into //splits//. The default split size is 32MB. Every file split is then executed by a different mapper. | ||
- | The size of file split can be overridden by '' | + | The size of file split can be overridden by '' |
===== Multiple reducers ===== | ===== Multiple reducers ===== | ||
- | Then number of reducers is specified by the job, default number is one. As the outputs of reducers are not merged, there are as many output files as reducers. | + | The number of reducers is specified by the job, defaulting to one if unspecified. As the outputs of reducers are not merged, there are as many output files as reducers. |
To use multiple reducers, the MR job must be executed by a cluster (even with one computer), not locally. The number of reducers is specified by '' | To use multiple reducers, the MR job must be executed by a cluster (even with one computer), not locally. The number of reducers is specified by '' | ||
- | perl script.pl [-jt cluster_master | -c cluster_size [-w sec_to_wait]] [-r number_of_reducers] | + | perl script.pl |
+ | |||
+ | Optimal number of reducers is the same as the number of machines in the cluster, so that all the reducers can run in parallel at the same time. | ||
==== Partitioning ==== | ==== Partitioning ==== | ||
When there are multiple reducers, it is important how the (key, value) pairs are distributed between the reducers. | When there are multiple reducers, it is important how the (key, value) pairs are distributed between the reducers. | ||
- | By default, (key, value) pair is sent to reducer number //hash(key) modulo number_of_reducers// | + | By default, (key, value) pair is sent to a reducer number //hash(key) modulo number_of_reducers// |
- | To override the default behaviour, MR job can specify a // | + | To override the default behaviour, MR job can specify a // |
<code perl> | <code perl> | ||
Line 45: | Line 47: | ||
A MR job must have a reducer if it specifies a partitioner. Also, the partitioner is not called if there is only one reducer. | A MR job must have a reducer if it specifies a partitioner. Also, the partitioner is not called if there is only one reducer. | ||
- | ===== Example | + | ===== The order of keys during reduce |
+ | It is guaranteed that every reducer processes the keys in //ascending order//. | ||
+ | |||
+ | On the other hand, the order of values belonging to one key is undefined. | ||
+ | |||
+ | ===== Exercise ===== | ||
+ | |||
+ | Run one MR job on '/ | ||
+ | wget --no-check-certificate ' | ||
+ | rm -rf step-8-out-ex; | ||
+ | less step-8-out-ex/ | ||
+ | |||
+ | ==== Solution ==== | ||
+ | You can also download the solution {{: | ||
+ | wget --no-check-certificate ' | ||
+ | rm -rf step-8-out-sol; | ||
+ | less step-8-out-sol/ | ||
- | Run a MR job on '/ | + | ---- |
- | {{:courses: | + | < |
+ | <table style=" | ||
+ | < | ||
+ | <td style=" | ||
+ | <td style=" | ||
+ | <td style=" | ||
+ | </ | ||
+ | </ | ||
+ | </ |