You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Deneche A. Hakim (JIRA)" <ji...@apache.org> on 2016/05/15 15:04:12 UTC

[jira] [Created] (DRILL-4676) Foreman.moveToState can block forever if called by the foreman thread while the query is still being setup

Deneche A. Hakim created DRILL-4676:
---------------------------------------

             Summary: Foreman.moveToState can block forever if called by the foreman thread while the query is still being setup
                 Key: DRILL-4676
                 URL: https://issues.apache.org/jira/browse/DRILL-4676
             Project: Apache Drill
          Issue Type: Bug
          Components: Execution - Flow
    Affects Versions: 1.6.0
            Reporter: Deneche A. Hakim
            Assignee: Deneche A. Hakim
             Fix For: 1.7.0


When the query is being setup, foreman has a special CountDownLatch that blocks rpc threads from delivering external events, this latch is unblocked at the end of the query setup.
In some cases though, when the foreman is submitting remote fragments, a failure in RpcBus.send() causes an exception to be thrown that is reported to 
Foreman.FragmentSubmitListener and blocks in the CountDownLatch. This causes the foreman thread to block forever, and can rpc threads to be blocked too.
This seems to happen more frequently at a high concurrency load, and also can prevent clients from connecting to the Drillbits.



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