Force push storage node replication?
-
How can I force push or force sync image replication across storage nodes?
-
@tesparza This should happen automatically. If it’s not, you have some sort of configuration problem. There’s a replication log you can look at in the web UI. Check that for errors.
Also, there’s this article on the location plugin. While this is meant to cover location plugin functionality, it also explains default functionality pretty well. https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin
-
@wayne-workman What happen is that one of the nodes used storage was not matching. All were at 20.66gb, except one that was 32gig. So theres no way for force sync?
-
@tesparza The sync is constantly running. If they are still not in sync, something is wrong and you need to look at the logs on the master node to find out why…
-
@sebastian-roth I think I found the issue, some people were imaging before the image finished replicating and it got stuck. Is that possible?
2021-08-25 02:29:53 /images/Win10MasterLegacy/d1p2.img -> ftp://fogproject@10.155.57.30/%2Fimages/Win10MasterLegacy/d1p2.img 0-9593724970 360.8K/s [08-25-21 7:37:02 am] Task started2021-08-25 02:37:02 /images/Win10MasterLegacy/d1.fixed_size_partitions -> ftp://fogproject@10.155.57.30/%2Fimages/Win10MasterLegacy/d1.fixed_size_partitions 0-4 50b/s 2021-08-25 02:37:02 /images/Win10MasterLegacy/d1.original.fstypes -> ftp://fogproject@10.155.57.30/%2Fimages/Win10MasterLegacy/d1.original.fstypes 0-15 169b/s 2021-08-25 02:37:02 /images/Win10MasterLegacy/d1.original.swapuuids -> ftp://fogproject@10.155.57.30/%2Fimages/Win10MasterLegacy/d1.original.swapuuids 0-0 2021-08-25 02:37:02 /images/Win10MasterLegacy/d1.partitions -> ftp://fogproject@10.155.57.30/%2Fimages/Win10MasterLegacy/d1.partitions 0-266 2.4K/s 2021-08-25 02:37:03 /images/Win10MasterLegacy/d1p3.img -> ftp://fogproject@10.155.57.30/%2Fimages/Win10MasterLegacy/d1p3.img 0-151346 230.2K/s 2021-08-25 02:37:03 /images/Win10MasterLegacy/d1.minimum.partitions -> ftp://fogproject@10.155.57.30/%2Fimages/Win10MasterLegacy/d1.minimum.partitions 0-266 244b/s 2021-08-25 02:37:05 /images/Win10MasterLegacy/d1.mbr -> ftp://fogproject@10.155.57.30/%2Fimages/Win10MasterLegacy/d1.mbr 0-1048576 331.7K/s 2021-08-25 02:37:44 /images/Win10MasterLegacy/d1p1.img -> ftp://fogproject@10.155.57.30/%2Fimages/Win10MasterLegacy/d1p1.img 0-9297590 216.7K/s [08-25-21 4:19:37 pm] Task started[08-25-21 6:00:28 pm] Task started[08-25-21 8:40:20 pm] Task started -
@tesparza said in Force push storage node replication?:
some people were imaging before the image finished replicating and it got stuck
Why do you think it’s stuck? I don’t think I have ever seen replication to go stuck.
Would you mind uploading the full
fogreplication.logand posting a link here? I am pretty sure there is something else going on. -
@sebastian-roth said in Force push storage node replication?:
ere is something else going on.
Everything is back synced, What i did was delete the image on the storage node and then it resynced by itself. What had happen was our ISP went into the campus to replace some of their equipment. So it went offline mid transfer. But the me upload the log anyways. This is for today so I dont see any errors. Working fine now.
-
@tesparza Yeah, todays log is full of “No need to sync …” messages. Seems all fine.
The replication process does check file size and checksum of the files on master node and each storage node. In case they don’t match the replication deletes the file on the storage node and resyncs that file over. So in general there shouldn’t be a case where replication is “stuck” with one file not in sync even if it was broken half way.
