Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes to the MapReduce algorithm. #374

Open
GoldenBadger opened this issue Feb 22, 2018 · 0 comments
Open

Changes to the MapReduce algorithm. #374

GoldenBadger opened this issue Feb 22, 2018 · 0 comments

Comments

@GoldenBadger
Copy link
Contributor

As discussed in the Sprint 5 planning meeting, we would like to rework the mapreduce algorithm itself to be closer to Apache Hadoop's flow.

The proposed order of operations is as follows:

  1. Mappers get data from external data source (FS).
  2. When a mapper completes all of its assigned tasks, it performs a Combine step followed by a Partition step on the intermediate data saved to its local disk.
  3. When all mappers have completed their tasks, the Shuffle step begins, which is simply the movement of local intermediate files to the FS for further processing.
  4. Then the Merge step combines the values of all duplicate keys.
  5. Finally, the intermediate data is sent to the reducers for final processing.
@GoldenBadger GoldenBadger added this to the Sprint 5 milestone Feb 22, 2018
@GoldenBadger GoldenBadger added this to To do in Heracles via automation Feb 22, 2018
@VoyTechnology VoyTechnology moved this from Backlog to Sprint 5 in Heracles Feb 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Heracles
  
Sprint 5
Development

No branches or pull requests

1 participant