Ch 8 Big Data - Exam IV

a series of steps that need to occur in service to an overall goal

states that the order that a (MapReduce) function is executed doesn't matter

foundational behaviors of MapReduce

MapReduce functional behavior that states that mapping must be concluded before reducing can take place

MapReduce functional behavior when all the mapping is complete & reducing begins.  Gathers and prepares all the mapped data for reduction

MapReduce functional behavior where code and its related data are placed on the same node prior to execution

MapReduce functional behavior where the engine must recognize that something is wrong and make the necessary correctionss

three categories of optimization techniques used to improve the reliability & performance of MapReduce jobs

MapReduce optimization technique that states that the closer the hardware processing elements are to each other, the less latency you will have to deal with.

MapReduce optimization technique that states that all values from the same key are sent to the same reducer

MapReduce optimization technique that states that a "warm standby" should be kept.  Also that lots of small files should be avoided, and long stretches of bandwidth are necessary, as well as security

the grammer in a programming language

an error produced when a program is able to run, but doesn't produce resonable output

a set of instructions that are performed one instruction at a time in the order stated

a set of instructions that are performed according to the outcome of a question

a set of instructions that are performed iteratively until something tells it to stop

high level structures that can be combined to create programs

something that a function is going to work on

the structure that encompases the code and the arguements - a code cluster - usually returns something (a value) passed back through variables

a set of instructions that do a specific task often needing information passed to it in variables so it can perform the task

large sets of code organized to allow for reuse for certain tasks - these often include a type of code cluster called a function

a program that allows large sets of data to be worked with at the same time over a number of nodes

steps in the MapReduce process

MapReduce behavior that self manages the number of tasks and the number of nodes so that all mapping occurs prior to reducing

MapReduce behavior that self manages the tasks by holding task results in limbo until all have completed; once tasks are completed maps are placed in a "shuffle & sort" area

MapReduce behavior that sends a copy of the code to each node because there is enhanced efficiency when the data and the code reside in the same node

MapReduce behavior that all programs "should" include which allows the system to properly realize when a failure or error occurs (ie: assigning a new node to complete a filed node's process)