# Alpha nodes stuck in "opPredMove"

**URL:** <https://discuss.dgraph.io/t/alpha-nodes-stuck-in-oppredmove/18391>\
**Category:** Dgraph Cloud / Slash GraphQL\
**Created:** [March 16, 2023, 12:27pm UTC](https://discuss.dgraph.io/t/alpha-nodes-stuck-in-oppredmove/18391 "2023-03-16T12:27:42Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![zooney](https://avatars.discourse-cdn.com/v4/letter/z/a9adbd/32.png) [@zooney](https://discuss.dgraph.io/u/zooney)\
**Post date:** [March 16, 2023, 7:53pm UTC](https://discuss.dgraph.io/t/alpha-nodes-stuck-in-oppredmove/18391/3 "2023-03-16T19:53:27Z")

</div>

In the documentation it says that:

> Dgraph Zero tries to rebalance the cluster based on the disk usage in each group. If Zero detects an imbalance, it will try to move a predicate along with its indices to a group that has lower disk usage. This can make the predicate temporarily read-only. Queries for the predicate will still be serviced, but any mutations for the predicate will be rejected and should be retried after the move is finished.
> 
> Zero would continuously try to keep the amount of data on each server even, typically running this check on a 10-min frequency. Thus, each additional Dgraph Alpha instance would allow Zero to further split the predicates from groups and move them to the new node.

Is there a way to set this to a different frequency or to stop predicates moving all together and make it a manual process?

---

_[View the full topic](https://discuss.dgraph.io/t/alpha-nodes-stuck-in-oppredmove/18391)._