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-4131: Move RPC allocators under Drill's ...
Date Mon, 18 Jan 2016 19:00:25 GMT
Github user jacques-n commented on a diff in the pull request:

    https://github.com/apache/drill/pull/327#discussion_r50033210
  
    --- Diff: exec/java-exec/src/main/java/org/apache/drill/exec/service/ServiceEngine.java
---
    @@ -56,22 +60,83 @@
       private final DrillConfig config;
       boolean useIP = false;
       private final boolean allowPortHunting;
    +  private final BufferAllocator userAllocator;
    +  private final BufferAllocator controlAllocator;
    +  private final BufferAllocator dataAllocator;
    +
     
       public ServiceEngine(ControlMessageHandler controlMessageHandler, UserWorker userWorker,
BootStrapContext context,
           WorkEventBus workBus, WorkerBee bee, boolean allowPortHunting) throws DrillbitStartupException
{
    +    userAllocator = newAllocator(context, "rpc:user", "drill.exec.rpc.user.server.memory.reservation",
    +        "drill.exec.rpc.user.server.memory.maximum");
    +    controlAllocator = newAllocator(context, "rpc:bit-control",
    +        "drill.exec.rpc.bit.server.memory.control.reservation", "drill.exec.rpc.bit.server.memory.control.maximum");
    +    dataAllocator = newAllocator(context, "rpc:bit-control",
    --- End diff --
    
    nice catch


---
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.
---

Mime
View raw message