[
https://issues.apache.org/jira/browse/DRILL-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651993#comment-15651993
]
ASF GitHub Bot commented on DRILL-4979:
---------------------------------------
Github user xhochy commented on the issue:
https://github.com/apache/drill/pull/649
No, this patch is actually functioning as the data port is already included
in the probuf:
https://github.com/apache/drill/blob/master/protocol/src/main/protobuf/Coordination.proto#L11
The `+1 logic` is only used in the initialization code for the port.
Also I did a test run with 5 drillbits and random dataports assigned to
them. They each were able to talk to them showing that the correct ports are
communicated.
> Make dataport configurable
> --------------------------
>
> Key: DRILL-4979
> URL: https://issues.apache.org/jira/browse/DRILL-4979
> Project: Apache Drill
> Issue Type: New Feature
> Components: Server
> Affects Versions: 1.8.0
> Environment: Scheduling drillbits with Apache Mesos+Aurora
> Reporter: Uwe L. Korn
>
> Currently the dataport of a Drillbit is fixed to +1 on the control port. In a
> dynamic execution environment like Apache Mesos+Aurora, each port is
> allocated by the scheduler and then passed on to the application process.
> There is no possibility or guarantee to allocate two consecutive ports.
> Therefore, to run Drill in this environment, the dataport of the drillbit
> also needs to configurable by the scheduler.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
