indeed, this has bitten me a while back, but now the default Cloudera
distribution configures them outside of /tmp
Really, as Eric has pointed out, I was making failure a regular occasion, by
bringing one computer down.
On Thu, Mar 3, 2011 at 10:05 PM, Harsh J <[EMAIL PROTECTED]> wrote:
> This appears to me like the simple case of your OS clearing out your
> /tmp at every boot. You will lose all data + fsimage if you haven't
> configured your dfs.data.dir and dfs.name.dir to not be located on
> On Fri, Mar 4, 2011 at 5:14 AM, Mark Kerzner <[EMAIL PROTECTED]>
> > It finally dawns on me that with such small cluster I better shut the
> > daemons down, for otherwise they are trying too hard to compensate for
> > missing node and eventually it goes bad. Is my understanding correct?
> Are your dfs.data.dir and/or dfs.name.dir properties pointing to
> locations on /tmp, by the way? This appears to me like the simple case
> of your OS clearing out your /tmp on boot. You will lose all data +
> fsimage this way if you haven't configured your dfs.data.dir and
> dfs.name.dir to not be located on /tmp.
> Harsh J