[ https://issues.apache.org/jira/browse/DRILL-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614793#comment-15614793 ]
Uwe L. Korn commented on DRILL-4979: ------------------------------------ Implementation-wise it seems like the only point where the {{+1}} is actually hardcoded is in {{exec/java-exec/src/main/java/org/apache/drill/exec/rpc/data/DataConnectionCreator.java:62}}, i.e. {{int port = server.bind(partialEndpoint.getControlPort() + 1, allowPortHunting)}}. Therefore a fix for this could be to introduce a new configuration option {{drill.exec.rpc.bit.server.dataport}} and use this if set, otherwise default back to {{controlport + 1}}. > 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)