3 ms·

I have to disagree completely with your example of horrible naming conventions regarding the jobtracker and tasktracker. The names are very descriptive and conv

I have to disagree completely with your example of horrible naming conventions regarding the jobtracker and tasktracker. The names are very descriptive and convey enough details to know what their purpose is. http://hadoop.apache.org/mapreduce/docs/current/mapred_tutorial.html#Job+Submission+and+Monitoring http://hadoop.apache.org/mapreduce/docs/current/mapred_tutor... "The MapReduce framework consists of a single master JobTracker and one slave TaskTracker per cluster-node. The master is responsible for scheduling the jobs' component tasks on the slaves, monitoring them and re-executing the failed tasks. The slaves execute the tasks as directed by the master." If your problems is in remembering the difference perhaps you have not spent enough time understanding the tools you are using.

programnature 15y ago
I think OP is saying he understands the difference in what they do, but can't keep the names straight. I felt the same way for the first few months of using hadoop. I eventually got that in real-life, a task is just a subpiece of a job. But the naming is not immediately evocative of the relationship, particularly since in computing, "job" is pretty overloaded. Far better would be "job" and "subjob".