Native, fast, reliable and well tested Linux FS monitor subsystem. using BSM API (with or without a prefetcher thread) Īnd any of this methods is bad (in it's own way), see the excerpt from the.9 - FreeBSD supportįreeBSD doesn't support inotify, so there're 3.5 ways to use clsync on it: You can easily use it to prevent sync-loops for bi-directional syncing. UPD: I've added option "-modification-signature" that helps to prevent syncing file, that is not changed. by scripts that chooses which variant of container to save.Įxample of the script is just a script that calls "find" on both sides toĭetermine which side has the latest changes :).Split-brain, that can be solved two ways: Starts and stop the process when containers stops. It's just need to start clsync-process when container SoĪndrew Savchenko proposed to run one clsync-instance per container. So I've started to write code forīi-directional syncing, however it's no time to complete it :(. " /srv/nodes//containers/")Īnd syncing every directory only in one direction. Well, in this case I with my colleagues were using separate directories forĮvery node of cluster (e.g. ![]() Get sync-loop [file-update on A causes file-update on B causes file-update Just run clsync to sync containers to neighboring node on both of them, you'll In this case you have to sync containers in both directions. LXC and trying to replicate containers between two servers (to make failover However let's solve next hypothetical problem. I've started to implement support of bi-directional syncing with using R /dev/stdin -Mdirect -r1 -ignore-failures -t1 -w1 -Smake - build Printf "%s\n" " f.c$" "-f" | clsync -have-recursive-sync -W. Some distributions already have clsync supported in the main repo: UPD: Starting with kernels 5.1 we will be able to use fanotify for all events ) 4 - Installing "inotify", leaving the code for "fanotify" in the safety. The program, like "directory creation" or "file deletion". However I encountered the problem, thatįanotify was unable to catch some important events at the moment of writing It's said that fanotify is much better than inotify. Incron/csync2/etc in our HPC-clusters for syncing /etc/įiles and running post-scripts. So there it is :)Īlso clsync had been used for some other tiny tasks, like to replace "lsyncd" to realize that we could've already write a new tool Long story short: "lsyncd" - is a good and useful utility, just did notįit to our needs well enough.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |