Hey Mayuran, One reason might be that the input data is available only on few nodes and Hence only that node is being used for mappers .. You should be able to run A dfs fsck and see for the input path how many actual replicas do you have.
Otherwise go to the slaves and take a thread-dump for all java child processes ?? (kill -3) The threaddump will go into hadoop logs and you can look them through hadoop UI if the mappers are getting stuck somewhere. Best Bhupesh On 8/12/09 1:36 PM, "Mayuran Yogarajah" <[email protected]> wrote: > Amandeep Khurana wrote: >> >> Ah.. That might be the issue.. I dont know the solution to this.. Wait for >> someone else to answer. The mappers not starting could be because of this as >> well. >> >> Whats your cluster configuration? How many cpu's, RAM etc...? >> >> > There are 6 servers in the cluster, they're all the same hardware > cpu/ram wise: 2xquad core > and 6gigs of ram. > > thanks, > M > >
