Hi Harsh
I check branch-1 and there is no such problem in it. This bug is only
related to CDH3 version.Sorry for bothering you.
On Mon, Apr 8, 2013 at 5:24 PM, Harsh J wrote:
> Anty,
>
> Worth checking if you can spot the bug in branch-1 as well:
>
> http://svn.apache.org/r
@Harsh
I'm using CDH3u4.However, the processing logical with regard to FSEditlog
between CDH3U4 and hadoop 1.0.2 is almost the same.
So i'm not sure it is proper to file a JIRA?
On Mon, Apr 8, 2013 at 4:33 PM, Harsh J wrote:
> Thanks for analyzing and reporting this Anty,
>
&
-- Forwarded message --
From: Anty
Date: Sun, Apr 7, 2013 at 5:48 PM
Subject: Probably a bug in FsEditLog
To: hdfs-dev@hadoop.apache.org, Chance Li
Hi:ALL
In our cluster, we configure the NameNode to write to both local and NFS
mounted directories. When the NFS mounted
s already been removed from other thread
by invoking FSEditLog#logEdit
If this was exactly a bug, my proposal fix is in method FSEditlog#logsync
ignore or print some warning message instead of aborting the namenode when
error edit stream doesn't exist in FSEditLog#editStreams
--
Best Regards
Anty Rao
