ge and any attachments to it are confidential and
>> may be legally privileged. If you have received this message in error, you
>> should delete it from your system immediately and advise the sender.
>> To any recipient of this message within HP, unless otherwise stated you
L".
-Original Message-
From: Todd Lipcon [mailto:t...@cloudera.com]
Sent: 09 February 2010 01:11
To: hdfs-dev@hadoop.apache.org
Subject: Re: Name Node Corruption When Shutdown Too Soon
Hi Jonathan,
Another question: how have you configured dfs.name.dir? Do you have
several directo
message in error, you
> should delete it from your system immediately and advise the sender.
> To any recipient of this message within HP, unless otherwise stated you
> should consider this message and attachments as "HP CONFIDENTIAL".
>
>
> -Original Message-----
&g
sage within HP, unless otherwise stated you should
consider this message and attachments as "HP CONFIDENTIAL".
-Original Message-
From: Todd Lipcon [mailto:t...@cloudera.com]
Sent: 09 February 2010 01:11
To: hdfs-dev@hadoop.apache.org
Subject: Re: Name Node Corruption When Shutdo
Hi Jonathan,
Another question: how have you configured dfs.name.dir? Do you have
several directories configured?
Thanks
-Todd
On Mon, Feb 8, 2010 at 4:45 PM, Todd Lipcon wrote:
> Hey Jonathan,
>
> As Konstantin mentioned, I've been looking into a couple issues that
> could be related. At first
Hey Jonathan,
As Konstantin mentioned, I've been looking into a couple issues that
could be related. At first glance it doesn't sound like you've run
into quite the same thing.
What version did you see this on? The steps to reproduce are something like:
1) Start a NN
2) Perform a bunch of edits
Hi Jonathan,
Thank you for raising the issue.
We will need more information about your configuration files.
It sounds like a problem noted by Todd in HDFS-909.
If edits directory precedes image in configuration, then edits
will be emptied prior to saving the image.
Any way it worth filing a jir
