[
https://issues.apache.org/jira/browse/LENS-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904438#comment-14904438
]
Hudson commented on LENS-777:
-----------------------------
FAILURE: Integrated in Lens-Commit #1089 (See
[https://builds.apache.org/job/Lens-Commit/1089/])
LENS-777: Fix: Waiting query selector change from intersecting to union
(rajatgupta59: rev 7ad12ed738abbf14d0b5bfe29dd45de209d32167)
*
lens-server/src/main/java/org/apache/lens/server/query/collect/UnioningWaitingQueriesSelector.java
*
lens-server/src/main/java/org/apache/lens/server/query/collect/IntersectingWaitingQueriesSelector.java
*
lens-server/src/test/java/org/apache/lens/server/query/collect/IntersectingWaitingQueriesSelectorTest.java
*
lens-server/src/main/java/org/apache/lens/server/query/QueryExecutionServiceImpl.java
*
lens-server/src/test/java/org/apache/lens/server/query/collect/UnioningWaitingQueriesSelectorTest.java
> Query remains in queue even when driver is free
> ------------------------------------------------
>
> Key: LENS-777
> URL: https://issues.apache.org/jira/browse/LENS-777
> Project: Apache Lens
> Issue Type: Bug
> Reporter: Arshad Matin
> Assignee: Akshay Goyal
> Fix For: 2.4
>
> Attachments: LENS-777.01.patch, LENS-777.02.patch
>
>
> Scenario:
> Config
> {noformat}
> <property>
> <name>driver.max.concurrent.launched.queries</name>
> <value>1</value>
> <description>Maximum queries which can be launched simultaneously on this
> driver. This should be equal to
> lens.driver.jdbc.pool.max.size. This configuration value is only useful
> when MaxConcurrentDriverQueriesConstraint
> is enabled by using
> org.apache.lens.server.api.query.constraint.MaxConcurrentDriverQueriesConstraintFactory
> as
> one of the factories in lens.driver.jdbc.query.constraint.factories
> property.</description>
> </property>
> <property>
> <name>lens.driver.jdbc.pool.max.size</name>
> <value>1</value>
> <description>Maximum number of concurrent connections allowed in
> pool</description>
> </property>
> {noformat}
> Launched 1st query with user U1
> Launched 2nd query with user U2
> Launched 3rd query with user U1
> Launched 4th query with user U2
> Query Status
> ==========
> Q1 -> Running
> Q2 -> Queued(queue number = 1)
> Q3 -> Queued(queue number = 2)
> Q4 -> Queued(queue number = 3)
> When Q1 completes, Query Status
> ==========================
> Q1 -> Successful
> Q2 -> Queued(queue number = 1)
> Q3 -> Running
> Q4 -> Queued(queue number = 2)
> When Q2 completes, Query Status
> ==========================
> Q1 -> Successful
> Q2 -> Queued(queue number = 1)
> Q3 -> Successful
> Q4 -> Queued(queue number = 2)
> user "U2" query will never get picked. Another query launched by user "U1"
> will be answered.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
