I once read somewhere that as applications are running, the job tracker receives updates directly from the task tracker nodes, which enables it to track progress and also coordinate failures in some cases. The task tracker isn’t a daemon process in the Hadoop cluster; for instance, the task tracker runs on slave nodes in the Hadoop cluster, which only means that each slave node has its service tied to task tracker and the storage which allows for Hadoop to be a distributed system.
The task tracker runs its processes resources on each of the slave nodes in the form of processing slots and not via the daemon processes. Although some studies say otherwise. I hope this helps.
I once read somewhere that as applications are running, the job tracker receives updates directly from the task tracker nodes, which enables it to track progress and also coordinate failures in some cases. The task tracker isn’t a daemon process in the Hadoop cluster; for instance, the task tracker runs on slave nodes in the Hadoop cluster, which only means that each slave node has its service tied to task tracker and the storage which allows for Hadoop to be a distributed system. The task tracker runs its processes resources on each of the slave nodes in the form of processing slots and not via the daemon processes. Although some studies say otherwise. I hope this helps.
Answer Anonymously
Copy Link
