hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7944) Replication leaks file reader resource & not reset currentNbOperations
Date Wed, 27 Feb 2013 18:23:13 GMT

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

Hadoop QA commented on HBASE-7944:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  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
                        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/4581//console

This message is automatically generated.
> Replication leaks file reader resource & not reset currentNbOperations
> ----------------------------------------------------------------------
>                 Key: HBASE-7944
>                 URL: https://issues.apache.org/jira/browse/HBASE-7944
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>             Fix For: 0.95.0
>         Attachments: 0.94.patch, hbase-7944.patch
> When I trace test case TestReplicationQueueFailover, I found current replication logic
has two following issues:
> 1) leak file reader when finishing read a file in function finishCurrentFile
> 2) never reset currentNbOperations(this can be seen in the attached error log) such as
"currentNbOperations:12655 and seenEntries:0 and size: 0" inconsistant info. 

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

View raw message