You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2012/12/20 04:03:12 UTC

[jira] [Commented] (HBASE-7400) ExportSnapshot mapper closes the FileSystem

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

Hadoop QA commented on HBASE-7400:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12561836/HBASE-7400-v0.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3630//console

This message is automatically generated.
                
> ExportSnapshot mapper closes the FileSystem
> -------------------------------------------
>
>                 Key: HBASE-7400
>                 URL: https://issues.apache.org/jira/browse/HBASE-7400
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client, master, regionserver, snapshots, Zookeeper
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>            Priority: Blocker
>             Fix For: hbase-6055, 0.96.0
>
>         Attachments: HBASE-7400-v0.patch
>
>
> The ExportSnapshotMapper closes the FileSystem on cleanup,
> and in case of shared instead, since there's no ref count, the job fails.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira