[
https://issues.apache.org/jira/browse/HBASE-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169264#comment-13169264
]
Anoop Sam John commented on HBASE-5009:
---------------------------------------
Due to the max wait time out elapse, when we drop the split attempt, we just
shutdown the thread pool which do the StoreFileSplitter tasks. This will not
guarantee the stop of the threads . Dont you think this could be an issue?
After the time out the split log thread will start the rollback but some
threads which it had started still might be there alive and can do some work
afterwards.
Ram - The split rollback need to ensure the closure of these threads also?
> 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
> Affects Versions: 0.90.6
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
>
> 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
