You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Mitchel Labonte (JIRA)" <ji...@apache.org> on 2017/11/28 14:08:01 UTC

[jira] [Created] (DRILL-5994) Cannot start web server on a machine with more than 200 cores

Mitchel Labonte created DRILL-5994:
--------------------------------------

             Summary: Cannot start web server on a machine with more than 200 cores
                 Key: DRILL-5994
                 URL: https://issues.apache.org/jira/browse/DRILL-5994
             Project: Apache Drill
          Issue Type: Bug
            Reporter: Mitchel Labonte
            Priority: Minor


If the WebServer is launched on a machine that has more than 200 cores, you get the following stack trace:

{noformat}
Exception in thread "main" org.apache.drill.exec.exception.DrillStartupException: Failure during initial startup of Drillbit:
at org.apache.drill.exec.server.Drillbit.start(Drillbit.java:313)
at org.apache.drill.exec.server.Drillbit.start(Drillbit.java:289)
at org.apache.drill.exec.server.Drillbit.start(Drillbit.java:285)
Caused by: java.lang.IllegalStateException: Insufficient max threads in ThreadPool: max=200 < needed=206
at org.eclipse.jetty.server.Server.doStart(Server.java:321)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.drill.exec.server.rest.WebServer.start(WebServer.java:197)
at org.eclipse.drill.exec.server.Drillbit.run(Drillbit.java:140)
at org.eclipse.drill.exec.server.Drillbit.start(Drillbit.java:309)
... 2 more
{noformat}

The cause of this is that in the WebServer start method, a Server instance is created with the default constructor, which initializes a QueuedThreadPool with a default maxThreads value of 200, and there is no way to configure this value.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)