[DRILL-6255] Drillbit while sending control message to itself creates a connection instead of submitting locally

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.12.0
• Fix Version/s: 1.14.0
• Component/s: Execution - Flow
• Labels: ready-to-commit
• Assignee: Sorabh Hamirwasia
• Reporter: Sorabh Hamirwasia
• Reviewer: Arina Ielchiieva
• Created: 15/Mar/18 22:27
• Updated: 18/May/18 18:44
• Resolved: 18/May/18 18:44

Description

With the new shutdown feature introduced in 1.12, there is a state introduced in DrillbitEndpoint. Due to this the equality check happening here 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.

Issue Links

• links to: GitHub Pull Request #1253