You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@heron.apache.org by GitBox <gi...@apache.org> on 2020/04/02 03:05:56 UTC

[GitHub] [incubator-heron] dttlgotv opened a new issue #3504: terrible resource is needed when submitting to aurora

dttlgotv opened a new issue #3504: terrible resource is needed when submitting to aurora
URL: https://github.com/apache/incubator-heron/issues/3504
 
 
   I write a simple example to test resource requirement to submit to aurora. It is very terrible that too more resource is needed. Please check below:
   
   my example:
    builder.newSource(() -> ThreadLocalRandom.current().nextInt(100))
           .setName("random-sentences-source");
      
             Config config = Config.newBuilder()
                         .setNumContainers(1)
                         .setPerContainerCpu(2)
                         .setPerContainerRamInGigabytes(3)
                         .build();
   
   When I submit this topo to aurora, 4.5 cpu and 6.3G memory are allocated to this topology. It seems that Tmaster used 2.5G cpu and 3.3G memory.
   
   My question is how to limit tmaster resource requirement. It seems that Tmaster task using more resource.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [incubator-heron] dttlgotv commented on issue #3504: terrible resource is needed when submitting to aurora

Posted by GitBox <gi...@apache.org>.
dttlgotv commented on issue #3504: terrible resource is needed when submitting to aurora
URL: https://github.com/apache/incubator-heron/issues/3504#issuecomment-607649211
 
 
   > In aurora, all containers need to have the same size, and container 0 is mainly for tmaster. Therefore the key is to keep the container size under control. In your example, your cpu and memory usage could be lower if you have 2 containers and 1 core/1.5G per container.
   
   Let me try, thanks a lot

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [incubator-heron] nwangtw commented on issue #3504: terrible resource is needed when submitting to aurora

Posted by GitBox <gi...@apache.org>.
nwangtw commented on issue #3504: terrible resource is needed when submitting to aurora
URL: https://github.com/apache/incubator-heron/issues/3504#issuecomment-607623734
 
 
   In aurora, all containers need to have the same size, and container 0 is mainly for tmaster. Therefore the key is to keep the container size under control. In your example, your cpu and memory usage could be lower if you have 2 containers and 1 core/1.5G per container.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services