[ 
https://issues.apache.org/jira/browse/LENS-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718214#comment-14718214
 ] 

Amareshwari Sriramadasu commented on LENS-753:
----------------------------------------------

bq. Giving queue numbers from waiting query collection may not be correct as 
they are not consistent. When a candidate query is picked up from waiting 
state, it is removed from the collection and checked for cost constraints. If 
it fails the constraints, the query is added back to the waiting query 
collection. This causes inconsistency in terms of indices of queries within the 
collection. Because of this inconsistency, user might see their queue number 
increasing.

Where is the requirement of queue number has to decrease always? If the 
position in queue is increased because of a high priority query, then position 
number getting incremented should be acceptable to user and same should be 
communicated to user.  Why are we saying this is inconsistent behavior? I don't 
agree with it.

> Queue number for queries in submitted queue
> -------------------------------------------
>
>                 Key: LENS-753
>                 URL: https://issues.apache.org/jira/browse/LENS-753
>             Project: Apache Lens
>          Issue Type: Improvement
>            Reporter: Akshay Goyal
>            Assignee: Akshay Goyal
>             Fix For: 2.4
>
>         Attachments: LENS-753.02.patch
>
>
> This is to add queue number for queries after they were launched, in order to 
> give users an idea of the sequence in which their queries were launched. Or 
> in other words, to give them an idea of how many queries were launched before 
> them which are still competing for resources with their query. 
> Giving queue numbers from waiting query collection may not be correct as they 
> are not consistent. When a candidate query is picked up from waiting state, 
> it is removed from the collection and checked for cost constraints. If it 
> fails the constraints, the query is added back to the waiting query 
> collection. This causes inconsistency in terms of indices of queries within 
> the collection. Because of this inconsistency, user might see their queue 
> number increasing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to