Difference between revisions of "Gluster"
Jump to navigation
Jump to search
Michael.mast (talk | contribs) (Created page with "==AWS Amazon Linux== I had moved the NFS backend for several services from EFS to an instance running NFS. This was much faster than EFS, but now my data was on a single insta...") |
Michael.mast (talk | contribs) |
||
| Line 1: | Line 1: | ||
==AWS Amazon Linux== | ==AWS Amazon Linux== | ||
| − | I had moved the NFS backend for several services from EFS to an instance running NFS. This was much faster than EFS, but now my data was on a single instance. A new critical app was being deployed and I needed redundancy. Previously played with gluster many years ago and decided to give it a shot. I wanted to keep the costs low so this will be a two node data and one node arbiter setup. The instances used are t3a.large for the data and t3a.small for the arbiter, all running Amazon Linux since CentOS is no longer viable. | + | I had moved the NFS backend for several services from EFS to an instance running NFS. This was much faster than EFS, but now my data was on a single instance. A new critical app was being deployed and I needed redundancy. Previously played with gluster many years ago and decided to give it a shot. I wanted to keep the costs low so this will be a two node data and one node arbiter setup. The instances used are t3a.large for the data and t3a.small for the arbiter, all running Amazon Linux since CentOS is no longer viable. Data nodes will have 200GB SSD storage. |
<pre> | <pre> | ||
sudo yum upgrade -y | sudo yum upgrade -y | ||
| + | sudo pvcreate /dev/nvme1n1 | ||
| + | sudo vgcreate data /dev/nvme1n1 | ||
| + | sudo lvcreate --size 195G --name gluster data | ||
| + | sudo mkfs.ext4 /dev/mapper/data-gluster | ||
| + | sudo mkdir /mnt/data | ||
</pre> | </pre> | ||
Revision as of 08:34, 15 December 2020
AWS Amazon Linux
I had moved the NFS backend for several services from EFS to an instance running NFS. This was much faster than EFS, but now my data was on a single instance. A new critical app was being deployed and I needed redundancy. Previously played with gluster many years ago and decided to give it a shot. I wanted to keep the costs low so this will be a two node data and one node arbiter setup. The instances used are t3a.large for the data and t3a.small for the arbiter, all running Amazon Linux since CentOS is no longer viable. Data nodes will have 200GB SSD storage.
sudo yum upgrade -y sudo pvcreate /dev/nvme1n1 sudo vgcreate data /dev/nvme1n1 sudo lvcreate --size 195G --name gluster data sudo mkfs.ext4 /dev/mapper/data-gluster sudo mkdir /mnt/data
