[
https://issues.apache.org/jira/browse/HBASE-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404551#comment-13404551
]
stack commented on HBASE-6116:
------------------------------
Dumb?: For sure the //writing was enabled? If saturated network, I could
imagine it not making a diff but if spare bandwidth.... I'd think it'd show
through. The //write would make us saturate the network on an interface before
a -- (pipeline) write would I suppose. And its easy enough for PE to saturate
network IIRC anyway, w/o //writes.
> Allow parallel HDFS writes for HLogs.
> -------------------------------------
>
> Key: HBASE-6116
> URL: https://issues.apache.org/jira/browse/HBASE-6116
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Attachments: 6116-v1.txt, apurtell-patches.zip,
> pipelined-vs-parallel-comparison.zip
>
>
> In HDFS-1783 I adapted Dhrubas changes to be used in Hadoop trunk.
> This issue will include the necessary reflection changes to optionally enable
> this for the WALs in HBase.
--
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
