Correct Answer : Get Lastest Questions and Answer : Explanation: The job submitter's view of the Job. It allows the user to configure the job, submit it, control its execution, and query the state. The set methods only work until the job is submitted, afterwards they will throw an IllegalStateException.
Question : You have submitted the Job and then you call a setXXX() method on that job instance, what will happen ?
1. It will set new values on submitted job and apply on runtime
2. It will set new values and will be applied only in the Mapper and Reducer which yet to start
4. It will not through any error and silently discard new set value
Correct Answer : Get Lastest Questions and Answer : Explanation: The job submitter's view of the Job. It allows the user to configure the job, submit it, control its execution, and query the state. The set methods only work until the job is submitted, afterwards they will throw an IllegalStateException.
Question : Which of the following is true?
1. Both submit() and waitForCompletion() methods are blocking call
2. Both submit() and waitForCompletion() methods are non-blocking call
Correct Answer : Get Lastest Questions and Answer : Explanation: If your aim is to run jobs in parallel then there is certainly no risk in using job.submit(). The main reason job.waitForCompletion exists is that it's method call returns only when the job gets finished, and it returns with it's success or failure status which can be used to determine that further steps are to be run or not.
Now, getting back at you seeing only the first job being executed, this is because by default Hadoop schedules the jobs in FIFO order. You certainly can change this behavior.