Question : Developer has submitted the YARN Job, by calling submitApplication() method on Resource Manager. Please select the correct order of the below steps after that
1. Container will be managed by Node Manager after job submission 2. Resource Manager triggers its sub-component Scheduler, which allocates containers for mapreduce job execution. 3. Access Mostly Uused Products by 50000+ Subscribers
Explanation: Job Start up: The call to Job.waitForCompletion() in the main driver class is where all the execution starts. The driver is the only piece of code that runs on our local machine, and this call starts the communication with the Resource Manager. Retrieves the new Job ID or Application ID from Resource Manager. The Client Node copies Job Resources specified via the -files, -archives, and -libjars command-line arguments, as well as the job JAR file on to HDFS. Finally, Job is submitted by calling submitApplication() method on Resource Manager. Resource Manager triggers its sub-component Scheduler, which allocates containers for mapreduce job execution. Then Resource Manager starts Application Master in the container provided by the scheduler. This container will be managed by Node Manager from here on wards.
You can also Refer/Consider Advance Hadoop YARN Training by HadoopExam.com
Question : Which statement is correct for below code snippet
public class TokenCounterMapper extends Mapper [Object, Text, Text, IntWritable>{
private final static IntWritable one = new IntWritable(1); private Text word = new Text();
public void map(Object key, Text value, Context context) throws IOException, InterruptedException { StringTokenizer itr = new StringTokenizer(value.toString()); while (itr.hasMoreTokens()) { word.set(itr.nextToken()); } context.write(word, one);
1. The client queries the NameNode for the block location(s). The NameNode returns the block location(s) to the client. The client reads the data directory off the DataNode(s).
2. The client queries all DataNodes in parallel. The DataNode that contains the requested data responds directly to the client. The client reads the data directly off the DataNode.
3. The client contacts the NameNode for the block location(s). The NameNode then queries the DataNodes for block locations. The DataNodes respond to the NameNode, and the NameNode redirects the client to the DataNode that holds the requested data block(s). The client then reads the data directly off the DataNode. 4. The client contacts the NameNode for the block location(s). The NameNode contacts the DataNode that holds the requested data block. Data is transferred from the DataNode to the NameNode, and then from the NameNode to the client.