[Gluster-users] health monitoring of replicated volume

[Deyan Chepishev]

Hello,

My main idea is that currently no one can tell you if the data is 
consistent on all nodes, for example very simple case:

2 replicated nodes, node1 and node2

I reboot node1 and during this time, someone writes a file which will be 
written on node2. At this time you have out of sync replication.

When node1 comes back up in a few minutes, there is no way to know if 
this node is with consistent data or not. Some people suggest to run ls 
-lR but you have to agree that this is not applicable if you have huge 
file system tree with millions of files.

So if I dont access the file which was written on node2 but not synced 
on node1 it will never be replicated and if something goes wrong with 
node2 I will loose data.

My question is, is there any algorithm, like wit RAID arrays, which can 
tell you if data/brick should be resynced.

as far as I understand currently my only option is to use ls -lR which 
would force resync and I should execute it on regular basis.

Regards,
Deyan.


Kamal K. Varma wrote:
> Hi Deyan,
>
> sync can be triggered using ls -lR  (time to complete depends upon 
> size of volume)
>
> Could you expand on what all you would would like to monitor as part 
> of health monitoring?
>
> Regards,
>
> Kamal
>
> Deyan Chepishev wrote:
>> Hello,
>>
>> Is there any reasonable way to monitor the health of replicated 
>> volume and sync it, if out of sync ?
>>
>> Regards,
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users