ppetru/alo-cluster
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Replace c3 (failed) with zippy for clusterfs.

Browse Source 
Use IPs for mounting glusterfs, prevents boot mount failing before networking comes up.
This commit is contained in:
Petru
2024-07-26 08:20:17 +01:00
parent f2ef036bf4
commit b84a90d35a
2 changed files with 9 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
common/glusterfs-client.nix
View File

@@ -3,10 +3,10 @@
environment.systemPackages = [ pkgs.glusterfs ];
fileSystems."/data/compute" = {
device = "c1:/compute";
device = "192.168.1.71:/compute";
fsType = "glusterfs";
options = [
"backup-volfile-servers=c2:c3"
"backup-volfile-servers=192.168.1.72:192.168.1.2"
"_netdev"
];
};

7
stateful-commands.txt
View File

@@ -11,3 +11,10 @@ mysql credentials
postgres credentials
* Put secrets/postgres_password into a Nomad var named secrets/postgresql.postgres_password
adding a new gluster node to the compute volume, with c3 having failed:
(instructions from https://icicimov.github.io/blog/high-availability/Replacing-GlusterFS-failed-node/)
* zippy: sudo mkdir /persist/glusterfs/compute -p
* c1: gluster peer probe 192.168.1.2 (by IP because zippy resolved to a tailscale address)
* c1: gluster volume replace-brick compute c3:/persist/glusterfs/compute/brick1 192.168.1.2:/persist/glusterfs/compute/brick1 commit force
* c1: gluster volume heal compute full