[
https://issues.apache.org/jira/browse/LENS-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329264#comment-15329264
]
Hadoop QA commented on LENS-1164:
---------------------------------
Applied patch:
[LENS-1164-2.patch|https://issues.apache.org/jira/secure/attachment/12810360/LENS-1164-2.patch]
and ran command: mvn clean install -fae. Result: Failure. Build Job:
https://builds.apache.org/job/PreCommit-Lens-Build/601/
> Query getting stuck in queue for inmemory queries
> -------------------------------------------------
>
> Key: LENS-1164
> URL: https://issues.apache.org/jira/browse/LENS-1164
> Project: Apache Lens
> Issue Type: Bug
> Components: server
> Affects Versions: 2.6
> Reporter: Archana H
> Assignee: Sushil Mohanty
> Fix For: 2.6
>
> Attachments: LENS-1164-2.patch
>
>
> Scenario:
> Max concurrent set to 1 and both persistence is false.
> 3 queries are fired. 1 goes to running, rest 2 queued.
> Even after 1st query is purged (after crossing TTL time), queries from queued
> are not getting picked for running. Any new query fired is getting completed,
> but those 2 are stuck in queue.
> This is happening because queries gets picked from waiting queue only upon
> query completion but in this case query is already completed.
> But when new query is fired and it completes, queries in waiting queue should
> be considered for running which is not happening in this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
