[
https://issues.apache.org/jira/browse/IMPALA-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16872494#comment-16872494
]
Lars Volker commented on IMPALA-2968:
-------------------------------------
One easy way that I can think of to do this is to add a "attempts before
blocking" counter to each queue node. Every time a node fails to get admitted,
we increment the counter by 1, and when hitting a configurable limit (e.g. 5)
we block.
[~bikramjeet.vig], [~tarmstrong], [~asherman] - Thoughts?
> Improve admission control dequeuing policy
> ------------------------------------------
>
> Key: IMPALA-2968
> URL: https://issues.apache.org/jira/browse/IMPALA-2968
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 2.3.0
> Reporter: Matthew Jacobs
> Priority: Minor
> Labels: admission-control, resource-management
>
> The current behavior only attempts to admit the head of the queue but the
> head might need resources which are contended (e.g. on a hot node) while a
> queued request behind the head might be admitted. We should consider a policy
> which would not block the entire queue but yet is unlikely to starve the head
> if other requests are continuously admitted from behind it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
