Hi, yaotian
I think you should check logs on the very tasktracker, it'll tell you why.
And here's some tips on deploying a MR job.
http://blog.cloudera.com/blog/2009/12/7-tips-for-improving-mapreduce-performance/
Charlie
At 2013-01-15 16:34:27,yaotian yaot...@gmail.com wrote:
I set
hi, 吴靖
I have got this error before. Please stop hbase on your cluster first. And
restart them with certain sequences: first regionserver on all nodes, then
hmaster.
Wish it helps.
Regards, Charlie
发件人： 吴靖 qhwj2...@126.com
收件人： user@hadoop.apache.org
发送日期
it will happen.
Of course, the real question is how to get a secondary name node going
with as little risk as possible. Should we just start up the
secondary name node? Or should we restart the name node first? Or is
there some other way for us to get right with our cluster?
Thanks,
Charlie
