66% is the start of the reduce function so its likely a endless loop there burning the cpu cycles

"Amandeep Khurana" <[email protected]> wrote in message news:[email protected]...
I have a MR job running on approximately 150000 lines of data in a text
file. The reducer hangs at 66% and at that moment the cpu usage is at 100%.
After 600 seconds, it kills the job... What could be going wrong and where
should I look for the problem?


Amandeep Khurana
Computer Science Graduate Student
University of California, Santa Cruz



Reply via email to