[
https://issues.apache.org/jira/browse/KUDU-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke updated KUDU-993:
-----------------------------
Target Version/s: (was: 1.6.0)
> Investigate making transaction tracker rejections more fair
> -----------------------------------------------------------
>
> Key: KUDU-993
> URL: https://issues.apache.org/jira/browse/KUDU-993
> Project: Kudu
> Issue Type: Improvement
> Components: tablet
> Affects Versions: Public beta
> Reporter: Adar Dembo
> Priority: Major
>
> When the transaction tracker hits its memory limit, it'll reject new
> transactions until pending transactions finish. Clients respond by retrying
> the failed transactions until the transaction tracker accepts them, or until
> they timeout.
> The rejection mechanism doesn't take into account how many times a
> transaction has been retried, and as a result, it's possible for some
> transactions to be rejected many times over even as other transactions are
> allowed through. Here's a contrived example: two clients submitting
> transactions simultaneously, with room for only one pending transaction.
> Given a long retry backoff delay and a short delay between transactions, it's
> possible for one client to "hog" the available space while the other
> continuously retries (each time it retries, the first client has managed to
> stuff another transaction in).
> We should investigate making this rejection system more fair so that no one
> transaction is starved.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
