[
https://issues.apache.org/jira/browse/HBASE-9676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783738#comment-13783738
]
Nicolas Liochon commented on HBASE-9676:
----------------------------------------
bq. By setting hbase.client.max.perregion.tasks > 1 the user has accepted the
possibility of the RS ACKing writes out of order.
Yes, that's why I set it to 1 by default (and I tend to think that at the end
nobody will actually change this). The guarantees are brittle whatever this
setting or .94 / .96: if there is a split while you're sending your puts, the
last put may be inserted before the first, even if initially they were on the
same region.
I think the total task & the region server config should make it to the
hbase-site.xml, but not on the one on the regions...
> AsyncProcess can create more tasks than hbase.client.max.total.tasks
> --------------------------------------------------------------------
>
> Key: HBASE-9676
> URL: https://issues.apache.org/jira/browse/HBASE-9676
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.98.0, 0.96.0
> Reporter: Nicolas Liochon
> Assignee: Nicolas Liochon
> Priority: Critical
> Fix For: 0.98.0, 0.96.1
>
> Attachments: 9676.v2.patch, 9676.v3.patch, 9676.v4.patch
>
>
> hbase.client.max.total.tasks allows to control the number of tasks in
> progress. But when adding tasks, we take only into account the number of
> tasks currently running, not the one we're creating.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
