[
https://issues.apache.org/jira/browse/HBASE-9676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784198#comment-13784198
]
Nick Dimiduk commented on HBASE-9676:
-------------------------------------
bq. 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.
Oh, that's true. We need to adopt this tagline: "The only guarantee is that
there are no guarantees! (outside of single row operations)." This whole
business is best left up to MultiRowMutationEndpoint, then.
Thanks for clarifying.
> 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)
