# Predicate Rebalances (Moves) Across Servers Cause Transactions to Abort **URL:** \ **Category:** Dgraph\ **Created:** [July 19, 2024, 9:43pm UTC](https://discuss.dgraph.io/t/predicate-rebalances-moves-across-servers-cause-transactions-to-abort/19452 "2024-07-19T21:43:29Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![rahst12](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/rahst12/32/2416_2.png) [@rahst12](https://discuss.dgraph.io/u/rahst12)\ **Post date:** [August 15, 2024, 11:13pm UTC](https://discuss.dgraph.io/t/predicate-rebalances-moves-across-servers-cause-transactions-to-abort/19452/2 "2024-08-15T23:13:28Z")
I found the answer my question reading through this post: > **[Alpha nodes stuck in "opPredMove"](https://discuss.dgraph.io/t/alpha-nodes-stuck-in-oppredmove/18391/3)** > > 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... ### Shard rebalancing 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. Reference: [Cluster Setup - Dgraph](https://dgraph.io/docs/deploy/cluster-setup/#shard-rebalancing) --- _[View the full topic](https://discuss.dgraph.io/t/predicate-rebalances-moves-across-servers-cause-transactions-to-abort/19452)._