|
|
# MapReduce
|
|
|
**Due: Wed Jan 13, 9:00pm**
|
|
|
|
|
|
*Modified from the [MIT 6.824 Labs][mit-labs]*
|
|
|
*Modified from the [MIT 6.824 Labs][mit-lab]*
|
|
|
|
|
|
|
|
|
## Introduction
|
... | ... | @@ -184,7 +184,7 @@ $ rm mrtmp.* |
|
|
```
|
|
|
|
|
|
|
|
|
## Part II: Distributing MapReduce jobs
|
|
|
## Part II: Distributing MapReduce Jobs
|
|
|
|
|
|
In this part you will complete a version of MapReduce that splits the work up
|
|
|
over a set of worker threads, in order to exploit multiple cores. A master
|
... | ... | @@ -221,7 +221,7 @@ of tests in `test_test.go`. You run unit tests in a package directory (e.g., the |
|
|
mapreduce directory) as follows:
|
|
|
|
|
|
```sh
|
|
|
$ cd mapreduce
|
|
|
$ cd mapreduce
|
|
|
$ go test
|
|
|
```
|
|
|
|
... | ... | @@ -266,7 +266,7 @@ something like this: |
|
|
```
|
|
|
The important thing to look for is a `PASS` at the end of your output indicating
|
|
|
that your implementation has passed all of the unit tests. If you would like to
|
|
|
not see these errors, we have provided a script (`/bin/run-tests`) which you can
|
|
|
not see these errors, we have provided a script (`/bin/run-test`) which you can
|
|
|
run in place of `go test`.
|
|
|
|
|
|
**Hint:** Use a `select` to check for new worker registrations as well as
|
... | ... | @@ -325,7 +325,7 @@ Make sure that you have done the following: |
|
|
the file you will upload to the Catalyst dropbox
|
|
|
|
|
|
|
|
|
[mit-labs]: http://css.csail.mit.edu/6.824/2015/labs/lab-1.html
|
|
|
[mit-lab]: http://nil.csail.mit.edu/6.824/2015/labs/lab-1.html
|
|
|
[mapreduce-pdf]: http://research.google.com/archive/mapreduce-osdi04.pdf
|
|
|
[go]: http://www.golang.org
|
|
|
[macports]: https://www.macports.org/
|
... | ... | |