# Should Scylla manager be run per-region, or one manager instance for a multi region cluster?

**URL:** <https://forum.scylladb.com/t/should-scylla-manager-be-run-per-region-or-one-manager-instance-for-a-multi-region-cluster/546>\
**Category:** ScyllaDB\
**Tags:** open-source, scylla-manager\
**Created:** [May 14, 2023, 9:28pm UTC](https://forum.scylladb.com/t/should-scylla-manager-be-run-per-region-or-one-manager-instance-for-a-multi-region-cluster/546 "2023-05-14T21:28:32Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![danthegoodman1](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/danthegoodman1/32/314_2.png) [@danthegoodman1](https://forum.scylladb.com/u/danthegoodman1)\
**Post date:** [May 14, 2023, 9:28pm UTC](https://forum.scylladb.com/t/should-scylla-manager-be-run-per-region-or-one-manager-instance-for-a-multi-region-cluster/546/1 "2023-05-14T21:28:32Z")

</div>

Since the open source version is limited to 5 instances, could I in theory have 5 instances per region, and each region has a dedicated scylla manager?

I suspect that this is not advised, but in theory will this work or break the cluster? I could stagger their repairs so it’s never concurrent

---

<div class="post-metadata">

**Author:** ![danthegoodman1](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/danthegoodman1/32/314_2.png) [@danthegoodman1](https://forum.scylladb.com/u/danthegoodman1)\
**Post date:** [May 14, 2023, 9:29pm UTC](https://forum.scylladb.com/t/should-scylla-manager-be-run-per-region-or-one-manager-instance-for-a-multi-region-cluster/546/2 "2023-05-14T21:29:04Z")

</div>

Pining @Guy since he asked 🙂

---

<div class="post-metadata">

**Author:** ![tzach](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/tzach/32/172_2.png) [@tzach](https://forum.scylladb.com/u/tzach)\
**Post date:** [May 15, 2023, 7:43am UTC](https://forum.scylladb.com/t/should-scylla-manager-be-run-per-region-or-one-manager-instance-for-a-multi-region-cluster/546/3 "2023-05-15T07:43:47Z")

</div>

Technically it might work, but not advice.  
You will need to ensure Managers tasks do not overlap and are limited per DC. By default, Manager tasks, like repair, are cluster wide.

---

<div class="post-metadata">

**Author:** ![danthegoodman1](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/danthegoodman1/32/314_2.png) [@danthegoodman1](https://forum.scylladb.com/u/danthegoodman1)\
**Post date:** [May 16, 2023, 2:26pm UTC](https://forum.scylladb.com/t/should-scylla-manager-be-run-per-region-or-one-manager-instance-for-a-multi-region-cluster/546/4 "2023-05-16T14:26:41Z")

</div>

How would you ensure that they are limited to a single region?

---

<div class="post-metadata">

**Author:** ![danthegoodman1](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/danthegoodman1/32/314_2.png) [@danthegoodman1](https://forum.scylladb.com/u/danthegoodman1)\
**Post date:** [May 16, 2023, 2:27pm UTC](https://forum.scylladb.com/t/should-scylla-manager-be-run-per-region-or-one-manager-instance-for-a-multi-region-cluster/546/5 "2023-05-16T14:27:58Z")

</div>

Or I guess that’s a silly question, since it seems like the agents call back to a manager instead, so it would just be a matter of pointing an agent to the correct manager.

---

<div class="post-metadata">

**Author:** ![danthegoodman1](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/danthegoodman1/32/314_2.png) [@danthegoodman1](https://forum.scylladb.com/u/danthegoodman1)\
**Post date:** [May 16, 2023, 2:33pm UTC](https://forum.scylladb.com/t/should-scylla-manager-be-run-per-region-or-one-manager-instance-for-a-multi-region-cluster/546/6 "2023-05-16T14:33:34Z")

</div>

And for reference, I am using a somewhat unusual use case where I want many small nodes in many regions to reduce latency for lookups, so I would be running into the limit of requiring the enterprise license to have scylla manager handle repairs automatically. All these nodes will be the minimum size since each node is not hit very frequently, but I want all data in all regions.

Would there be another recommended way to run this in so many regions without doing manual repairs?

---

<div class="post-metadata">

**Author:** ![tzach](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/tzach/32/172_2.png) [@tzach](https://forum.scylladb.com/u/tzach)\
**Post date:** [May 16, 2023, 5:54pm UTC](https://forum.scylladb.com/t/should-scylla-manager-be-run-per-region-or-one-manager-instance-for-a-multi-region-cluster/546/7 "2023-05-16T17:54:50Z")

</div>

I’m not aware of other tools for running recurrent repairs on ScyllaDB.  
Note that repair works between _all_ nodes, including nodes from different data centers.

---

<div class="post-metadata">

**Author:** ![danthegoodman1](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/danthegoodman1/32/314_2.png) [@danthegoodman1](https://forum.scylladb.com/u/danthegoodman1)\
**Post date:** [May 16, 2023, 6:44pm UTC](https://forum.scylladb.com/t/should-scylla-manager-be-run-per-region-or-one-manager-instance-for-a-multi-region-cluster/546/8 "2023-05-16T18:44:07Z")

</div>

Understood thanks! To clarify you are confirming that running a `nodetool repair` will repair on all nodes across the cluster in that single command? I.e. I only need to run that once for the whole cluster manually, not on each node? My understanding was that this is only per-node.

---

<div class="post-metadata">

**Author:** ![tzach](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/tzach/32/172_2.png) [@tzach](https://forum.scylladb.com/u/tzach)\
**Post date:** [May 16, 2023, 7:09pm UTC](https://forum.scylladb.com/t/should-scylla-manager-be-run-per-region-or-one-manager-instance-for-a-multi-region-cluster/546/9 "2023-05-16T19:09:28Z")

</div>

`nodetool repair` sync between the node you are running the command from, and its replicas.  
It does not repair all the nodes.

> **[Nodetool repair | ScyllaDB Docs](https://docs.scylladb.com/stable/operating-scylla/nodetool-commands/repair.html)**
>
> ScyllaDB is an Apache Cassandra-compatible NoSQL data store that can handle 1 million transactions per second on a single server.
