[
https://issues.apache.org/jira/browse/HBASE-12719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14263418#comment-14263418
]
Hudson commented on HBASE-12719:
--------------------------------
SUCCESS: Integrated in HBase-1.0 #628 (See
[https://builds.apache.org/job/HBase-1.0/628/])
HBASE-12719 test provider to remove just the hdfs interactions from fshlog.
(enis: rev bc464cc745cd3d021eb9072fc40c3a0543e247f1)
* hbase-server/src/test/java/org/apache/hadoop/hbase/wal/IOTestProvider.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/wal/DisabledWALProvider.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java
> Add test WAL provider to quantify FSHLog overhead in the absence of HDFS.
> -------------------------------------------------------------------------
>
> Key: HBASE-12719
> URL: https://issues.apache.org/jira/browse/HBASE-12719
> Project: HBase
> Issue Type: Improvement
> Components: test, wal
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Minor
> Fix For: 1.0.0, 2.0.0, 1.1.0
>
> Attachments: HBASE-12719.1.patch.txt, HBASE-12719.2.patch.txt,
> HBASE-12719_comparison_chart.tiff
>
>
> Discussion in HBASE-5699 included showing the max throughput for our WAL
> benchmark (using the DisabledWALProvider) compared to when we are actually
> dealing with synchronization and talking with HDFS.
> What we can't see in that comparison is how much of the (sizable) gap is due
> to the coordination done in FSHLog to deal with multi-threading and how much
> of it is due to talking to HDFS.
> Make a test-only provider that we can use to isolate the cost for HDFS
> appends, HDFS flush, and file rolling.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
