Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 28 Dec 2011 04:25:30 +0000 (UTC)
From: "Zhihong Yu (Updated) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1350589674.47721.1325046330656.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1196312671.1027.1323691350904.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HBASE-5009) Failure of creating split dir if it
 already exists prevents splits from happening further
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhihong Yu updated HBASE-5009:
------------------------------

    Attachment: 5009.txt
    
> Failure of creating split dir if it already exists prevents splits from happening further
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-5009
>                 URL: https://issues.apache.org/jira/browse/HBASE-5009
>             Project: HBase
>          Issue Type: Bug
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 0.92.1, 0.90.6
>
>         Attachments: 5009.txt, HBASE-5009.patch, HBASE-5009_Branch90.patch
>
>
> The scenario is
> -> The split of a region takes a long time
> -> The deletion of the splitDir fails due to HDFS problems.
> -> Subsequent splits also fail after that.
> {code}
> private static void createSplitDir(final FileSystem fs, final Path splitdir)
>   throws IOException {
>     if (fs.exists(splitdir)) throw new IOException("Splitdir already exits? " + splitdir);
>     if (!fs.mkdirs(splitdir)) throw new IOException("Failed create of " + splitdir);
>   }
> {code}
> Correct me if am wrong? If it is an issue can we change the behaviour of throwing exception?
> Pls suggest.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira