For each action a job is launched by oozie:launcher which in turn executes your actual action job. For example you have a flow like :-
It actually going to launch 4 MR's as below:-
So, at this point of time four Map slots are required (two for MR launchers, two for actual jobs). But, default only two Map slots are available in each node. That is, only two Map tasks will run at any point of time in a node. This is specified by the `mapred.tasktracker.map.tasks.maximum` property which defaults to 2 in the mapred-site.xml file.
Available slots are occupied by 2 launchers and So, the 2 Jobs wait for available slots.
This happens in pseudo-distributed mode. So may be one can run it over cluster or change "mapred.tasktracker.map.tasks.maximum" property in mapred-site.xml.
Note that setting property in pseudo -distribute may not even work. So, one might has to bump Memory and Cores too.
It actually going to launch 4 MR's as below:-
So, at this point of time four Map slots are required (two for MR launchers, two for actual jobs). But, default only two Map slots are available in each node. That is, only two Map tasks will run at any point of time in a node. This is specified by the `mapred.tasktracker.map.tasks.maximum` property which defaults to 2 in the mapred-site.xml file.
Available slots are occupied by 2 launchers and So, the 2 Jobs wait for available slots.
This happens in pseudo-distributed mode. So may be one can run it over cluster or change "mapred.tasktracker.map.tasks.maximum" property in mapred-site.xml.
Note that setting property in pseudo -distribute may not even work. So, one might has to bump Memory and Cores too.
Comments
Post a Comment