Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <27442759.89941276564033812.JavaMail.jira@thor>
Date: Mon, 14 Jun 2010 21:07:13 -0400 (EDT)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Commented: (HBASE-2728) Support for HADOOP-4829
In-Reply-To: <18281149.89481276562294750.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878819#action_12878819 ] 

Todd Lipcon commented on HBASE-2728:
------------------------------------

Here's a thought. What if we did something like:
FileSystem fs = FileSystem.get(conf);
fs.close();
fs = FileSystem.get(conf); // now we know we have a fresh instance?

Or, if we're certain we always get the filesystem instance from this var, we could use FileSystem.newInstance?

My only nervousness is that this might break again and we wouldn't notice (since we don't seem to have any good unit tests for it)

> Support for HADOOP-4829
> -----------------------
>
>                 Key: HBASE-2728
>                 URL: https://issues.apache.org/jira/browse/HBASE-2728
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.20.6
>
>         Attachments: HBASE-2728.patch
>
>
> Users who have a HADOOP-4829 patched hadoop will run into the issue that closing a RS cleanly result into data loss because the FileSystem will be closed before the regions are. Cloudera is an example. We need to support those users.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.