You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Sorabh Hamirwasia (JIRA)" <ji...@apache.org> on 2018/03/15 22:28:00 UTC
[jira] [Created] (DRILL-6255) Drillbit while sending control
message to itself creates a connection instead of submitting locally
Sorabh Hamirwasia created DRILL-6255:
----------------------------------------
Summary: Drillbit while sending control message to itself creates a connection instead of submitting locally
Key: DRILL-6255
URL: https://issues.apache.org/jira/browse/DRILL-6255
Project: Apache Drill
Issue Type: Bug
Components: Execution - Flow
Affects Versions: 1.12.0
Reporter: Sorabh Hamirwasia
Assignee: Sorabh Hamirwasia
Fix For: 1.14.0
With the new shutdown feature introduced in 1.12, there is a state introduced in DrillbitEndpoint. Due to this the equality check happening [here|https://github.com/apache/drill/blob/master/exec/java-exec/src/main/java/org/apache/drill/exec/work/foreman/FragmentsRunner.java#L256] will result in false and hence the fragments supposed to be scheduled on Foreman will be treated as remote fragments and a connection will be created to schedule it. The equality check is false because localEndpoint state is STARTUP whereas state in assigned Drillbit is ONLINE.
I guess now we should update the equality check to verify just for address and control port to be same between assigned and local Drillbit endpoint. A test can be added for this based on _sys.memory_ table since that guarantees scheduling minor fragments on each Drillbit node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)