drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-4979) Make dataport configurable
Date Wed, 09 Nov 2016 12:03:58 GMT

    [ https://issues.apache.org/jira/browse/DRILL-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650751#comment-15650751

ASF GitHub Bot commented on DRILL-4979:

GitHub user xhochy opened a pull request:


    DRILL-4979: Make port of the DataConnection configurable


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/xhochy/drill DRILL-4979

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #649
commit 277b14f552bb8cff001fd251bd3bc5303bf9e8b4
Author: Korn, Uwe <uwe.korn@blue-yonder.com>
Date:   2016-11-09T12:02:20Z

    DRILL-4979: Make port of the DataConnection configurable


> 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

View raw message