It could be something strange like that. You should still be able to access the task tracker's logs to see output from the jobs, which could indicate the issue -- are you looking at those logs rather than the namenode?
On Mon, May 3, 2010 at 8:32 PM, Tamas Jambor <[email protected]> wrote: > I still couldn't figure out the problem, it stucks at the same point. there > are no errors in the log file. > maybe it gets into an infinite loop? >
