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

Hudson commented on HBASE-6647:
-------------------------------

Integrated in HBase-0.94 #445 (See 
[https://builds.apache.org/job/HBase-0.94/445/])
    HBASE-6321  ReplicationSource dies reading the peer's id
HBASE-6647  [performance regression] appendNoSync/HBASE-4528 doesn't
            take deferred log flush into account (Revision 1379290)

     Result = FAILURE
jdcryans : 
Files : 
* 
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
* 
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLog.java
* 
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/replication/ReplicationZookeeper.java
* 
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java

                
> [performance regression] appendNoSync/HBASE-4528 doesn't take deferred log 
> flush into account
> ---------------------------------------------------------------------------------------------
>
>                 Key: HBASE-6647
>                 URL: https://issues.apache.org/jira/browse/HBASE-6647
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.94.0
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.96.0, 0.94.2
>
>         Attachments: HBASE-6647-0.94.patch, HBASE-6647-0.94-v2.patch, 
> HBASE-6647-0.94-v3.patch, HBASE-6647.pach
>
>
> Since we upgraded to 0.94.1 from 0.92 I saw that our ICVs are about twice as 
> slow as they were. jstack'ing I saw that most of the time we are waiting on 
> sync()... but those tables have deferred log flush turned on so they 
> shouldn't even be calling it.
> HTD.isDeferredLogFlush is currently only called in the append() methods which 
> are pretty much not in use anymore.

--
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

Reply via email to