# Node-Red HA with docker swarm and glusterfs

**URL:** <https://discourse.nodered.org/t/node-red-ha-with-docker-swarm-and-glusterfs/75484>\
**Category:** General\
**Tags:** docker\
**Created:** [20 February 2023 17:07 UTC](https://discourse.nodered.org/t/node-red-ha-with-docker-swarm-and-glusterfs/75484 "2023-02-20T17:07:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![basanet](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/basanet/32/76438_2.png) [@basanet](https://discourse.nodered.org/u/basanet)\
**Post date:** [20 February 2023 17:07 UTC](https://discourse.nodered.org/t/node-red-ha-with-docker-swarm-and-glusterfs/75484/1 "2023-02-20T17:07:27Z")

</div>

Hi,

I'm trying to achieve a highly available node-red cluster with docker swarm and glusterfs.

Currently I have 3 manager nodes with node-red containers installed.

All nodes access the same gluster replicated folder.

When I change the flow in 1 node, I receive the notification on the other nodes that the flows have been changed.

How can I programmatically reload the flows.json file on the other nodes, whenever the file changes?

or is there a better solution for my approach?

My goal is to create a HA Node-Red cluster, which is resilient to any HW/SW failure and when I make changes to the flows, all the other nodes will apply them as soon as they receive it.

Many thanks for any advise on this.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [21 April 2023 17:07 UTC](https://discourse.nodered.org/t/node-red-ha-with-docker-swarm-and-glusterfs/75484/2 "2023-04-21T17:07:57Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.