Is it potential to have an exclusion listing for file varieties (possibly even particular recordsdata) in order that they wont attempt to sync with the secondary nodes? I’ve appeared on the DRBD configuration file and can’t discover something about it. If not is there one other master->slave syncing system that enables for exclusions?
Why I ask:
Attempting to maneuver from a single server to a cluster behind a load-balancer infrastructure. I wish to hold the servers operational/config recordsdata in sync. There are log recordsdata which are written in the identical directories as their corresponding operational/config recordsdata.
When grasp server (major) has related recordsdata up to date, slave (secondary) server recordsdata are synced.
I do know I can restructure the code however I would love to keep away from that.
Probably Related Info:
AWS ec2 servers
AWS Load Balancer
AWS NFS (EFS) was tried however efficiency hit was too massive.
Couldn’t get Jenkins to perform the purpose both.
Fascinated with organising a Git Repo for the grasp, cloning the repo on the slaves, after which including triggers each time commits are made. Is there no higher resolution? Haven’t absolutely checked out Puppet may that be an choice? Perhaps Corosync? If you happen to can level me to good use documentation as properly that may be nice.