How to configure a deployment use more disk resource?

[rockybean]

Hi,
As I know, we can boost cpu share by changing some settings as below.

Need some advice on cpu core number vs memory for ece allocator

In general we recommend trying to keep the cpu:mem ratio in the 1:8 range (that's a typical ratio you'll see in standard AWS hardware) and we have observed issues with smaller clusters not being able to load with 1:11 or worse (the temp fix is described below and there's a full fix coming in 2.2 or 2.3) There's a few workarounds: As you point out you can artificially restrain the allocator capacity .... this makes most sense if you have no control over how the capacity will be used, since in …

And ece use blk_io.weight to limit disk resource for container.

How does ece limit disk iops for es node?

Hi, As we know, docker provides capability to limit disk iops by using 'blkio-weight' parameter. I notice ece set different 'blkio-weight' for different size es node. What is the strategy behind this? Thanks!

I wonder if there is a similar setting for disk like cpu share setting to allow a deployment use more disk resource.

thanks!

[Alex_Piggott]

You can always use as much disk resource as available, the blk-weight only kicks in if the disk is over-provisioned to manage sharing between different instances on the same allocator

It uses the same weighting as the CPU (ie changing one cluster's CPU weight will also increase its IO weight as discussed here)

Alex