drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jacques-n <...@git.apache.org>
Subject [GitHub] drill pull request: Drill-3242: Offload RPC threads
Date Mon, 02 Nov 2015 18:50:14 GMT
GitHub user jacques-n opened a pull request:


    Drill-3242: Offload RPC threads


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

    $ git pull https://github.com/jacques-n/drill DRILL-3242v2

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 #229
commit 839f8dac2e2d0479a1552701a5274ebe8416fea6
Author: Chris Westin <cwestin@yahoo.com>
Date:   2015-05-22T21:17:41Z

    SerializedExecutor sketch for consideration.
    Based on the EventProcessor, but recast as an Executor that accepts Runnables.
    The idea would be to use this on RPC reception points to immediately hand off
    work. Each Fragment would have a SerializedExecutor associated with it, serving
    as a queue to deliver events to when the RPC thread receives them.

commit e7db9dcacbc39c4797de1aa29b119a7428451dea
Author: Jacques Nadeau <jacques@apache.org>
Date:   2015-05-25T05:01:49Z

    DRILL-3242: Update RPC layer so that requests and response are managed on a secondary
    - Create a separate serialized executor for fragment receiverFinished events.
    - Update serialized executor to pool object creation.
    - Ensure that FragmentExecutor acceptExternalEvents countdown occurs when only execution
is cancellation.


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message