# Dgraph zero rpc timeout when moving \_predicate\_ between groups

**URL:** <https://discuss.dgraph.io/t/dgraph-zero-rpc-timeout-when-moving-predicate-between-groups/2468>\
**Category:** Dgraph\
**Created:** [April 15, 2018, 10:10pm UTC](https://discuss.dgraph.io/t/dgraph-zero-rpc-timeout-when-moving-predicate-between-groups/2468 "2018-04-15T22:10:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![coolguru](https://avatars.discourse-cdn.com/v4/letter/c/7cd45c/32.png) [@coolguru](https://discuss.dgraph.io/u/coolguru)\
**Post date:** [April 15, 2018, 10:10pm UTC](https://discuss.dgraph.io/t/dgraph-zero-rpc-timeout-when-moving-predicate-between-groups/2468/1 "2018-04-15T22:10:46Z")

</div>

`Going to move predicate: [_predicate_], size: [7.3 MB] from group 2 to 1`

Our 3 replica HA cluster is stuck moving `_predicate_` between groups. Any recommendation on how to handle `_predicate_` to avoid moving groups?

---

<div class="post-metadata">

**Author:** ![pawan](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/pawan/32/1946_2.png) [@pawan](https://discuss.dgraph.io/u/pawan)\
**Post date:** [April 16, 2018, 2:28am UTC](https://discuss.dgraph.io/t/dgraph-zero-rpc-timeout-when-moving-predicate-between-groups/2468/2 "2018-04-16T02:28:13Z")

</div>

Is the cluster deployed using Kubernetes? Can you share full logs for Zero and all the servers that would help us debug this issue? You can avoid all predicate move if you want by setting a very high value for `--rebalance_interval` flag in `dgraph zero`.

---

<div class="post-metadata">

**Author:** ![coolguru](https://avatars.discourse-cdn.com/v4/letter/c/7cd45c/32.png) [@coolguru](https://discuss.dgraph.io/u/coolguru)\
**Post date:** [April 17, 2018, 5:46pm UTC](https://discuss.dgraph.io/t/dgraph-zero-rpc-timeout-when-moving-predicate-between-groups/2468/3 "2018-04-17T17:46:57Z")

</div>

Unfortunately, I’d lost the logs from the servers. But after moving to master tag docker image, things have been stable and we haven’t been able to reproduced this issue. I’ll update this post if we’re able to reproduce this again. Thanks again!
