# Newly added storage nodes have disk usage at 98%

**URL:** <https://forums.foundationdb.org/t/newly-added-storage-nodes-have-disk-usage-at-98/2291>\
**Category:** Using FoundationDB\
**Created:** [August 12, 2020, 3:46pm UTC](https://forums.foundationdb.org/t/newly-added-storage-nodes-have-disk-usage-at-98/2291 "2020-08-12T15:46:02Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![ajbeamon](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/ajbeamon/32/13_2.png) [@ajbeamon](https://forums.foundationdb.org/u/ajbeamon)\
**Post date:** [August 14, 2020, 3:08pm UTC](https://forums.foundationdb.org/t/newly-added-storage-nodes-have-disk-usage-at-98/2291/15 "2020-08-14T15:08:42Z")

</div>

> [@mbhaskar](#):
>
> I think one of the fix was along the lines, what you suggested. IIRC, fix was a scheme when a server crosses a threshold, data distributor stops using teams with that server as destination. Evan would know details better.

Yes, this is one of the fixes I was talking about since 6.2.11, it avoids putting data on processes that are getting full and are also fuller than other processes.

---

_[View the full topic](https://forums.foundationdb.org/t/newly-added-storage-nodes-have-disk-usage-at-98/2291)._