# Bug report - node went out of sync when a remote farmer (with all finished plots) replotted

**URL:** <https://forum.autonomys.xyz/t/bug-report-node-went-out-of-sync-when-a-remote-farmer-with-all-finished-plots-replotted/3189>\
**Category:** Support\
**Created:** [April 15, 2024, 3:35am UTC](https://forum.autonomys.xyz/t/bug-report-node-went-out-of-sync-when-a-remote-farmer-with-all-finished-plots-replotted/3189 "2024-04-15T03:35:12Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\
**Post date:** [April 15, 2024, 2:29pm UTC](https://forum.autonomys.xyz/t/bug-report-node-went-out-of-sync-when-a-remote-farmer-with-all-finished-plots-replotted/3189/7 "2024-04-15T14:29:26Z")

</div>

This seems to be related to large number of farmers connected to the same node. It wasn’t really designed for this and there are likely bottlenecks there that blow up when new segment is archived. I’m not planning to address this before we do Substrate upgrade (likely next release) and then [farming cluster](https://forum.autonomys.xyz/t/farming-cluster/3041) that should remove the need to have many connections to the node in the first place in addition to other improvements .

---

_[View the full topic](https://forum.autonomys.xyz/t/bug-report-node-went-out-of-sync-when-a-remote-farmer-with-all-finished-plots-replotted/3189)._
