Hi everyone,
I applied the patch provided at
https://issues.apache.org/jira/browse/HADOOP-2873 and my
namenode/cluster is up again without formatting it :-) Thanks for the
quick help!
Reading and writing to the cluster seems to work fine except for MapRed
jobs: All counters say 0 even I can
Hi Raghu,
done: https://issues.apache.org/jira/browse/HADOOP-2873
Subsequent tries did not succeed - so it looks like I need to re-format
the cluster :-(
Cu on the 'net,
Bye - bye,
André èrbnA
Raghu Angadi wrote:
Please file a jira
André,
You can try to rollback.
You did use upgrade when you switched to the new trunk, right?
--Konstantin
Raghu Angadi wrote:
André Martin wrote:
Hi Raghu,
done: https://issues.apache.org/jira/browse/HADOOP-2873
Subsequent tries did not succeed - so it looks like I need to
re-format the
Raghu Angadi wrote:
Please report such problems if you think it was because of HDFS, as
opposed to some hardware or disk failures.
Will do. I suspect it's something else. I'm testing on a notebook in
pseudo-distributed
mode (per the quick start guide). My IP changes when I take that box
-Original Message-
From: Steve Sapovits [mailto:[EMAIL PROTECTED]
Sent: Friday, February 22, 2008 2:34 PM
To: core-user@hadoop.apache.org
Subject: Re: Namenode fails to re-start after cluster shutdown
Raghu Angadi wrote:
Please report such problems if you think it was because of HDFS, as
opposed
