[
https://issues.apache.org/jira/browse/HBASE-10094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-10094:
--------------------------
Resolution: Fixed
Fix Version/s: 0.99.0
0.96.1
0.98.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Thanks Himanshu. Yeah, gives some insight on sync rates. Let me see if can
get better reporting, a reporting that will expose clumping of syncs or syncing
even though only a little amount of data has been written. This would be good
to know too.
> Add batching to HLogPerformanceEvaluation
> -----------------------------------------
>
> Key: HBASE-10094
> URL: https://issues.apache.org/jira/browse/HBASE-10094
> Project: HBase
> Issue Type: Sub-task
> Components: Performance, wal
> Reporter: stack
> Assignee: Himanshu Vashishtha
> Fix For: 0.98.0, 0.96.1, 0.99.0
>
> Attachments: 10094v2.txt
>
>
> As Himanshu points out in the the parent issue, HLogPE is using an unorthodox
> API appending edits to the WAL; it is using an API that is meant for tests
> only that does an append immediately followed by a sync call.
> In normal deploy, WAL appends are done as a bunch of appends followed by a
> sync on the tail of the transaction -- not a sync per append.
> This issue is about changing HLogPE to use append and then sync. It also
> adds an argument so you can specifying batching of a set of appends before
> the sync is called. The latter lets HLogPE mimic multi puts that use the
> minibatch... which appends, appends, appends.. and then syncs.
> Assigning to Himanshu for review.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
