[
https://issues.apache.org/jira/browse/HBASE-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13265421#comment-13265421
]
Todd Lipcon commented on HBASE-5699:
------------------------------------
bq. I disagree, considering that most of the deployments have rep=3 you're
using three spindles not one
That said, most of our customers are deploying 6 disks if not 12 :)
IMO the other big gain we can get from multiple WALs is to automatically switch
between WALs when one gets "slow". IMO we should maintain a count of
outstanding requests (probably by size) for each WAL, and submit writes to
whichever has fewer outstanding requests. That way if one is faster, it will
take more of the load. Then simultaneously measure trailing latency stats on
each WAL, and if one is significantly slower than the other for some period of
time, have it roll (to try to get a new set of disks/nodes)
> Run with > 1 WAL in HRegionServer
> ---------------------------------
>
> Key: HBASE-5699
> URL: https://issues.apache.org/jira/browse/HBASE-5699
> Project: HBase
> Issue Type: Improvement
> Reporter: binlijin
> Assignee: Li Pi
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
