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

ASF GitHub Bot commented on DRILL-6693:
---------------------------------------

arina-ielchiieva commented on a change in pull request #1440: DRILL-6693: When 
a query is started from Drill Web Console, the UI becomes inaccessible
URL: https://github.com/apache/drill/pull/1440#discussion_r212288493
 
 

 ##########
 File path: 
exec/java-exec/src/main/java/org/apache/drill/exec/server/rest/WebServer.java
 ##########
 @@ -136,7 +136,8 @@ public void start() throws Exception {
     final boolean portHunt = config.getBoolean(ExecConstants.HTTP_PORT_HUNT);
     final int acceptors = 
config.getInt(ExecConstants.HTTP_JETTY_SERVER_ACCEPTORS);
     final int selectors = 
config.getInt(ExecConstants.HTTP_JETTY_SERVER_SELECTORS);
-    final QueuedThreadPool threadPool = new QueuedThreadPool(2, 2, 60000);
+    final int handlers = 
config.getInt(ExecConstants.HTTP_JETTY_SERVER_HANDLERS);
+    final QueuedThreadPool threadPool = new QueuedThreadPool(2, 2);
 
 Review comment:
   Given another thought to this since we are hard-coding number of threads as 
well, no need to make idle time configurable. Please disregard the question.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> When a query is started from Drill Web Console, the UI becomes inaccessible 
> until the query is completed
> --------------------------------------------------------------------------------------------------------
>
>                 Key: DRILL-6693
>                 URL: https://issues.apache.org/jira/browse/DRILL-6693
>             Project: Apache Drill
>          Issue Type: Bug
>    Affects Versions: 1.13.0, 1.14.0
>            Reporter: Anton Gozhiy
>            Assignee: Vlad Rozov
>            Priority: Major
>             Fix For: 1.15.0
>
>         Attachments: jstack.txt
>
>
> *Steps:*
>  # From Web UI, run the following query:
> {noformat}
> select * 
> from (
>     select employee_id, full_name, first_name, last_name, position_id, 
> position_title, store_id, department_id, birth_date, hire_date, salary, 
> supervisor_id, education_level, marital_status, gender, management_role 
>     from cp.`employee.json` 
>     union
>     select employee_id, full_name, first_name, last_name, position_id, 
> position_title, store_id, department_id, birth_date, hire_date, salary, 
> supervisor_id, education_level, marital_status, gender, management_role 
>     from cp.`employee.json` 
>     union
>     select employee_id, full_name, first_name, last_name, position_id, 
> position_title, store_id, department_id, birth_date, hire_date, salary, 
> supervisor_id, education_level, marital_status, gender, management_role
>     from cp.`employee.json`)
> where last_name = 'Blumberg'
> {noformat}
>  # While query is running, try open the Profiles page (or any other). If It 
> completes too fast, add some unions to the query above.
> *Expected result:*
>  Profiles page should be opened. The running query should be listed.
> *Actual result:*
>  The Web UI hangs until the query completes.
> *Notes:*
> - If you open another tab with Web Console, it also stuck when the query is 
> running.
> - If the query is started from sqlline, everything is fine.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to