[
https://issues.apache.org/jira/browse/HBASE-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311887#comment-14311887
]
hongyu bi commented on HBASE-3473:
----------------------------------
Hi [~lhofhansl]，
we may try parallel replication by hash rowkey to thread# , so we can preserve
ordering on row-level which i think is fine to HBase.
thanks
> Add a configuration property for socket receive buffer size for replication
> endpoints
> -------------------------------------------------------------------------------------
>
> Key: HBASE-3473
> URL: https://issues.apache.org/jira/browse/HBASE-3473
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Reporter: Gary Helmling
> Priority: Minor
>
> Looking at this blog post about optimizing replication throughput for
> LinkedIn's Kafka:
> http://sna-projects.com/blog/2011/01/optimizing-tcp-socket-across-data-centers/
> It seems worth testing out if HBase replication connections can also benefit
> from increasing the socket receive buffer size on (expected to be)
> high-latency connections.
> To this end, we would add a new configuration property for receive buffer
> size for replication connection and do some benchmarking to evaluate
> throughput with different values, verifying that making this configurable
> would have significant impact. For the moment, it seems best to scope the
> configuration setting to replication connections only, in order to avoid also
> impacting (negatively) intra-cluster communications.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
