Unexpected High Disk Utilization on All Frozen Nodes After Adding New Node in Elastic Cloud

We’re using frozen tier in Elastic Cloud with searchable snapshots (fully mounted).
Initially had 3 frozen nodes (~99.4% used disk capacity), and hit the 9000 shard limit.
Added a 4th frozen node to increase capacity (12,000 shards total).

After the node joined, shards rebalanced equally on all 4 frozen nodes, but all 4 nodes now show ~99.4% disk usage—including the new one, almost immediately.

Only ~120 shards were pending before scale-up.
Is this high disk usage due to blob cache behavior, or something else we should investigate?

Looking to understand if this is expected in Elastic Cloud or a potential misconfiguration.

Thanks!

Hello @SourabhK1

Welcome to the community.

As per this URL you can check the defaults set on your environment generally it is 90% default. So when you add a new frozen node the disk space will be shown by default 90% occupied :

Thanks!!

@Tortoise Thank you. This is something relevant.

1 Like